Page 1
Copyright©2015SolutionsIQInc.Allrightsreserved.
6801185thAveNE,Suite200Redmond,WA98052solutionsiq.com1.800.235.4091
CreatingAlignmentwithTheProductWallReleasePlanningWorkshop
[email protected]
Agile2016– 25July2016
Page 2
ProductWallReleasePlanningWorkshop
Page 3
ProductWallCreatedLive
Page 5
Prominent,VisibleLocation
Page 6
ContinuousCollaboration
Page 8
CommonCostlyMisalignment
Success
Page 9
EstablishValuableAlignment
Success
Page 10
HOW:ConditionsandParticipants• Releasetimeframeofsixmonthsorless• Schedule2-3days• 30-100people
• Workingonsameproduct,samecodebaseorotherwiselinked
• AgileTeams– AllMembers• ProductManagement
• SubjectMatterExperts• Marketing,Leadership,Operations,Support,Others
•Users
Page 11
• Clarityofproductpurpose• Dependenciesvisible• Sharedownershipofresults• Sharedunderstandings• ReadytouseSprintPlans• Connectionsbetweenfunctionalskillsanddepartments
• Viewofproductpossibilities• Refinedbacklog• Fun
ExpectedResults
Page 12
Why?
30-100peoplefor2-3days!
Page 13
WorkshopIncorporatesaCompleteAgileProductEcosystem
Page 14
5LevelsofAgilePlanning
ProductVision
RoadMap
Release
Sprint
Daily
Page 15
ProductEcosystem
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
Page 16
ProductStrategyWhatarethe
problemswearesolving?Product
Discovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
CustomerResearch
OngoingFeedback
Page 17
CustomerResearchWhoareour
customersandwhatare
theirneeds?
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
OngoingFeedback
Page 18
Whatarethe
outcomesweneedto
achieve?ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
ProductDiscovery
Page 19
Whatisthe
minimalviable
productforoutcomes?
ProductDiscovery
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
ProductPlanning
Page 20
Whatisthe
workneededtobuildour
product?
ProductDiscovery
ProductPlanning
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
ProductDevelopment
Page 21
Whenwillwe
deliverproduct
increments?
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductStrategy
CustomerResearch
OngoingFeedback
ProductDelivery
Page 22
Howwillwe
stayfocusedand
coordinated?
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
Ongoing(Constant)Feedback
Page 23
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
ProductVision
RoadMap
Release
Sprint
Daily
AllInOneWorkshop
Page 24
ProductWallReleasePlanningWorkshopActivities
Page 25
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
VisionCreation
WorkshopActivities
Page 26
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
VisionCreation
BusinessModelCanvas
WorkshopActivities
Page 27
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
VisionCreation
RoadMapCreation
BusinessModelCanvas
WorkshopActivities
Page 28
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
VisionCreation
RoadMapCreation
PersonaCreation
BusinessModelCanvas
WorkshopActivities
Page 29
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
VisionCreation
RoadMapCreation
ReleaseVisionCreation
PersonaCreation
BusinessModelCanvas
WorkshopActivities
Page 30
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
VisionCreation
RoadMapCreation
ReleaseVisionCreation
PersonaCreation
UserStoryMapping
BusinessModelCanvas
WorkshopActivities
Page 31
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
VisionCreation
RoadMapCreation
ReleaseVisionCreation
PersonaCreation
UserStoryMapping
ProductWallCreation
BusinessModelCanvas
WorkshopActivities
Page 32
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
VisionCreation
RoadMapCreation
ReleaseVisionCreation
PersonaCreation
UserStoryMapping
ProductWallCreation
SprintStoryPlanning
BusinessModelCanvas
WorkshopActivities
Page 33
VisionCreation
RoadMapCreation
ReleaseVisionCreation
PersonaCreation
UserStoryMapping
ProductWallCreation
SprintStoryPlanning
BusinessModelCanvas
ProductVision
RoadMap
Release
Sprint
Daily
LevelsofAgilePlanning
Page 34
Activity:VisionCreation
Page 35
VisionCreation
“Acomputeroneverydeskandineveryhome.”
BillGates,1980
Page 36
ExampleVisionasElevatorPitch
Page 37
GeoffreyMoore’sElevatorPitch
FOR<targetcustomer>WHO<statementoftheneed>THE<productname>ISA<productcategory>THAT<keybenefit>UNLIKE<primarycompetitor>OURPRODUCT<furtherdifferentiation>
From Geoffrey Moore, Crossing the Chasm
Page 38
HOW:VisionExercise• Ifaproductvisionalreadyexists,useit!
• HaveCEOoraProductManagementleaderpresentit
• 20minutes,atmost• Ifcreatingone,introducetheelevatorpitchformat• HaveProductManagementleaddiscussiontofillintheformat
• 20minutes,atmost
Page 39
Activity:BusinessModelCanvas
Page 40
BusinessModelCanvas
Page 41
BMCTemplate
What are the most important costs inherent in our business model? Which Key Resources are most expensive? Which Key Activities are most expensive?
Through which Channels do our Customer Segments want to be reached? How are we reaching them now?How are our Channels integrated? Which ones work best?Which ones are most cost-efficient? How are we integrating them with customer routines?
For what value are our customers really willing to pay?For what do they currently pay? How are they currently paying? How would they prefer to pay? How much does each Revenue Stream contribute to overall revenues?
For whom are we creating value?Who are our most important customers?
What type of relationship does each of our CustomerSegments expect us to establish and maintain with them?Which ones have we established? How are they integrated with the rest of our business model?How costly are they?
What value do we deliver to the customer?Which one of our customer’s problems are we helping to solve? What bundles of products and services are we offering to each Customer Segment?Which customer needs are we satisfying?
What Key Activities do our Value Propositions require?Our Distribution Channels? Customer Relationships?Revenue streams?
Who are our Key Partners? Who are our key suppliers?Which Key Resources are we acquiring from partners?Which Key Activities do partners perform?
What Key Resources do our Value Propositions require?Our Distribution Channels? Customer Relationships?Revenue Streams?
Day Month Year
No.
This work is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/
or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.
Page 42
Whataretheelements thatmakeupabusinessmodel?
Page 43
CustomerSegment
“Forwhomarewecreatingvalue?”
Source:AdaptedfromAlexOsterwalder
Page 44
ValueProposition
“Whatvaluedowedelivertothecustomer?”
Source:AdaptedfromAlexOsterwalder
Page 45
Channels
“Howdowedeliverthevaluewecreatetothecustomer?”
Source:AdaptedfromAlexOsterwalder
Page 46
CustomerRelationships
“Howdowecreate&maintainrelationshipswithourcustomers?”
Source:AdaptedfromAlexOsterwalder
Page 47
RevenueStreams
“Howmuchwillthesecustomerspayforthevaluewecreate?”
Source:AdaptedfromAlexOsterwalder
Page 48
CostStructure
“Howmuchwillthiscosttocreateandmaintain?”
Source:AdaptedfromAlexOsterwalder
Page 49
KeyResources
“Whoandwhatwillweneedtocreatethisvalue?”
Source:AdaptedfromAlexOsterwalder
Page 50
KeyActivities
“Whatwillwedowiththeseresourcestobuildvalue?”
Source:AdaptedfromAlexOsterwalder
Page 51
KeyPartners
“WhowouldwepartnerwiththatwillprovideuswithKeyResourcesorKeyActivities?”
Source:AdaptedfromAlexOsterwalder
Page 52
HOW:BuildBMCExercise• Preparealarge,blankBusinessModelCanvasinadvanceandtapetothewall
• Tellthestoryofeachbox• Solicitstickynotestoputineachbox,eitherbyvoiceorbywritingtheironanplacingthemonthecanvas
• Fillineverybox• Usedifferentcolors,marks,etc.asneeded• Maytakeanhourtocomplete• Couldhavesmallerrepresentativeteamdoitbeforemainworkshop
Page 53
Activity:RoadMapCreation
Page 55
HOW:CreateTheRoadMap• Beforetheworkshop,helpProductManagementdefinemain“Epics”orfeaturegroupsdesiredfortherelease• Theseareatahighlevelnottoomuchdetail• Basedonmarketresearch,customerinterviews,etc.
• Attheworkshopthedesiredfeaturegroupscanbepresentedandrefined
• TheRoadMapincludescurrentandnext2-3releases
Page 56
Activity:PersonaCreation
Page 59
EmpathyMap
ThinkandFeel?
Hear? See?
SayandDo?
Pain Gain
Page 60
HOW:CreatePersonas• Ifyoualreadyhavepersonas,usethem
• Existingpersonascanbeexplainedandrefined• Splitintoad-hocpersonateams,onepersonaperteam
• BuildtheEmpathyMapforeachpersonawithinthead-hocteams
• Regroupandpresentcreationstoentiregroup• Alltakesupto1.5hours
Page 61
Activity:ReleaseVisionCreation
Page 62
ReleaseVisionCreation
FOR<targetcustomer>WHO<statementoftheneed>THE<productname>
ISA<productcategory>THAT<keybenefit>UNLIKE<primarycompetitor>OURPRODUCT<furtherdifferentiation>
From Geoffrey Moore, Crossing the Chasm
FOR<targetcustomer>WHO<statementoftheneed>THE<productname>
ISA<productcategory>THAT<keybenefit>UNLIKE<primarycompetitor>OURPRODUCT<furtherdifferentiation>
From Geoffrey Moore, Crossing the Chasm
FOR<targetcustomer>WHO<statementoftheneed>THE<productname>
ISA<productcategory>THAT<keybenefit>UNLIKE<primarycompetitor>OURPRODUCT<furtherdifferentiation>
From Geoffrey Moore, Crossing the Chasm
FOR<targetcustomer>WHO<statementoftheneed>THE<productname>
ISA<productcategory>THAT<keybenefit>UNLIKE<primarycompetitor>OURPRODUCT<furtherdifferentiation>
From Geoffrey Moore, Crossing the Chasm
Page 63
HOW:CreateReleaseVision• ProductManagementreferencestheRoadMaptogivefeaturegroupstoeachteam• Collaborativelydecidewhichteamwilllikelyworkonwhichfeaturegroup
• SplitintoyourdefinedAgileTeams• Lookingattheirfeaturegroup,eachteamwritesandelevatorpitchforthatfeatureset
• ComebacktogetherandpresentReleaseVisionstoeachother
• Takes45minutes
Page 64
Activity:UserStoryMapping
Page 66
IdentifyreleasesinaStoryMapbyslicinghorizontally
time
optio
nality
necessary
lessoptional
moreoptional
firstrelease
secondrelease
thirdrelease
Usergoals
ReleaseSlices
Source:JeffPatton.“AnIntroductiontoUserStoryMapping”
Page 67
Abovetheline,ornot
Page 68
HOW:CreateStoryMaps• Eachteamusestheir“Epics”orfeaturegroupsdesiredfortherelease
• Convertthefeaturegroupstousergoalsbyasking“Whatistheusertryingtoaccomplishwiththisnewfeature?”• ThesegoalsarethetoprowoftheStoryMap
• Startmakingactionstheuserwilltaketoaccomplisheachgoal
• HaveanexperiencedStoryMapfacilitator!• Thismappingtakesseveralhours
Page 69
Activity:ProductWallCreation
Page 70
ProductWallCreation
Page 71
Teams,Dependencies,State
Page 73
Sprints
FeatureGrou
porEpicL
anes
ProductWallGrid
Page 74
HOW:CreateTheProductWall• EachteampullsactionsfromtheStoryMaporwriteslargestoriesfromtheStoryMap
• Eachteam,allatthesametimeplacesthesecardsonTheProductWall• PlacementintoSprintsisa“gutfeel”guessatthispoint.
• Justlaythemout,makingandchangingcardsastheygo.
• Tagthecardstoindicateownerteamanddependencies
• Reviewtoeachothertheendresult
Page 75
Activity:SprintStoryPlanning
Page 76
SprintStoryPlanning
Page 77
SprintStoryPlanningCycle
Page 78
HOW:SprintStoryPlanning• EachteamreferencesthelargestoriesinTheProductWallSprint1column
• EachteamplansSprint1intheirusualway• Eachhour,allteamsreturntoTheProductWalltoupdatethecontentsofSprint1andtheStoryMaps
• ContinuethiscycleuntilTeamshaveSprint2planned
• NowplanSprint2,then3untiltimerunsout• TheProductWallReleaseWorkshopendswithteamsperformingthiscycle
Page 79
ProductDiscovery
ProductPlanning
ProductDevelop-ment
ProductDelivery
ProductStrategy
CustomerResearch
OngoingFeedback
VisionCreation
RoadMapCreation
ReleaseVisionCreation
PersonaCreation
UserStoryMapping
ProductWallCreation
SprintStoryPlanning
BusinessModelCanvas
FinishWithReadySprintPlans
Page 81
HOW:SampleWorkshopAgendaPre-Workshop Activites - MondayTime Subject Description
1:30 - 3:00 Business Model CanvasInvited participants create the canvas for presentation tomorrow
3:30 - 4:30
Preparation for tomorrow Room prep, materials, etc.
Product Owner Epics/User Goal ReviewReview backlogs, dependencies, remaining planning for tomorrow
Page 82
HOW:SampleWorkshopAgendaWorkshop - TuesdayTime 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 VisionRelease Vision presentation by Executive and Product Management
9:45 - 10:15Review Business Model Canvas
Present and review the Business Model Canvas created by Product Management
10:15 - 10:30 Break10:30 - 12:00 Persona workshop Review current personas with any updates12:00 - 12:45 Lunch
12:45 - 1:30 Team Roster ReviewDiscussions 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 mapPresent 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:45Introduce User Story Maps
Brief training (a review for most) of User Story Mapping, emphasize Definition of Done
3:45 - 4:45 Build User Story MapsAppropriate and volunteer groups takle each User Story Map area.
4:45 - 5:00 Review the dayReview the accomplishments of the day. Preview of tomorrow. Handle questions
Page 83
HOW:SampleWorkshopAgendaWorkshop - WednesdayTime Subject Description9:00 - 9:15 Opening Schedule and objectives for the day.
9:15 - 9:45Vision 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 day10: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 group12: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 CheckFaciliator asks for fist of five "confidence factor" Definition of Done reminder
2:15 - 2:30 Break
2:30 - 2:45Intro 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 dayReview the accomplishments of the day. Preview of tomorrow. Handle questions
Page 84
HOW:SampleWorkshopAgendaWorkshop - ThursdayTime Subject Description
9:00 - 9:15 OpeningSchedule 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 Wall9: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:00Update 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:00Retrospective of the workshop Retrospective of the workshop. How did it work for us?
Page 85
Ongoing(Constant)FeedbackUsingTheProductWall
Page 86
ProductWallLocation
Page 90
HOW:ScrumofScrums• TwoormoretimesperweekaScrumofScrumstakesplaceinfrontofTheProductWall
• Eachteamselectsonepersontorepresenttheteamatthemeeting• Notalwaysthesameperson,rotate• Allmembersofallteamsarewelcometoattend,alongwithanyoneelseinterested
• Onlytherepresentativesspeak• Updatecards,highlightdependencies• TheScrumofScrumslasts15minutes
Page 92
IncreaseTeamVisibility
Page 93
TagstoColorandShapes
Page 94
HOW:OwnTheProductWall• Talkaboutthevocabularyandrulesofthewall• Bringupimprovementideas
• Keepitassimpleaspossible• Keepitasusefulaspossible
• ChangestothewayTheProductWallworksshouldbemadecollaboratively
• Ifpeoplearenotusingit,thatisanindicatorthatimprovementsareneeded
• ScrumMasters watchforimprovementneeds
Page 95
SelectExercises
VisionCreation
RoadMapCreation
ReleaseVisionCreation
PersonaCreation
UserStoryMapping
ProductWallCreation
SprintStoryPlanning
BusinessModelCanvas
Page 96
• Vision:GeoffreyMoore,CrossingtheChasm• BusinessModelCanvas:AlexOsterwalder,
www.businessmodelgeneration.com• EmpathyMap:DaveGray• StoryMapping:JeffPatton,
www.agileproductdesign.com/blog/the_new_backlog.html- Book:“UserStoryMapping”
• ProductWall:InspiredbyTomLooy,agileatlas.org/articles/item/the-great-wall-scaling-agile-on-a-multi-team-project
• ProductEcosystem:InspiredbySkipAngel• Awesomeclientsthatbuildthings!
Acknowledgements
Page 98
AlanDayleySeniorAgileCoach
CSM,CSPO,CSP,SAFe Agilist
[email protected]
http://www.solutionsiq.com/author/adayley/
@DayleyAgile
http://plus.google.com/+AlanDayley
Page 99
HowtobuildaBusinessModelCanvas
Page 100
? ? ???
?
??
?
?
??
“Let’smapoutourexistingbusinessmodel”
Source:AdaptedfromAlexOsterwalder
tip:tellastory
Page 101
? ? ???
?
?
?
?
??
“WhoisourCustomerSegment?”
Source:AdaptedfromAlexOsterwalder
Page 102
? ? ???
?
?
?
??
“Whatneedoftheirsdowesolve?”
Source:AdaptedfromAlexOsterwalder
Page 103
? ? ???
?
?
??
“Howdowedeliveroursolutiontothem?”
Source:AdaptedfromAlexOsterwalder
Page 104
? ? ???
?
??
“Howdowebuildrelationshipswiththem?”
Source:AdaptedfromAlexOsterwalder
Page 105
??
?
??
“Howdowemakemoneydeliveringthisvalue?”
Source:AdaptedfromAlexOsterwalder
Page 106
?
??
“Whatdoesthiscostustobuild&maintain?”
Source:AdaptedfromAlexOsterwalder
Page 107
??
“Who&whatdoweneedtocreatethis?”
Source:AdaptedfromAlexOsterwalder
Page 108
?
“Whatactivitiesdotheseresourcesperform?”
Source:AdaptedfromAlexOsterwalder
Page 109
“Whodowepartnerwith?”
Source:AdaptedfromAlexOsterwalder
Page 110
Thiscanapplytointernalprojects!
Source:AdaptedfromAlexOsterwalder
Page 111
ThiscanbeanInternalUserorStakeholder
Source:AdaptedfromAlexOsterwalder
Page 112
ThiscanbeanInternalProduct orB2BSolution.
Source:AdaptedfromAlexOsterwalder
Page 113
ThesecanbeInternalCostsandMetrics.
Source:AdaptedfromAlexOsterwalder
Page 114
ThesecanbeInternalPartnershipsacrossFunctionalDepartments
Source:AdaptedfromAlexOsterwalder
Page 115
Bonus:CollaborationPrinciples
Page 116
Ideas Decisions
Principle:DivergethenConverge
DivergeBrainstormingObservations
ConvergeInsights
Conclusions
Setup Goal
Page 117
Principle:Small,Large,Small
Individuals
SmallGroups
LargeGroup
MostDecisions
}
Page 118
Principle:Multi-channelInteraction
Sub-Group
Sub-Group
Sub-Group
Sub-GroupSub-Group
Page 119
Principle:Self-organization
Meetingself-organizationisabout:
•Allowingtheattendeestodecide‘how’theworkofthemeetingwillbedone•Allowingtheattendeestochoosetheirworkinthemeeting,ratherthanpre-assignit•Attendeesdecidehowtheywillrespondtotheirgivenobjectivesandenvironment•Managers&Leaderscaninfluencetheobjectivesandenvironmentofthemeeting
Page 120
<FooterContent:PresentationTitle,PartnerName,Other> 120
Thankyou!solutionsiq.com/1.800.235.4091