a game without thrones

28
GAME GAME An Agile Orga n i zat ion built from Lego An Agile Orga n i zat ion built from Lego # # without without

Upload: peter-merel

Post on 22-Jan-2017

213 views

Category:

Business


1 download

TRANSCRIPT

Page 1: A Game Without Thrones

GAME GAME

An Agile Organization

built from Lego

An Agile Organization

built from Lego

##withoutwithout

Page 2: A Game Without Thrones

〉No Command & Control〉Collaboration Loop Limit = 4〉Maximum Meeting Size = 6

What’s the difference between Agile

Organization and some other kind?

Page 3: A Game Without Thrones

〉Noble houses can’t build; they’re busy fighting〉Wildlings barter engineering to avoid fighting〉Wildlings work as a holarchy, not a hierarchyQuestion:

Why would Wildlings

build a Castle?

Answer:

No one else can

Page 4: A Game Without Thrones

〉5-person squads〉Each member has a different chapter〉Each squad has a different name

Thenns, Giants, Frozen Shore, Ice River Clan, Cave People …

Squads

Page 5: A Game Without Thrones

〉Chapters cross-link the squads

The Artist: metric is geometric and scale symmetry. Focuses breadth-first, never losing sight of the whole.

The Architect: metric is enclosed volume. Focuses on reusable practices, tools and building techniques

The Coach: metric is balance – the multiple of all the other metrics. Focuses work on the current bottleneck.

The Merchant: metric is # of different rooms. Focuses design on experiences of high-born lords and ladies

The Maester: metric is sturdiness. Integrity vs winter, wobbles and walkers. Focuses on root causes.

Chapters

Page 6: A Game Without Thrones

Five minutes per ceremony

〉Sprint: build a new castle feature!〉Chapter Meeting: coordination between squads〉Refactoring: integrate features into the castle〉Retro: improve workflow & accept/reject treaties

The Small Council meets during Refactoring

Our FourCeremonies

Page 7: A Game Without Thrones

〉Chapter Meetings each pick a leader, Roshambo〉Leaders form a Small Council per release cycle 〉Resolves cross-cutting concerns & feature priorities

The Small Council

Page 8: A Game Without Thrones

〉 Squads make decisions by unanimous consensus〉Unless the Coach says that’s taking too long – if so:〉 The Coach taps the role that best fits the decision〉The Coach never makes the decision themselves

Leadership as a Service

Page 9: A Game Without Thrones

Brainstorm & Prototype Castle Layout

〉Work in your own area: don’t attempt to refactor your work with the other squads yet!

〉Autonomy: focus on getting efficient workflow into your own squad during the sprint

〉Non-interference: don’t worry about what the other squads are doing yet

SprintZero

Page 10: A Game Without Thrones

Chapter Meetings:Proposing Treaties as

Pairs of Stories:

As the Crows …In order to open Castle Black …

We want allies against the Walkers …

As the Frozen Shore Clan ...In order to survive the Winter ...

We want a farm south of the Wall ...

Page 11: A Game Without Thrones

Refactoring &Small Council

While the Small Council prioritizes …

The rest of us refactor our work into

the Castle

Page 12: A Game Without Thrones

Squad Retros:Reject or Accept Treaties

and Council Stories!

As the Crows …In order to open Castle Black …

We want allies against the Walkers …

As the Frozen Shore Clan ...In order to survive the Winter ...

We want a farm south of the Wall ...

Also identify & fix squad workflow problems

Page 13: A Game Without Thrones

Implement accepted Treaty/Council stories

〉Work in your own area: don’t attempt to refactor your work into the Castle yet!

〉Autonomy: focus on improving your own metric for your own squad during this sprint

〉Non-interference: don’t worry about what the other squads are doing yet

SprintOne

Page 14: A Game Without Thrones

Chapter Meetings:Proposing Treaties as

Pairs of Stories:

As the Crows …In order to open Castle Black …

We want allies against the Walkers …

As the Frozen Shore Clan ...In order to survive the Winter ...

We want a farm south of the Wall ...

Page 15: A Game Without Thrones

Refactoring &Small Council

While the Small Council prioritizes …

The rest of us refactor our work into the

Castle

Page 16: A Game Without Thrones

Squad Retros:Reject or Accept Treaties

and Council Stories!

As the Crows …In order to open Castle Black …

We want allies against the Walkers …

As the Frozen Shore Clan ...In order to survive the Winter ...

We want a farm south of the Wall ...

Also identify & fix squad workflow problems

Page 17: A Game Without Thrones

Implement accepted Treaty/Council stories

〉Work in your own area: don’t attempt to refactor your work into the Castle yet!

〉Autonomy: focus on improving your own metric for your own squad during this sprint

〉Non-interference: don’t worry about what the other squads are doing yet

SprintTwo …

Page 18: A Game Without Thrones

Chapter Meetings:Proposing Treaties as

Pairs of Stories:

As the Crows …In order to open Castle Black …

We want allies against the Walkers …

As the Frozen Shore Clan ...In order to survive the Winter ...

We want a farm south of the Wall ...

Page 19: A Game Without Thrones

Refactoring &Small Council

While the Small Council prioritizes …

The rest of us refactor our work into the

Castle

Page 20: A Game Without Thrones

Squad Retros:Reject or Accept Treaties

and Council Stories!

As the Crows …In order to open Castle Black …

We want allies against the Walkers …

As the Frozen Shore Clan ...In order to survive the Winter ...

We want a farm south of the Wall ...

Also identify & fix squad workflow problems

Page 21: A Game Without Thrones

〉eXponential return〉 Simple design〉 Continuous throughput〉 Autonomous teams〉 Learning: triple loop〉 Ecosystems thinking

www.xscalealliance.org

What’s the difference between Agile

Organization and some other kind?

Page 22: A Game Without Thrones

〉Products are service ecosystems〉Product return curves are sigmoids〉Don’t chain the curves; stack them

eXponentialreturn

Page 23: A Game Without Thrones

〉Design means the elegance of minimum〉Not look and feel; how the ecosystem works〉Design, Delivery & Devops hand-in-glove

Simpledesign

BUILDLEARN

MEASURE

TESTS

DATA CODE

REFACTOR

Page 24: A Game Without Thrones

〉At one time there’s one bottleneck constraint〉Work on other constraints is premature〉Because it won’t increase Throughput

Continuousthroughput

Throughput

Page 25: A Game Without Thrones

〉Self-managing teams don’t have masters〉Self-aligning streams don’t have owners〉Leadership as a Service + Chapter Meetings

AutonomousTeams

Page 26: A Game Without Thrones

〉Learning What, How & How to learn How〉Self-Organizing Transformation: Steel Threads〉Continuous Delivery x Continuous Innovation

triple loopLearning

Page 27: A Game Without Thrones

Ecosystemsthinking

〉Ecosystems are networks of mutual benefit〉Whole board: think globally, act locally〉Avoiding hill-climbing: iterative and reductive

Page 28: A Game Without Thrones

GAME GAME

An Agile Organization

built from Lego

An Agile Organization

built from Lego

##withoutwithout