Geeks With Blogs
Stephen Myers Good Times with .Net
1.        The SCRUM must be short and NOT exceed 15 minutes daily. Achieve this with a Timekeeper. The Timekeeper role should rotate daily and the timekeeper should be fined $1 if the SCRUM does not start on time by opening the call in line and closing the door or if the SCRUM exceeds 15 minutes. 
2.       Team members must be on time for the SCRUM or be fined $1. To have productive developers, the SCRUM should be run at a reasonable time – a morning stand up should be a good way to share information and start a productive day, not a wake-up call to get Asses in seats or chastise developers who are not early risers.   
3.       Use a SCRUM Board. The board should consist of a list of each: milestones, issues, and risks with due dates as they apply to the team. There is also a team member component where each team member’s name is on one axis and two weeks’ worth of dates forward on the other axis. In each box, team members should put any Time off or what they plan on working on that day. This should be completely updated for the current week going forward before SCRUM on Monday morning or team members should be fined $1. 
4.       The format should be that each team member in the circle tells briefly what they are working on and any issues or risks that are going to cause the work to stall or miss deadlines. The timekeeper must keep the SCRUM moving by deciding when a topic is getting too deep and should be moved to a breakout session with the appropriate parties. The Team Leaders should go over the issues and risks to make sure that they have owners.   
5.       Fine Money can be used to purchase beer or something else for the team. 
Posted on Wednesday, October 5, 2011 1:59 PM | Back to top


Comments on this post: Salient Qualities of Effective SCRUM

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © smyers | Powered by: GeeksWithBlogs.net