Sharpen up your Scrum
Did you just wake up from your Agile dream realizing that your Scrum is not as Agile as you thought it would be and you are not seeing the obvious benefit as clearly as before?
Are technical debts piling up and is the increment release process painful?
Then you might need to look yourself in the mirror and have a honest retrospective about Scrum with inspecting your symptoms – only then you are able to understand what might be causing your problems.
Remember when you first heard of Scrum and how its success stories where so interesting and how this Scrum Framework was so simple and compelling? (I do too! )
But what happened? Why is your Scrum not as smooth and transparent as you wanted?
Most likely you have given too much discount on the Scrum definition, values, roles or events in your company – it can be easy to let things slide abit, but that can and probably will cause snowball effects.
But don’t worry, you can fix this – Let me show you how.
Your Dev team is the largest stakeholder
Sure, you have large customers or important individuals that can affect the product development – but make no mistake, your Dev Team is the biggest stakeholder.
Help the Dev team know that they are the most important stakeholder and help them understand that using Scrum the right way they have more leverege when discussing backlog items with the Product Owner.
In this way you make the Dev Team will feel more responsible on the Product and have its functions and wellness as a priority.
Mutual respect and democracy
Within a Scrum team there should be a democracy and the Product Owner or Scrum Master is not to control the team – this should be a open discussion where everybody decides on what backlog items is to be worked on.
Encourage your Dev team on being honest and respectful with each other– in that way the Dev team will be able to learn more and that will reinforce the team’s ability to cooperate.
So what steps should I take to restart my Scrum?
- Read the official Scrum Guide (again).
- Get the managment to formally support Scrum and coach them on their role in Scrum.
- Make sure you have Scrum Master and Product Owner roles in place.
- Facilitate an extra retrospective event where you go over Scrum with the focus to see where you are doing well in Scrum and where you have lost your way in Scrum.
- Create an action plan on how to get back on track.
After you have restarted your Scrum you are not done!
To keep Scrum working, you will need to apply Continual Service improvement approach.
There is always something to improve and there is always the risk that some Dev Team, Scrum Master or Project Owners start to mess with the Scrum definition, values, roles or events in your company – so stay alert to keep your Scrum on Track.
CoreMotif knows Scrum in and out. Send us a mail with your thoughts and we will be happy to get back to you.