Presented by - Schedschd.ws/hosted_files/agile2016/f9/UsingTheProductWallRelease...• Connections between functional skills and ... Business Model Canvas Workshop Activities. Product

Copyright©2015SolutionsIQInc.Allrightsreserved.

6801185thAveNE,Suite200Redmond,WA98052solutionsiq.com1.800.235.4091

CreatingAlignmentwithTheProductWallReleasePlanningWorkshop

PresentedbyAlanDayleySeniorAgileCoachadayley@solutionsiq.com

Agile2016– 25July2016

ProductWallReleasePlanningWorkshop

ProductWallCreatedLive

CreatedByEveryone

Prominent,VisibleLocation

ContinuousCollaboration

WhyPlanThisWay?

CommonCostlyMisalignment

Success

EstablishValuableAlignment

Success

HOW:ConditionsandParticipants• Releasetimeframeofsixmonthsorless• Schedule2-3days• 30-100people

• Workingonsameproduct,samecodebaseorotherwiselinked

• AgileTeams– AllMembers• ProductManagement

• SubjectMatterExperts• Marketing,Leadership,Operations,Support,Others

•Users

• Clarityofproductpurpose• Dependenciesvisible• Sharedownershipofresults• Sharedunderstandings• ReadytouseSprintPlans• Connectionsbetweenfunctionalskillsanddepartments

• Viewofproductpossibilities• Refinedbacklog• Fun

ExpectedResults

Why?

30-100peoplefor2-3days!

WorkshopIncorporatesaCompleteAgileProductEcosystem

5LevelsofAgilePlanning

ProductVision

RoadMap

Release

Sprint

Daily

ProductEcosystem

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

ProductStrategyWhatarethe

problemswearesolving?Product

Discovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

CustomerResearch

OngoingFeedback

CustomerResearchWhoareour

customersandwhatare

theirneeds?

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

OngoingFeedback

Whatarethe

outcomesweneedto

achieve?ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

ProductDiscovery

Whatisthe

minimalviable

productforoutcomes?

ProductDiscovery

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

ProductPlanning

Whatisthe

workneededtobuildour

product?

ProductDiscovery

ProductPlanning

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

ProductDevelopment

Whenwillwe

deliverproduct

increments?

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductStrategy

CustomerResearch

OngoingFeedback

ProductDelivery

Howwillwe

stayfocusedand

coordinated?

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

Ongoing(Constant)Feedback

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

ProductVision

RoadMap

Release

Sprint

Daily

AllInOneWorkshop

ProductWallReleasePlanningWorkshopActivities

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

VisionCreation

WorkshopActivities

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

VisionCreation

BusinessModelCanvas

WorkshopActivities

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

VisionCreation

RoadMapCreation

BusinessModelCanvas

WorkshopActivities

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

VisionCreation

RoadMapCreation

PersonaCreation

BusinessModelCanvas

WorkshopActivities

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

VisionCreation

RoadMapCreation

ReleaseVisionCreation

PersonaCreation

BusinessModelCanvas

WorkshopActivities

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

VisionCreation

RoadMapCreation

ReleaseVisionCreation

PersonaCreation

UserStoryMapping

BusinessModelCanvas

WorkshopActivities

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

VisionCreation

RoadMapCreation

ReleaseVisionCreation

PersonaCreation

UserStoryMapping

ProductWallCreation

BusinessModelCanvas

WorkshopActivities

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

VisionCreation

RoadMapCreation

ReleaseVisionCreation

PersonaCreation

UserStoryMapping

ProductWallCreation

SprintStoryPlanning

BusinessModelCanvas

WorkshopActivities

VisionCreation

RoadMapCreation

ReleaseVisionCreation

PersonaCreation

UserStoryMapping

ProductWallCreation

SprintStoryPlanning

BusinessModelCanvas

ProductVision

RoadMap

Release

Sprint

Daily

LevelsofAgilePlanning

Activity:VisionCreation

VisionCreation

“Acomputeroneverydeskandineveryhome.”

BillGates,1980

ExampleVisionasElevatorPitch

GeoffreyMoore’sElevatorPitch

FOR<targetcustomer>WHO<statementoftheneed>THE<productname>ISA<productcategory>THAT<keybenefit>UNLIKE<primarycompetitor>OURPRODUCT<furtherdifferentiation>

From Geoffrey Moore, Crossing the Chasm

HOW:VisionExercise• Ifaproductvisionalreadyexists,useit!

• HaveCEOoraProductManagementleaderpresentit

• 20minutes,atmost• Ifcreatingone,introducetheelevatorpitchformat• HaveProductManagementleaddiscussiontofillintheformat

• 20minutes,atmost

Activity:BusinessModelCanvas

BusinessModelCanvas

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.

Whataretheelements thatmakeupabusinessmodel?

CustomerSegment

“Forwhomarewecreatingvalue?”

Source:AdaptedfromAlexOsterwalder

ValueProposition

“Whatvaluedowedelivertothecustomer?”

Source:AdaptedfromAlexOsterwalder

Channels

“Howdowedeliverthevaluewecreatetothecustomer?”

Source:AdaptedfromAlexOsterwalder

CustomerRelationships

“Howdowecreate&maintainrelationshipswithourcustomers?”

Source:AdaptedfromAlexOsterwalder

RevenueStreams

“Howmuchwillthesecustomerspayforthevaluewecreate?”

Source:AdaptedfromAlexOsterwalder

CostStructure

“Howmuchwillthiscosttocreateandmaintain?”

Source:AdaptedfromAlexOsterwalder

KeyResources

“Whoandwhatwillweneedtocreatethisvalue?”

Source:AdaptedfromAlexOsterwalder

KeyActivities

“Whatwillwedowiththeseresourcestobuildvalue?”

Source:AdaptedfromAlexOsterwalder

KeyPartners

“WhowouldwepartnerwiththatwillprovideuswithKeyResourcesorKeyActivities?”

Source:AdaptedfromAlexOsterwalder

HOW:BuildBMCExercise• Preparealarge,blankBusinessModelCanvasinadvanceandtapetothewall

• Tellthestoryofeachbox• Solicitstickynotestoputineachbox,eitherbyvoiceorbywritingtheironanplacingthemonthecanvas

• Fillineverybox• Usedifferentcolors,marks,etc.asneeded• Maytakeanhourtocomplete• Couldhavesmallerrepresentativeteamdoitbeforemainworkshop

Activity:RoadMapCreation

RoadMapCreation

HOW:CreateTheRoadMap• Beforetheworkshop,helpProductManagementdefinemain“Epics”orfeaturegroupsdesiredfortherelease• Theseareatahighlevelnottoomuchdetail• Basedonmarketresearch,customerinterviews,etc.

• Attheworkshopthedesiredfeaturegroupscanbepresentedandrefined

• TheRoadMapincludescurrentandnext2-3releases

Activity:PersonaCreation

PersonaCreation

DataPersona

EmpathyMap

ThinkandFeel?

Hear? See?

SayandDo?

Pain Gain

HOW:CreatePersonas• Ifyoualreadyhavepersonas,usethem

• Existingpersonascanbeexplainedandrefined• Splitintoad-hocpersonateams,onepersonaperteam

• BuildtheEmpathyMapforeachpersonawithinthead-hocteams

• Regroupandpresentcreationstoentiregroup• Alltakesupto1.5hours

Activity:ReleaseVisionCreation

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

HOW:CreateReleaseVision• ProductManagementreferencestheRoadMaptogivefeaturegroupstoeachteam• Collaborativelydecidewhichteamwilllikelyworkonwhichfeaturegroup

• SplitintoyourdefinedAgileTeams• Lookingattheirfeaturegroup,eachteamwritesandelevatorpitchforthatfeatureset

• ComebacktogetherandpresentReleaseVisionstoeachother

• Takes45minutes

Activity:UserStoryMapping

UserStoryMapping

IdentifyreleasesinaStoryMapbyslicinghorizontally

time

optio

nality

necessary

lessoptional

moreoptional

firstrelease

secondrelease

thirdrelease

Usergoals

ReleaseSlices

Source:JeffPatton.“AnIntroductiontoUserStoryMapping”

Abovetheline,ornot

HOW:CreateStoryMaps• Eachteamusestheir“Epics”orfeaturegroupsdesiredfortherelease

• Convertthefeaturegroupstousergoalsbyasking“Whatistheusertryingtoaccomplishwiththisnewfeature?”• ThesegoalsarethetoprowoftheStoryMap

• Startmakingactionstheuserwilltaketoaccomplisheachgoal

• HaveanexperiencedStoryMapfacilitator!• Thismappingtakesseveralhours

Activity:ProductWallCreation

ProductWallCreation

Teams,Dependencies,State

ProductWallBuild

Sprints

FeatureGrou

porEpicL

anes

ProductWallGrid

HOW:CreateTheProductWall• EachteampullsactionsfromtheStoryMaporwriteslargestoriesfromtheStoryMap

• Eachteam,allatthesametimeplacesthesecardsonTheProductWall• PlacementintoSprintsisa“gutfeel”guessatthispoint.

• Justlaythemout,makingandchangingcardsastheygo.

• Tagthecardstoindicateownerteamanddependencies

• Reviewtoeachothertheendresult

Activity:SprintStoryPlanning

SprintStoryPlanning

SprintStoryPlanningCycle

HOW:SprintStoryPlanning• EachteamreferencesthelargestoriesinTheProductWallSprint1column

• EachteamplansSprint1intheirusualway• Eachhour,allteamsreturntoTheProductWalltoupdatethecontentsofSprint1andtheStoryMaps

• ContinuethiscycleuntilTeamshaveSprint2planned

• NowplanSprint2,then3untiltimerunsout• TheProductWallReleaseWorkshopendswithteamsperformingthiscycle

ProductDiscovery

ProductPlanning

ProductDevelop-ment

ProductDelivery

ProductStrategy

CustomerResearch

OngoingFeedback

VisionCreation

RoadMapCreation

ReleaseVisionCreation

PersonaCreation

UserStoryMapping

ProductWallCreation

SprintStoryPlanning

BusinessModelCanvas

FinishWithReadySprintPlans

SampleAgenda

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

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

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

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?

Ongoing(Constant)FeedbackUsingTheProductWall

ProductWallLocation

ScrumofScrums

ScrumofScrums

NowInSprint2

HOW:ScrumofScrums• TwoormoretimesperweekaScrumofScrumstakesplaceinfrontofTheProductWall

• Eachteamselectsonepersontorepresenttheteamatthemeeting• Notalwaysthesameperson,rotate• Allmembersofallteamsarewelcometoattend,alongwithanyoneelseinterested

• Onlytherepresentativesspeak• Updatecards,highlightdependencies• TheScrumofScrumslasts15minutes

OwnandImprove

IncreaseTeamVisibility

TagstoColorandShapes

HOW:OwnTheProductWall• Talkaboutthevocabularyandrulesofthewall• Bringupimprovementideas

• Keepitassimpleaspossible• Keepitasusefulaspossible

• ChangestothewayTheProductWallworksshouldbemadecollaboratively

• Ifpeoplearenotusingit,thatisanindicatorthatimprovementsareneeded

• ScrumMasters watchforimprovementneeds

SelectExercises

VisionCreation

RoadMapCreation

ReleaseVisionCreation

PersonaCreation

UserStoryMapping

ProductWallCreation

SprintStoryPlanning

BusinessModelCanvas

• 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

?

AlanDayleySeniorAgileCoach

CSM,CSPO,CSP,SAFe Agilist

adayley@solutionsiq.com

http://www.solutionsiq.com/author/adayley/

@DayleyAgile

http://plus.google.com/+AlanDayley

HowtobuildaBusinessModelCanvas

? ? ???

?

??

?

?

??

“Let’smapoutourexistingbusinessmodel”

Source:AdaptedfromAlexOsterwalder

tip:tellastory

? ? ???

?

?

?

?

??

“WhoisourCustomerSegment?”

Source:AdaptedfromAlexOsterwalder

? ? ???

?

?

?

??

“Whatneedoftheirsdowesolve?”

Source:AdaptedfromAlexOsterwalder

? ? ???

?

?

??

“Howdowedeliveroursolutiontothem?”

Source:AdaptedfromAlexOsterwalder

? ? ???

?

??

“Howdowebuildrelationshipswiththem?”

Source:AdaptedfromAlexOsterwalder

??

?

??

“Howdowemakemoneydeliveringthisvalue?”

Source:AdaptedfromAlexOsterwalder

?

??

“Whatdoesthiscostustobuild&maintain?”

Source:AdaptedfromAlexOsterwalder

??

“Who&whatdoweneedtocreatethis?”

Source:AdaptedfromAlexOsterwalder

?

“Whatactivitiesdotheseresourcesperform?”

Source:AdaptedfromAlexOsterwalder

“Whodowepartnerwith?”

Source:AdaptedfromAlexOsterwalder

Thiscanapplytointernalprojects!

Source:AdaptedfromAlexOsterwalder

ThiscanbeanInternalUserorStakeholder

Source:AdaptedfromAlexOsterwalder

ThiscanbeanInternalProduct orB2BSolution.

Source:AdaptedfromAlexOsterwalder

ThesecanbeInternalCostsandMetrics.

Source:AdaptedfromAlexOsterwalder

ThesecanbeInternalPartnershipsacrossFunctionalDepartments

Source:AdaptedfromAlexOsterwalder

Bonus:CollaborationPrinciples

Ideas Decisions

Principle:DivergethenConverge

DivergeBrainstormingObservations

ConvergeInsights

Conclusions

Setup Goal

Principle:Small,Large,Small

Individuals

SmallGroups

LargeGroup

MostDecisions

}

Principle:Multi-channelInteraction

Sub-Group

Sub-Group

Sub-Group

Sub-GroupSub-Group

Principle:Self-organization

Meetingself-organizationisabout:

•Allowingtheattendeestodecide‘how’theworkofthemeetingwillbedone•Allowingtheattendeestochoosetheirworkinthemeeting,ratherthanpre-assignit•Attendeesdecidehowtheywillrespondtotheirgivenobjectivesandenvironment•Managers&Leaderscaninfluencetheobjectivesandenvironmentofthemeeting

<FooterContent:PresentationTitle,PartnerName,Other> 120

Thankyou!solutionsiq.com/1.800.235.4091