A few days back I did a Scrum Tapas Video explaining what are few of the rules within Scrum. Besides these rules, there are also certain guidelines which help the Scrum Teams to make the best possible use of Scrum framework to create maximum Business Impact.
When I refer to rules, I mean those aspects which cannot be mended to fit a particular context. For ex: You cannot do Scrum without the 3 Roles – Product Owner, Development Team and Scrum Master.
When I refer to guidelines, I refer to those aspects which might be changed to fit to a particular context; the impact however, could only be verified after implementation. Then we Inspect and Adapt accordingly.
For ex: Product Backlog Refinement consumes no more than 10% of teams capacity. Is the capacity – # of hours; # of story points; # of man days – well no rule for that. Scrum Teams self-organize and choose what best fits their context; following the guideline that we consume no more than 10% of team capacity.
In this post I will be exploring few such guidelines which bind the 11 essentials together and give the Scrum Team flexibility to fit those aspects to their context.
#1. Development Team size: The size of Development Team is suggested to be 3-9 members. Depending on the context, it might have more people or lesser. The impact of it would vary based on team context.
From the Scrum guide:
Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful.
#2. Titles/Roles on Development Team: Scrum doesn’t recognize any titles/roles within the Development Team. Within the Development Team, everyone is a Development Team Member. Although, within an organization the team members may have titles/roles. In my experience that I have been associated with Scrum; I haven’t come across any team which has only one title/role.
#3. Three question format for Daily Scrum: Most teams that I have worked with utilize the format of 3 questions for Daily Scrum:
- What did I do yesterday that helped the Development Team meet the Sprint Goal?
- What will I do today to help the Development Team meet the Sprint Goal?
- Do I see any impediments that prevents me or the Development Team to meet the Sprint Goal?
Surprise, these 3 questions are just a template for teams that are starting with Scrum. The Development Team can structure the Daily Scrum in any way that they see fit as long as they focus on the progress towards Sprint Goal.
#4. Time-box for Events: The time-box for events states the maximum amount of time allowed for the event for a 1 month sprint. The guideline is: it is usually shorter for shorter duration of sprints.
Does that mean, for a two week Sprint, Sprint Planning is time-boxed …read more
Read more here:: B2CMarketingInsider