Re: [scrumdevelopment] Sprint planning
- Your problem isn't sprint planning, its the silos. Anytime you have silos - i.e. only person that can do something you will have bottlenecks. Whole books are written on this subject (think Goldratt and the Theory of Constraints). Scrum tells you to have team members pull + self assign work - only when they're free to avoid this problem. Over time it will create a team of generalising specialists.Congratulations this is one of the key agile problems that everyone finds sooner or later.CheersMark LevisonOn Mon, Nov 23, 2009 at 10:13 PM, Sharmila D <sharmila.patwardhan@...> wrote:
I have been working with a Scrum team for the core Architecture of the product. We have been working in sprints. However since it is core architecture, we have different modules for which within the team we have people who have expertise. So after we have planned and estimated in the sprint planning meeting, we often end-up with uneven leveling of work.
Although I completely understand that in the Sprint planning, the team commits. However after the sprint planning we have to work out and find if we have people who are overloaded.
Has anyone encountered this kind of situation?
How do we improve the sprint planning in this case?
We have also proposed competency building but the "expert" area will still remain to some extent.
It's easier to write "the team commits and picks of work" but that's not really the case here.
Any thoughts or ideas?