In one of my previous posts I discussed the Portfolio Canvas. I received several questions from my readers, triggered by the picture of the Portfolio Canvas, that they would like to see the post in English. I asked the developers if they were willing to create an English version. I just received the first draft.
The remainder of this post is the translation of the Dutch post: Portfolio Canvas.
I was triggered by a sneak preview of this portfolio Canvas during a seminar about business agility with an agile portfolio (28 June 2017). I thought this canvas was an answer for agile portfolio management, but now it is formally released, I have to conclude it’s not completely true.
In this post, I will briefly summarize this portfolio Canvas and I give my vision and some recommendations. Feel free to give feedback too.
Michael Sauerbier, Diederik Biesboer, Daniel van den Dries & John van Rouwendaal (all from Cratos Consulting) are the developers of the Portfolio Canvas®.
On their website ( http://cratosconsulting.nl/het-portfolio-canvas/, in Dutch only) we get the following summary:
The Portfolio Canvas is a tool for portfolio managers and (senior) management to:
- Create a project portfolio overview and
- To facilitate the priority discussion
The Portfolio Canvas supports organizations in answering the following questions:
- Who, why, when, and which projects and programs
- What are the overall portfolio cost (Euro) and benefits (revenues)
- Biggest portfolio risks and dependencies
The Portfolio Canvas delivers added value in the development and monitoring of a project portfolio by:
- Facilitating the creation of the project portfolio
- Delivering a simple overview of the agreed portfolio
- Communicating the agreed portfolio
- Facilitates progress monitoring and control.
Remarks and recommendations:
- Good initiative, which can become, in co-creation, a valuable add for organizations.
- Replace revenues with benefits or value (financial & non-financial) and work force with people.
- Nice layout. For me unclear why the arrow and the circle in the center is counter clockwise.
- I have my doubts if the portfolio canvas offers enough information to control the portfolio progress (maybe by adding post-its on projects in the ‘DOING’-area with impediments (e.g. end date not feasible).
- I would suggest extending the portfolio canvas with a timeline at the bottom with milestones (changes, benefits). And make the picture clockwise to show movement of the portfolio (and remove or shorten the rectangular extension)
- The developers explain that the portfolio canvas is based, among other things, on Kanban (Lean). I would like to emphasize this by adding a WIP-limit in the ‘DOING’-area (as an answer to a common anti-pattern of too many parallel in-flight projects).
- Best practices like Management of Portfolios (AXELOS) or the Standard for Portfolio Management (PMI) suggest dividing the portfolio into different buckets or categories and prioritize the initiatives within these buckets or categories.
- This could be facilitated by giving each strategic objective its own color and use post-its with the same color for the corresponding projects and programs.
Looking forward to your remarks and recommendations.