RSSSprint 2 Started Today
Sep 07
Today we started the second sprint for this set of requirements… Again it’s only about bringing up a website accessibility using the w3.org requirements. This means that this is more like a Scrum simulation than a real Scrum. But still it does make the whole team understand and use Scrum which is good. But there are some serious drawbacks though. Amongst which:
- Requirements are not expressed as user stories
- More often than not requirements can’t be broken down into tasks
- Requirements are not expressed as functions
This has several consequences:
- Estimation is difficult and inaccurate, though this might be due our team’s inability to do proper estimate
- tasks are very small and not numerous … thus reducing the sense of urgency
- Scrum is heavy in comparison to the amount of work needed to achieve the Sprint objectives
With all this in mind, I still consider it as a success in the sense
- that the whole team is adopting Scrum successfully and enthusiastically.
- The management and development process suddenly became apparent to everybody in the whole company giving more sense to my role as well. Eventually, I sense that this will raise the whole department credibility thus my own credibility (I work as project manager but I am the only project manager, thus my role entails department management as well lol)
- Everybody is expressing himself more and gray areas are cleared early
There is still so much work to do to achieve a refined Scrum process…
Today however, we all discussed the concept of “Done”, we also started using some nice templates for our product and sprint backlogs and I also setup a quite nice Scrum wall… All this I feel is giving life to our process and bringing it one step closer to a professional high level Scrum process!