Outcome Improvement Canvas

Published by Cristina Pana on

While interacting with various agile software teams, we have observed that most of them have measured success using process metrics – velocity, time to market, cycle times, resolved issues, planned vs done work.

This year we conducted a study about agility in the romanian software community. Most respondents evaluated that Agile success is measured by looking at business value added and quality.

Agile Success Metrics

Agile software development is based on continuous improvement. And on the ability to adapt to change to deliver quality working software. Although useful, sometimes the metrics we choose don’t always reflect the outcome. The effort in measuring is relevant if connected with the bigger picture. And if it will have positive impact in delivering the promise to its customers.

Product, People and Development.

Software development is a complex work. Adding on top the customer expectations and people needs increases this level of complexity. Focusing on outcomes can be a great way to create a balance and generate healthy progress.

This is why we designed this canvas. You can use this tool to generate awareness on what is the desired outcome. While taking into account the three pillars:

  • product management
  • organizational and people
  • development process.
outcome improvement canvas
Outcome improvement canvas Example

The Outcome Improvement Canvas helps you assess the current state, describe your key outcomes, decide on the right actions and keep track of your progress in a simple way.

You can use the canvas as a guiding tool in assessment. Or in discovery workshops, planning, retrospective, review meetings and day to day work. The entire product team and contributors (support stakeholders) should contribute and be aware of its contents. Having clear outcomes can help teams keep their work on the needed track.

The Why row should change when the team is satisfied with the results. And when the team believes that the outcome is achieved. On the other hand, the team can change the following rows anytime. As long as it serves the outcome, of course.

Outcomes are the results or changes you expect to happen after a series of actions. It can be quantitative or qualitative, good outcome statements are specific, measurable, and realistic. Our suggestion is to reflect the content of the canvas in the product or sprint backlog. Also, you can print it and make it visible in the office.

Download the template in different sizes here

We have used this tool mostly in assessment phases in our programs, to make the team aware of the current state and define what should we focus on. And It gives structure in conversations and generates visibility and common understanding of the outcomes.

If you use the canvas, please share with us your experience and how it helped you.


Leave a Reply

Avatar placeholder

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Cookie Settings