What is the Must Should Could Won’t Retrospective?
Our actions should express our priorities, and Must Should Could Won’t is a great sprint retrospective template to help teams identify those priorities to ensure they continue to deliver value where it is most needed.
With that in mind, it’s an approach that aligns well with Agile processes and frameworks given its focus on the delivery of valuable things first.
It is also a great Scrum sprint retrospective idea as it offers the product owner a mechanism to step into the shoes of their customer and view the product from their perspective.
The Must Should Could Won’t template is incredibly powerful when used well. It is a particularly useful tool to maintain focus on priorities for projects with a large number of feature requests and competing stakeholders. It is also a great way to ensure any personal bias of the project team does not distort project priorities.
Must Should Could Won’t Retrospective Template format
These elements are critical or core to delivery or release or are a requirement as needed by law or project delivery requirements.
These elements are important but not critical for the release nor are they time-sensitive. They may be requests that have come from users but are not show stoppers and can be seen as nice to have items – think low-cost value adds.
These would be great to have, but the release could be fulfilled without them. They may be future iteration ideas, potential growth or product differentiators, and something that could happen in the future.
These are elements that the team will not do and is specifically out of scope. For example, they may choose not to support an operating system, or that a product direction is specifically excluded.