Working with the Product Canvas - Roman Pichler
The product backlog is a handy tool that lists the outstanding work necessary to develop a product. But it can be insufficient to create a brand-new product or an update aimed at a new market. Its linear structure makes it difficult to capture all product aspects including the user interface design and the user interaction; there is no place to state assumptions about the target group, the users and customers of the product and their needs and trying to prioritise all items can lead to long-winded discussions that are of limited value. This talk introduces a new tool: the Product Canvas. The canvas is designed to help product owners and agile teams create new products and product updates aimed at new markets. It has grown out of my work with product owners and product managers over the last ten years, it's compatible with the Business Model Canvas. If you are struggling to use your product backlog effectively or need help on agile requirements, user stories, user journeys, and personas, then don't miss this talk.
Recommandé
Recommandé
Contenu connexe
Plus de JAX London
Plus de JAX London (20)
Working with the Product Canvas - Roman Pichler
- 1. working with the product canvas @romanpichler romanpichler.com
- 3. the threat
- 4. what we need
- 5. how do we capture ideas and requirements? Great for But where are ! prioritising! the users?! features! Product Backlog Where is! What about the user the user interaction?! interface?! © 2012 Pichler Consul3ng Ltd 5
- 6. enter the product canvas Captures Describes the! who, why UX properly! and what! Product Canvas Provides the! Promotes! big picture &! helpful! the details! techniques! h9p://www.romanpichler.com/blog/agile-‐product-‐innova3on/the-‐product-‐canvas/ © 2012 Pichler Consul3ng Ltd 6
- 7. the product canvas explained Vision Your overarching goal or intention. Name The name of the product. Personas Journeys Ready Stories The users and the The user’s interaction with the The assumptions to be customers, with the need product captured as one or more validated next captured to be addressed or the scenarios, workflows, or story as ready stories: clear, problem to be solved; boards. feasible and testable described as personas. stories prioritised from one to n. Bound by a sprint goal when Scrum is used. Epics Design Constraints The product functionality The product and user The generic operational described as coarse- interface design preferably qualities of the product grained user stories. captured in form of paper such as performance, sketches. interoperability and robustness described in form of constraint cards. © 2012 Pichler Consul3ng Ltd 7
- 8. Stocking the canvas Personas Journeys Ready Stories 1 2 6 Epics Design Constraints 3 4 5 Implementable! Target group! Product! and needs! sketch! items! © 2012 Pichler Consul3ng Ltd 8
- 9. A Sample Product canvas Defeat! X-Wing! Vision the empire! Name Fighter! Personas Journeys Ready Stories t! Sprin Goa l! 1. Story! 2. Story! 3. Story! Epics Design Constraints Hyper-! drive! 4. Story! Deflector! Perfor-! mance! Proton! R2 com- torpedos! patible! 5. Story! Inflight! repairs! Unit! Auto! 6. Story! nav! cost! © 2012 Pichler Consul3ng Ltd 9
- 10. the product canvas in action Vision Change:! Pivot or! persevere! Product Canvas Build! Measure! Learn! © 2012 Pichler Consul3ng Ltd 10
- 11. thank you!