.png)
© scrum.org
The team adopted the SCRUM method to work on TMSS. Over the course of the past years, the SCRUM team iteratively (in sprints) developed components and functionality in a prioritization-based order in close collaboration with stakeholders and users through alignment- and review sessions.
The PO collaborated with the various stakeholders on the priority of the work. Input about the backlog could be given in multiple ways, like stakeholder meetings, sprint reviews, or coincidental encounters in the hallway, to name some. Every iteration, the team decided on the goal for the next three weeks and the work involved. Through daily meetings, the team came to product increments which were reviewed with all who were interested at the end of the three weeks. Finally, during the sprint retrospective, the team came together to discuss what could be improved during the next iteration.
What have we learned along the way?
- Know your customer.
- Focus on a goal, less on the specific items of work.
- Be transparent about a change of priorities within an iteration.
- Estimate work for the short and long term, by comparing these to similar pieces of work carried out before.
- Communicate (and collaborate on) expectations early and often.
- Use one (product) backlog for transparent prioritization.
- Release software early and often. A minimum viable product, although lacking functionality, will give you better insights for future product development.
If you want to know more, do reach out!