10 Things to Scrum Right
Scurm is a famous agile software methodology, which based on team self-organizing.
for more information about scrum you can visit
Control Chaos, the official home for scrum.
or keep in touch with my blogs, I'll be writing lots of articles about Scrum in the next weeks.
Scrum is really easy to adopt and use, and also easy to screw up, and these are some practices you should consider.
- Make the three roles of Scrum clear and known (Scrum Master, Product Owner and Team)
- Separate the Pigs from Chickens for each project
Pigs are all the people that have any title of the three Scrum titles within the project
Chickens are the people interested in the project but not part of the Scrum. - Scrum Master MUST believe in Scrum philosophy and also well trained.
- Scrum Master MUST attend and lead all the daily scrum meetings and scrum planning meetings, ignoring Scrum meetings sends negative messages to all team members
- The relation between the Scrum Master and the Team must follow the analogy of Sheepdog and Sheep group, so the Scrum Master always takes care of the team and does all possible actions to solve any problems facing the team, also protecting them from outside bad influence.
- No tasks can be added to a sprint once started, which means no side work.
- Product Owner should be responsible of Product Backlog and add any tasks to the backlog to be implemented in future sprints.
- No releases in middle of sprints, Sprints are meant to produce working releases at the end of each sprint, doing many releases in one sprint will make the sprint goals out of control.
- Daily Scrum Meetings should never exceed 20 minutes, which means 3 minutes for each team member at max
Scrum Planning Meetings should not exceed 8 hours, the first 4 hours are for the Product Owner describing the Product Backlog items and prioritizing them, the last 4 hours is for the team members to assign tasks between them and make estimations.
All the meetings should be recorded in the daily log, for future reference.
- The Scrum Master role is Guiding the team to follow the process, not Controling the team in the process, the team should have enough space to self-organize itself, the main concern for the Scrum Master is the Process itself, and making sure that it is applied in the right way.
Digg This
