Risk management in Scrum – Insights
The Nokia test provides criteria to measure the adequacy of Scrum implementation. If we have ScrumBut (aka inadequate Scrum), then we should not expect the accomplishments in terms of higher velocity, better quality and increased customer value.
Even while we are implementing ScrumBut, we should strive to show some value from using Scrum. This value will allow us to remove handicaps for Scrum implementation and therefore improve our score in Nokia test.
ScrumBut introduces risks to the project. Such risks should be managed using the rigor of Risk Management (RskM) process. PMBOK® and CMMI® have in-depth addressing of RskM details. Traditionally, software development is driven by risks. There are two drivers that can help us start brainstorming for risk identification.
- Risks originated from ScrumBut.
- Risks originated from not achieving the value which management expects as a result of using Scrum.
- Monitor the risks
- Update risks status
- Identify new risks
- Create actions to address risks
Such meetings and the outcomes tasks are planned in the sprint backlog.