Product 2012
Product Canvas
The bridge between vision and backlog: personas and big picture on one side, the next goal's details on the other.
What it is
Pichler's working canvas for agile product teams: name, goal, and metrics across the top; personas, the big-picture journey and epics in the middle; and a product details section holding just the next iteration's items. It keeps the backlog attached to the reasons behind it.
Reach for it when
- A scrum team's backlog has detached from any picture of the user
- A new product needs enough structure for sprint one without a 40-page spec
- Design and engineering plan from two different documents
Running it
- Set the goal and its metric first. One goal. The canvas serves it.
- Sketch personas and the journey at whiteboard fidelity; epics hang off the journey.
- Detail only the next goal's slice into ready items. The rest stays big-picture on purpose.
- Revisit at every sprint boundary; move one epic into detail as one moves out.
Watch out: If the details section grows past one iteration's worth, it's a backlog wearing a canvas costume.
Add unlimited notes to any activity
Comments & Discussion
Add a Comment
Recent Comments (3)
This workshop was incredibly effective for our remote team! We adapted it slightly for a virtual setting and it worked wonderfully. The key was breaking into smaller breakout rooms.
Great resource! One tip: prepare all materials the day before to avoid any last-minute rushes.
Used this for our quarterly planning session. The structured approach really helped us stay on track!