The Product Wall Release Planning Workshop by Alan Dayley
Download as PPTX, PDF•12 likes•5,731 views
The document outlines a comprehensive workshop framework for creating product alignment through a 'product wall' release planning workshop, emphasizing stakeholder collaboration across various teams. Key activities include defining product vision, identifying customer needs, persona creation, user story mapping, and sprint planning, all aimed at ensuring transparency, shared ownership, and effective project management. The workshop is structured to accommodate a large group of participants over 2-3 days, with activities designed to facilitate understanding and establish actionable plans for product development.
The Product Wall Release Planning Workshop by Alan Dayley
- 1. Copyright © 2015 SolutionsIQ Inc. All rights reserved. 6801 185th Ave NE, Suite 200 Redmond, WA 98052 solutionsiq.com 1.800.235.4091 Creating Program Alignment: The Product Wall Release Planning Workshop PREPARED BY Alan Dayley Senior Agile Coach [email protected] Mile High Agile 2015 - 4/3/2015
- 2. Product Wall Release Workshop
- 3. • Clarity of product purpose • Dependencies visible • Shared ownership of results • Shared understandings • Ready to use Sprint Plans • Connections between functional skills and departments • View of product possibilities • Refined backlog • Fun Expected Results
- 4. HOW: Conditions and Participants • Release time frame of six months or less • Schedule 2-3 days • 30-100 people • Working on same product, same code base or otherwise linked • Agile Teams – All Members • Product Management • Subject Matter Experts • Marketing, Leadership, Operations, Support, Others • Users
- 5. Why? 30-100 people for 2-3 days!
- 8. 5 Levels of Agile Planning Product Vision Road Map Release Sprint Daily
- 10. Product Strategy What are the problems we are solving? »Business Canvas »Product Principles »Product Vision Product Discovery Product Planning Product Develop- ment Product Delivery Customer Research Ongoing Feedback
- 11. Customer Research Who are our customers and what are their needs? »Customer Development (Lean Startup) »Customer Personas Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Ongoing Feedback
- 12. Product Discovery What are the outcomes we need to achieve? »Experience/Story Map »Product Ideation »Feature Priortization Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback
- 13. Product Planning What is the minimal viable product for outcomes? »Product Backlog Refinement »Minimal Viable Experiments Product Discovery Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback
- 14. Product Development What is the work needed to build our product? »Iterative Development / Scrum »Task Board »Information Radiators Product Discovery Product Planning Product Delivery Product Strategy Customer Research Ongoing Feedback
- 15. Product Delivery When will we deliver product increments? »Delivery Forecasts »Product Roadmap »Release Burndown / Burnup Product Discovery Product Planning Product Develop- ment Product Strategy Customer Research Ongoing Feedback
- 16. Ongoing (Constant) Feedback How will we stay focused and coordinated? »Product Wall »Scrum of Scrums Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research
- 17. Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback All In One Workshop Product Vision Road Map Release Sprint Daily Product Wall Release Workshop
- 19. Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback Vision Creation Business Model Canvas Workshop Activities
- 20. Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback Vision Creation Road Map Creation Business Model Canvas Workshop Activities
- 21. Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback Vision Creation Road Map Creation Persona Creation Business Model Canvas Workshop Activities
- 22. Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback Vision Creation Road Map Creation Release Vision Creation Persona Creation Business Model Canvas Workshop Activities
- 23. Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback Vision Creation Road Map Creation Release Vision Creation Persona Creation User Story Mapping Business Model Canvas Workshop Activities
- 24. Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback Vision Creation Road Map Creation Release Vision Creation Persona Creation User Story Mapping Product Wall Creation Business Model Canvas Workshop Activities
- 25. Product Discovery Product Planning Product Develop- ment Product Delivery Product Strategy Customer Research Ongoing Feedback Vision Creation Road Map Creation Release Vision Creation Persona Creation User Story Mapping Product Wall Creation Sprint Story Planning Business Model Canvas Workshop Activities
- 26. Levels of Agile Planning Vision Creation Road Map Creation Release Vision Creation Persona Creation User Story Mapping Product Wall Creation Sprint Story Planning Business Model Canvas Product Vision Road Map Release Sprint Daily
- 28. Vision Creation “A computer on every desk and in every home.” Bill Gates, 1980
- 29. Example Vision as Elevator Pitch
- 30. Geoffrey Moore’s Elevator Pitch FOR <target customer> WHO <statement of the need> THE <product name> IS A <product category> THAT <key benefit> UNLIKE <primary competitor> OUR PRODUCT <further differentiation> From Geoffrey Moore, Crossing the Chasm
- 31. HOW: Vision Exercise • If a product vision already exists, use it! • Have CEO or a Product Management leader present it • 20 minutes, at most • If creating one, introduce the elevator pitch format • Have Product Management lead discussion to fill in the format • 20 minutes, at most
- 32. Activity: Business Model Canvas
- 34. BMC Template
- 35. What are the elements that make up a business model?
- 36. Customer Segment “For whom are we creating value?” Source: Adapted from Alex Osterwalder
- 37. Value Proposition “What value do we deliver to the customer?” Source: Adapted from Alex Osterwalder
- 38. Channels “How do we deliver the value we create to the customer?” Source: Adapted from Alex Osterwalder
- 39. Customer Relationships “How do we create & maintain relationships with our customers?” Source: Adapted from Alex Osterwalder
- 40. Revenue Streams “How much will these customers pay for the value we create?” Source: Adapted from Alex Osterwalder
- 41. Cost Structure “How much will this cost to create and maintain?” Source: Adapted from Alex Osterwalder
- 42. Key Resources “Who and what will we need to create this value?” Source: Adapted from Alex Osterwalder
- 43. Key Activities “What will we do with these resources to build value?” Source: Adapted from Alex Osterwalder
- 44. Key Partners “Who would we partner with that will provide us with Key Resources or Key Activities?” Source: Adapted from Alex Osterwalder
- 45. HOW: Build BMC Exercise • Prepare a large, blank Business Model Canvas in advance and tape to the wall • Tell the story of each box • Solicit sticky notes to put in each box, either by voice or by writing their on an placing them on the canvas • Fill in every box • Use different colors, marks, etc. as needed • May take an hour to complete • Could have smaller representative team do it before main workshop
- 46. Activity: Road Map Creation
- 48. HOW: Create The Road Map • Before the workshop, help Product Management define main “Epics” or feature groups desired for the release • These are at a high level not too much detail • Based on market research, customer interviews, etc. • At the workshop the desired feature groups can be presented and refined • The Road Map includes current and next 2-3 releases
- 50. Persona Creation
- 51. Data Persona
- 52. Empathy Map Think and Feel? Hear? See? Say and Do? Pain Gain
- 53. HOW: Create Personas • If you already have personas, use them • Existing personas can be explained and refined • Split into ad-hoc persona teams, one persona per team • Build the Empathy Map for each persona within the ad-hoc teams • Regroup and present creations to entire group • All takes up to 1.5 hours
- 54. Activity: Release Vision Creation
- 55. Release Vision Creation FOR <target customer> WHO <statement of the need> THE <product name> IS A <product category> THAT <key benefit> UNLIKE <primary competitor> OUR PRODUCT <further differentiation> From Geoffrey Moore, Crossing the Chasm FOR <target customer> WHO <statement of the need> THE <product name> IS A <product category> THAT <key benefit> UNLIKE <primary competitor> OUR PRODUCT <further differentiation> From Geoffrey Moore, Crossing the Chasm FOR <target customer> WHO <statement of the need> THE <product name> IS A <product category> THAT <key benefit> UNLIKE <primary competitor> OUR PRODUCT <further differentiation> From Geoffrey Moore, Crossing the Chasm FOR <target customer> WHO <statement of the need> THE <product name> IS A <product category> THAT <key benefit> UNLIKE <primary competitor> OUR PRODUCT <further differentiation> From Geoffrey Moore, Crossing the Chasm
- 56. HOW: Create Release Vision • Product Management references the Road Map to give feature groups to each team • Collaboratively decide which team will likely work on which feature group • Split into your defined Agile Teams • Looking at their feature group, each team writes and elevator pitch for that feature set • Come back together and present Release Visions to each other • Takes 45 minutes
- 57. Activity: User Story Mapping
- 59. Identify releases in a Story Map by slicing horizontally time optionality necessary less optional more optional first release second release third release Source: Jeff Patton. “An Introduction to User Story Mapping” User goals Release Slices
- 60. HOW: Create Story Maps • Each team uses their “Epics” or feature groups desired for the release • Convert the feature groups to user goals by asking “What is the user trying to accomplish with this new feature?” • These goals are the top row of the Story Map • Start making actions the user will take to accomplish each goal • Have an experienced Story Map facilitator! • This mapping takes several hours
- 61. Activity: Product Wall Creation
- 66. HOW: Create The Product Wall • Each team pulls actions from the Story Map or writes large stories from the Story Map • Each team, all at the same time places these cards on The Product Wall • Placement into Sprints is a “gut feel” guess at this point. • Just lay them out, making and changing cards as they go. • Tag the cards to indicate owner team and dependencies • Review to each other the end result
- 67. Activity: Sprint Story Planning
- 69. Sprint Story Planning Cycle
- 70. HOW: Sprint Story Planning • Each team references the large stories in The Product Wall Sprint 1 column • Each team plans Sprint 1 in their usual way • Each hour, all teams return to The Product Wall to update the contents of Sprint 1 and the Story Maps • Continue this cycle until Teams have Sprint 2 planned • Now plan Sprint 2, then 3 until time runs out • The Product Wall Release Workshop ends with teams performing this cycle
- 71. Sample Agenda
- 72. HOW: Sample Workshop Agenda Pre-Workshop Activites - Monday Time Subject Description 1:30 - 3:00 Business Model Canvas Invited participants create the canvas for presentation tomorrow 3:30 - 4:30 Preparation for tomorrow Room prep, materials, etc. Product Owner Epics/User Goal Review Review backlogs, dependencies, remaining planning for tomorrow
- 73. HOW: Sample Workshop Agenda Workshop - Tuesday Time Subject Description 9:00 - 9:15 Opening Introductions. Schedule and objectives for the day. Review of the release cadence (sprints) and iteration calendar, planning rules and expectations. 9:15 - 9:45 Release Vision Release Vision presentation by Executive and Product Management 9:45 - 10:15 Review Business Model Canvas Present and review the Business Model Canvas created by Product Management 10:15 - 10:30 Break 10:30 - 12:00 Persona workshop Review current personas with any updates 12:00 - 12:45 Lunch 12:45 - 1:30 Team Roster Review Discussions about team rosters and needs. Definition of Done and Team Agreements 1:30 - 1:45 Above the Line Peer accountability improvement 1:45 - 3:15 User goals / Road map Present the goals the user wants to accomplish with each product area. This is the top line of the User Story Map 3:15 - 3:30 Break 3:30 - 3:45 Introduce User Story Maps Brief training (a review for most) of User Story Mapping, emphasize Definition of Done 3:45 - 4:45 Build User Story Maps Appropriate and volunteer groups takle each User Story Map area. 4:45 - 5:00 Review the day Review the accomplishments of the day. Preview of tomorrow. Handle questions
- 74. HOW: Sample Workshop Agenda Workshop - Wednesday Time Subject Description 9:00 - 9:15 Opening Schedule and objectives for the day. 9:15 - 9:45 Vision and Persona review Evaluate if the vision still fits and makes sense. Check the personas and empathy maps 9:45 - 10:45 Build User Story Maps Continue work of previous day 10:45 - 11:00 Break 11:00 - 12:00 Adjust user activities for importance and define release content slices Adjust the vertical information of the maps to define importance of actions 12:00 - 12:15 Review User Story Maps Highlights of each map are reported to the whole group 12:15 - 1:00 Lunch 1:00 - 1:15 Introduce Product Wall Brief training on creating and using a Product Wall 1:15 - 2:00 Build Product Wall Write epics/stories from User Story maps into the Product Wall 2:00 - 2:15 Confidence Check Faciliator asks for fist of five "confidence factor" Definition of Done reminder 2:15 - 2:30 Break 2:30 - 2:45 Intro to Sprint Story Planning Cycle Describe how the User Story Map <-> Product Wall <-> Backlog Refinement <-> Sprint Planning will work 2:45 - 4:45 Sprint Story Planning Individual teams start grooming backlogs, planning sprints, etc. 4:45 - 5:00 Review the day Review the accomplishments of the day. Preview of tomorrow. Handle questions
- 75. HOW: Sample Workshop Agenda Workshop - Thursday Time Subject Description 9:00 - 9:15 Opening Schedule and objectives for the day. Have Sprint 1 tasked and ready! 9:15 - 9:45 Product Wall Review Referencing the vision, personas, etc., review the Product Wall 9:45 - 10:45 Sprint Story Planning Individual teams start grooming backlogs, planning sprints, etc. 10:45 - 11:00 Confidence Check Faciliator asks for fist of five "confidence factor" 11:00 - 12:00 Sprint Story Planning Individual teams start grooming backlogs, planning sprints, etc. 12:00 - 1:00 Lunch 1:00 - 2:00 Sprint Story Planning Individual teams start grooming backlogs, planning sprints, etc. 2:00 - 2:15 Confidence Check Faciliator asks for fist of five "confidence factor" 2:15 - 3:15 Sprint Story Planning Individual teams start grooming backlogs, planning sprints, etc. 3:15 - 3:30 Confidence Check Faciliator asks for fist of five "confidence factor" 3:30 - 4:00 Update Product Wall and Present Sprint Plans Each team presents their plans tasked out plans for Sprints 1-2 and stories for subsequent Sprints. Update the Product Wall accordingly. 4:00 - 4:30 "Product Box" Commitment Commitment to the Product Wall items that can go "on a Product Box" 4:30 - 5:00 Retrospective of the workshop Retrospective of the workshop. How did it work for us?
- 76. Ongoing Product Wall Use
- 78. Scrum of Scrums
- 79. Scrum of Scrums
- 80. Now In Sprint 2
- 81. HOW: Scrum of Scrums • Two or more times per week a Scrum of Scrums takes place in front of The Product Wall • Each team selects one person to represent the team at the meeting • Not always the same person, rotate • All members of all teams are welcome to attend, along with anyone else interested • Only the representatives speak • Update cards, highlight dependencies • The Scrum of Scrums lasts 15 minutes
- 82. Own and Improve
- 84. Tags to Color and Shapes
- 85. HOW: Own The Product Wall • Talk about the vocabulary and rules of the wall • Bring up improvement ideas • Keep it as simple as possible • Keep it as useful as possible • Changes to the way The Product Wall works should be made collaboratively • If people are not using it, that is an indicator that improvements are needed • ScrumMasters watch for improvement needs
- 86. Select Exercises Vision Creation Road Map Creation Release Vision Creation Persona Creation User Story Mapping Product Wall Creation Sprint Story Planning Business Model Canvas
- 87. • Vision: Geoffrey Moore, Crossing the Chasm • Business Model Canvas: Alex Osterwalder, www.businessmodelgeneration.com • Empathy Map: Dave Gray • Story Mapping: Jeff Patton, www.agileproductdesign.com/blog/the_new_backl og.html • Product Wall: Inspired by Tom Looy, agileatlas.org/articles/item/the-great-wall-scaling- agile-on-a-multi-team-project • Product Ecosystem: Inspired by Skip Angel • Awesome clients that build things! Acknowledgements
- 89. Alan Dayley Agile Coach CSM, CSPO, CSP, SAFe Agilist [email protected] http://bigvisible.com/author/adayley @DayleyAgile http://plus.google.com/+AlanDayley
- 90. How to build a Business Model Canvas
- 91. ? ? ??? ? ? ? ? ? ? ? “Let’s map out our existing business model” Source: Adapted from Alex Osterwalder tip: tell a story
- 92. ? ? ??? ? ? ? ? ? ? “Who is our Customer Segment?” Source: Adapted from Alex Osterwalder
- 93. ? ? ??? ? ? ? ? ? “What need of theirs do we solve?” Source: Adapted from Alex Osterwalder
- 94. ? ? ??? ? ? ? ? “How do we deliver our solution to them?” Source: Adapted from Alex Osterwalder
- 95. ? ? ??? ? ? ? “How do we build relationships with them?” Source: Adapted from Alex Osterwalder
- 96. ?? ? ? ? “How do we make money delivering this value?” Source: Adapted from Alex Osterwalder
- 97. ? ? ? “What does this cost us to build & maintain?” Source: Adapted from Alex Osterwalder
- 98. ? ? “Who & what do we need to create this?” Source: Adapted from Alex Osterwalder
- 99. ? “What activities do these resources perform?” Source: Adapted from Alex Osterwalder
- 100. “Who do we partner with?” Source: Adapted from Alex Osterwalder
- 101. This can apply to internal projects! Source: Adapted from Alex Osterwalder
- 102. This can be an Internal User or Stakeholder Source: Adapted from Alex Osterwalder
- 103. This can be an Internal Product or B2B Solution. Source: Adapted from Alex Osterwalder
- 104. These can be Internal Costs and Metrics. Source: Adapted from Alex Osterwalder
- 105. These can be Internal Partnerships across Functional Departments Source: Adapted from Alex Osterwalder
- 107. Ideas Decisions Principle: Diverge then Converge Diverge Brainstorming Observations Converge Insights Conclusions Setup Goal
- 108. Principle: Small, Large, Small Individuals Small Groups Large Group Most Decisions }
- 110. Principle: Self-organization Meeting self-organization is about: •Allowing the attendees to decide ‘how’ the work of the meeting will be done •Allowing the attendees to choose their work in the meeting, rather than pre-assign it •Attendees decide how they will respond to their given objectives and environment •Managers & Leaders can influence the objectives and environment of the meeting
- 111. <Footer Content: Presentation Title, Partner Name, Other> 111 Thank you! solutionsiq.com / 1.800.235.4091