Download - Why and How to Run a Large Distributed Team Retrospective

Transcript
Page 1: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 1

Large Distributed Team Retrospectives

See also: http://www.innovationgames.com/2014/06/how-to-run-huge-retrospectives/

Page 2: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 2

About Conteneo

Conteneo is aCollaboration Amplification company.

Grounded in the science of play, our enterprise software and professional services merge serious games, domain expertise and collaboration leadership to super power teams to achieve Epic Wins.

Page 3: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co

Retrospecting Retrospectives

+ Δ

Page 4: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co

Retrospective Outcomes / Impact

What is the impact or outcome over time? Augment your graph with specific changes you’ve made.

time

impact

low

high

Page 5: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co

Retrospective Outcomes / Impact

time

Impact / Benefit

high

low

EarlyAdoption

Team Maturation

OrganizationalLimits

WhyBother?

Page 6: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co

Exploring Your Frame

What was the “scope” when you answered this question? (e.g., a single team or ?)

Page 7: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co

Design Challenge

Design an effective retrospective for 30 Scrum teams in three locations.

Constraints: You do not have enough budget to fly everyone to the same location.

Page 8: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co

Agenda

• Motivations for Enterprise Retrospectives• Process Overview• Expected Results• Expect Actions

Page 9: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co

You have many Agile teams.

To improve performance of the enterprise you need to conduct an enterprise retrospective – not just one team – but every team.

Improving Enterprise Performance

Page 10: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co

Traditional retrospectives focus on a single, co-located team.

They can produce results that improve the performance of the team, but often fail to address the needs of the enterprise – the issues affecting multiple teams or beyond the scope of control of any single team.

Single Team Retrospectives

Image Credit: http://www.cornetdesign.com/images/AgileRetrospectives_134B2/IMG_0016.jpg

Page 11: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 11

Collaboration is…

Pretty easy for small teams…

Pretty hardfor large distributed teams!

Page 12: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 12

Collaboration is Hard for Large Teams Because

Serious Games that Amplify Collaboration. • Meetings

• Email threads

• Video conferencing

• Surveys

Success

We mistake communication for collaboration!

Page 13: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 13

Games are the Ideal Collaboration Tool!

Goals Constraints Rules Voluntary Participation

Page 14: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 14

Conteneo’s Games Scale to Large Teams

San José, CA Budget Games

Page 15: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 15

We Need Online Retrospectives

Speed Boat is a well-known retrospective technique in which teams collaboratively identify the anchors slowing them down.

Playing Speed Boat online and at scale, we can efficiently conduct an Enterprise Retrospective.

The result? An Epic Win!

Page 16: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 16

Setting Scope

We have found success in setting scope as follows:

Time Scope: Last 6 months or last release, whichever is greater

Process Scope: The complete development process from story creation, through development and into production deployment (release to customer).

Page 17: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 17

Step 1: Identify the Teams

We identify the teams and the facilitators.

Page 18: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 18

Step 2: Conduct Retrospectives

We schedule and conduct online retrospectives using Speed Boat.

Anchor: ImpedimentPropeller: Good Stuff

Placement indicates how bad or how good.

The number of items is shared among all players.

Good

Really Good

Somewhat Bad

Bad

Really Bad

Page 19: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 19

Step 3: Analyzing Results

We download the results of all games to categorize each of the ideas.

Categorize Each Idea

Create Project

Describe Features,Benefits and

Price

Team & Enterprise Projects

Page 20: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 20

Categorize: People, Process, Technology

People

Tools / TechnologyProcess

“We should use GitHub”

“My PO doesn't attend planning meetings”

“We aren’t clear on the meaning of Done, Done”

Page 21: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 21

Categorize: Scope of Control

“We should use GitHub”

“My PO doesn't attend planning meetings”

“We aren’t clear on the meaning of Done, Done”

We use Diana Larsen’s Circles and Soup framework to help analyze results. This helps

This is also an excellent online retrospective tool!

www.innovationgames.com/circles-and-soup

Page 22: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 22

Scope vs. PPT Scatter Plot

Teams identified positive and negative feedback

about evenly.

Significant opportunities for highly

impactful improvements.

Page 23: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co

Keep Doing Good Stuff – Address Oppty

Page 24: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 24

Creating Projects

We create projects to address the impediments.

Entire project list.

Team projects.

Enterprise projects.

Page 25: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 25

Selecting Projects

• Management reviews our results.

• Projects are selected and engaged. • Some projects may be just “approved”. • We may play additional Innovation Games® such as

Buy a Feature to help in the selection of the projects.

Page 26: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 26

Sharing Results

• Results are shared with the team members.

• This may be through• Senior Leaders• Scrum Masters

• We want the participants to know they’ve been heard and that we’ll be acting on the results.

Page 27: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 27

Time Estimates

Planning / Goal Setting2-3 weeks

Game Play1 week

Post-Processing2-3 weeks

Projects? 1- 5 months

Page 28: Why and How to Run a Large Distributed Team Retrospective

www.conteneo.co © Copyright 2014 Conteneo, Inc. 28

Luke HohmannFounder & CEO, Conteneo, Inc.

480 San Antonio Road, Suite 202Mountain View, CA 94040mobile: (408) [email protected]