Using the Product Wall Release Workshop

8/10/2019 Using the Product Wall Release Workshop

1/109

2014 BigVisible Solutions, Inc. All Rights Reserved 2014 BigVisible Solutions, Inc. All Rights Reserved

!"#$% '() *+,-./' 0122

3)2)1") 0,+4"(,5

!"#$%&'%( *+,& -#.#,% (, ./+#%( 0123",$.

4+'/1+'5 *,+ !$#"' 6,,(. 789:

;< !"1% =1


2/109



3/109


Product Wall Release Workshop


4/109


5/109


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 linkedAgile Teams AllMembers

Product Management

Subject Matter Experts Marketing, Leadership, Operations,

Support, Others

Users


6/109


Why?

30-100 people for 2-3 days!


7/109 2014 BigVisible Solutions, Inc. All Rights Reserved 2014 BigVisible Solutions, Inc. All Rights Reserved

Common Costly Misalignment

Success



Establish Valuable Alignment

Success



5 Levels of Agile Planning

ProductVision

Road Map

Release

Sprint

Daily



BV Product Ecosystem



Product Strategy



Customer Research



Product Discovery



Product Planning



Product Development



Product Delivery



Ongoing (Constant) Feedback



All In One Workshop

Product

Vision

Road Map

Release

Sprint

Daily

Product WallRelease Workshop



Vision Creation

Workshop Activities



Vision Creation

Business Model Canvas

Workshop Activities



Vision Creation

Road Map Creation


Workshop Activities



Vision Creation

Road Map Creation

Persona Creation


Workshop Activities


23/109


Vision Creation

Road Map Creation

Release Vision Creation

Persona Creation


Workshop Activities


24/109


Vision Creation

Road Map Creation


Persona Creation

User Story Mapping


Workshop Activities


25/109


Vision Creation

Road Map Creation


Persona Creation

User Story Mapping

Product Wall Creation


Workshop Activities


26/109


Vision Creation

Road Map Creation


Persona Creation

User Story Mapping


Sprint Story Planning


Workshop Activities

L l f A il Pl i


27/109


Levels of Agile Planning

Vision Creation

Road Map Creation


Persona Creation

User Story Mapping




Product

Vision

Road Map

Release

Sprint

Daily


28/109


Activity: Vision Creation

Vi i C ti


29/109


Vision Creation

A computer on every deskand in every home.

Bill Gates, 1980 E l Vi i El t Pit h


30/109


Example Vision as Elevator Pitch

G ff M El t Pit h


31/109


Geoffrey Moores Elevator Pitch

FOR WHO

THE

IS A THAT

UNLIKE

OUR PRODUCT From Geoffrey Moore, Crossing the Chasm

HOW Vi i E i


32/109


HOW: Vision Exercise

If a product vision already exists, use it!

Have CEO or a Product Managementleader present it

20 minutes, at most

If creating one, introduce the elevator pitchformat

Have Product Management lead

discussion to fill in the format 20 minutes, at most


33/109


Activity: Business Model Canvas

B i M d l C


34/109




35/109


36/109


What are theelementsthat

make up a

businessmodel?


37/109


CustomerSegment

For whom are we creating value?

Source: Adapted from Alex Osterwalder


38/109


ValueProposition

What value do we deliver to the

customer?



39/109


Channels

How do we deliver the value we

create to the customer?



40/109


CustomerRelationships

How do we create & maintain

relationships with ourcustomers?



41/109


42/109


CostStructure

How much will this cost to create

and maintain?



43/109


KeyResources

Who and what will we need to

create this value?



44/109


KeyActivities

What will we do with these

resources to build value?



45/109


KeyPartners

Who would we partner with that

will provide us with KeyResources or Key Activities?


HOW: Build BMC Exercise


46/109


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 themon 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


47/109


? ? ???

?

??

?

?

??

Lets map out our existing business model


tip: tell a story


48/109


49/109


? ? ???

?

?

?

??

What need of theirs do we solve?



50/109


? ? ???

?

?

??

How do we deliver our solution to them?



51/109


? ? ???

?

??

How do we build relationships with them?



52/109


??

?

??

How do we make money delivering this

value?



53/109


?

??

What does this cost us to build &

maintain?



54/109


??

Who & what do we need to create this?



55/109


?

What activities do these resources

perform?



56/109


Who do we partner with?



57/109


This can apply to internal projects!



58/109


This can be anInternal User

orStakeholder



59/109


This can be anInternal

ProductorB2B Solution.



60/109


These can be InternalCosts and Metrics.Source: Adapted from Alex Osterwalder


61/109


These can be

Internal

Partnerships

across

FunctionalDepartmentsSource: Adapted from Alex Osterwalder


62/109


Activity: Road Map Creation

Road Map Creation


63/109


Road Map Creation

HOW: Create The Road Map


64/109


HOW: Create The Road Map

Before the workshop, help Product

Management define main Epics or featuregroups 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


65/109

Persona Creation


66/109


Persona Creation

Data Persona


67/109


Data Persona


68/109

HOW: Create Personas


69/109


HOW: Create Personas

If you already have personas, use them

Existing personas can be explained andrefined

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


70/109


Activity: Release Vision Creation



71/109



FOR

WHO THE

IS A

THAT

UNLIKE

OUR PRODUCT

From Geoffrey Moore, Crossing the Chasm

FOR

WHO

THE

IS A

THAT

UNLIKE

OUR PRODUCT

From Geoffrey Moore, Crossing the Chasm

FOR

WHO

THE

IS A

THAT

UNLIKE


FOR

WHO

THE

IS A

THAT

UNLIKE


HOW: Create Release Vision


72/109


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


73/109


Activity: User Story Mapping

User Story Mapping


74/109


y pp g

Release Slices


75/109


Identify releases in a Story Map by slicing horizontally

time

optionality

necessary

lessoptional

moreoptional

first release

second release

third release

Source: Jeff Patton. An Introduction to User Story Mapping

User goals


76/109


77/109


Activity: Product Wall Creation



78/109


Teams, Dependencies, State


79/109


, p ,

Product Wall Build


80/109


Product Wall Grid


81/109


Sprints

FeatureGro

upLane

s

HOW: Create The Product Wall


82/109


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 guessat 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


83/109


Activity: Sprint Story Planning



84/109


p y g

Sprint Story Planning Cycle


85/109


p y g y

HOW: Sprint Story Planning


86/109


y g

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 andthe 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


87/109


Sample Agenda

HOW: Sample Workshop Agenda


88/109


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



89/109


Workshop - Tuesday


9:00 - 9:15 Opening

Introductions. Schedule and objectives for the day. Review ofthe release cadence (sprints) and iteration calendar, planning

rules and expectations.

9:15 - 9:45 Release Vision

Release Vision presentation by Executive and ProductManagement

9:45 - 10:15

Review Business ModelCanvas

Present and review the Business Model Canvas created byProduct 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 Doneand 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 eachproduct area. This is the top line of the User Story Map

3:15 - 3:30 Break

3:30 - 3:45

Introduce User StoryMaps

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 Maparea.

4:45 - 5:00 Review the day

Review the accomplishments of the day. Preview of tomorrow.Handle questions



90/109


Workshop - Wednesday


9:00 - 9:15 Opening Schedule and objectives for the day.

9:15 - 9:45Vision and Personareview Evaluate if the vision still fits and makes sense. Check thepersonas 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 forimportance and define

release content slicesAdjust the vertical information of the maps to defineimportance 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 Check

Faciliator asks for fist of five "confidence factor" Definition ofDone reminder

2:15 - 2:30 Break

2:30 - 2:45

Intro to Sprint StoryPlanning 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



91/109


Workshop - Thursday


9:00 - 9:15 Opening

Schedule and objectives for the day. Have Sprint 1 tasked andready!

9:15 - 9:45 Product Wall Review Referencing the vision, personas, etc., review the Product Wall


10:45 - 11:00 Confidence Check Faciliator asks for fist of five "confidence factor"


12:00 - 1:00 Lunch





3:30 - 4:00

Update Product Wall andPresent Sprint Plans

Each team presents their plans tasked out plans for Sprints 1-2and 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 aProduct Box"

4:30 - 5:00

Retrospective of theworkshop Retrospective of the workshop. How did it work for us?


92/109


Ongoing Product Wall Use

Product Wall Location


93/109


Scrum of Scrums


94/109


Scrum of Scrums


95/109


Now In Sprint 2


96/109


HOW: Scrum of Scrums


97/109


Two or more times per week a Scrum of

Scrums takes place in front of The ProductWall

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


98/109


Own and Improve

Increase Team Visibility


99/109


Tags to Color and Shapes


100/109


HOW: Own The Product Wall


101/109


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

Acknowledgements


102/109


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_backlog.html

Product Wall: Inspired by Tom Looy,

agileatlas.org/articles/item/the-great-wall-scaling-agile-on-a-multi-team-project

Awesome clients that build things!


103/109


?


104/109

Alan DayleyAgile Coach

CSM, CSPO, CSP, SAFe [email protected]

http://bigvisible.com/author/adayley

@DayleyAgile

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


105/109


Bonus: Collaboration Principles

Principle: Diverge then Converge


106/109


Ideas Decisions

Diverge

Brainstorming

Observations

Converge

Insights

Conclusions

Setup Goal

Principle: Small, Large, SmallL G


107/109


Individuals

Small Groups

Large Group

MostDecisions

}

Principle: Multi-channel Interaction


108/109


Sub-Group

Sub-Group

Sub-Group

Sub-GroupSub-Group

Principle: Self-organization


109/109

Meeting self-organization is about:

Allowing the attendees to decide how thework 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 theobjectives and environment of the meeting

Using the Product Wall Release Workshop

Documents

Transcript of Using the Product Wall Release Workshop