Covering up problems…
From the Scrum Guide: “Each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum. Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless.”
In your use of the Scrum framework, what has your team changed? What have elements been left out?
- Make a list of these elements, together with the reasons this was decided.
- What is the real problem this covered up?
- Is that problem still there?
- With your new insights, could you find better ways of dealing with that problem? While making better use of the Scrum framework?
Example:
Change: a team does the Daily Scrum only once a week - it’s called Daily...
Reason: Team members only work 2 days per week on the project.
Problem covered: not enough focus, not enough capacity - initiative not high enough in the priorities.
Better way: put this initiative in the fridge until more capacity is available. Focus on the more important initiative; finish it faster with the freed capacity; then switch back to this initiative with higher capacity and so more focus. Which will get this 2nd initiative also finished faster... Win-win-win.
What have you changed? Why? Sure you still want this change...?!?
I hope you find value in these short articles and if you are looking for more clarifications, feel free to take contact.
Don't want to miss any of these blog posts? Have the “The Scrum Guide Explored” series weekly in your mailbox.
Wishing you an inspiring read and a wonderful journey.
Scrum on!
