The Rise of the TeamsAhmad Fahmy @z2ahmadahmad@z2consulting.com

Dan North @tastapod 1. Care about the audience. What do you want them to do differently? 2. Have a narrative arc, not just "info". 3. Enjoy yourself!

Gone in

60

seconds

The rise of the team

•Forming self managing teams•Unfreezing •Disrupting•Learning new behaviors(e.g. working together, understanding the business, quality)

What happens next…

This is awesome!

What do all the managers do?

Everything begins to

slows down…

J-Curve(s)

Pune

•Managers to leaders•Creating a sense of urgency•Solving system wide problems and opportunities•The BDC workshop

A simple

pattern…influenced by

many things1)Create a near term goals

2)Gather behavior stories

3)Derive meaningful behavior changes

4)Generate experiments

5)Inspect and adapt at short intervals

ahmadfahmy.com

Create a near term

goals

[The goal] from [x] to [y]

in the next 6 | 12 months

[Reduce the release sprint] from [4 weeks] to [2 weeks]

[ability to push to production] from [once a day] to [intraday]

[Reduce total cost of ownership] from [$2/trade] to [$1/trade]

[rationalize settlement systems] from [8] to [7]

[Run the dover half marathon] in the next

Gather behavior

stories

In order to achieve [GOAL] the [x TEAM] stop [BEHAVIOR] [IMPACT]

the [y TEAM] stop [BEHAVIOR] [IMPACT]

the [z TEAM] stop [BEHAVIOR] [IMPACT]

• The [technology organization] [needs to stop writing crap code] [so the product team doesn't have to manually test for a month]

• The [business/product team] [need to figure out what they want so they can stop changing their minds at the last minute and [pushing out the delivery]

• The managers should stop poking their nose into what we are doing at the last minute so we can get stuff done

• The technology organization needs to stop padding their estimates so we can understand what is really going on

Derive meaningful

behavior changesthe [PRODUCT ORGANIZATION/DEVELOPMENT TEAMS] NEED TO HAVE A MORE COLLABORATIVE REQUIREMENTS PROCESS

the [DEVELOPMENT TEAMS] NEED TO STOP AND FIX DEFECTS

Generate experiments

• [Create a workshop to review all manual regression and create an

“eliminate/automate” list [HIGH IMPACT, YES]

• off site to create a Product backlog (Low effort /High impact) [HIGH/YES]

• [Automate all regression tests][HIGH/NO]

• [Replace requirements documentation with User Stories/SBE] [HIGH/YES]

[Experiment][ impact high | medium | low][doable in a month or less y | n]

ahmadfahmy.com

Do these !

Do these second Kill these

HIG

H

EF

FO

RT

LO

W

EF

FO

RT

HIGH

IMPACT

LOW

IMPACT

eff

ort

impact

Inspect and adapt

every at short/regular

intervalsInspect the data.

did the good habit stick?

did the bad habit stop?

did the big bang have the desired result.

Celebrate successes

How long does it take

for an organization to

self organize?

Interested in more?

Email “+1” toahmad@zone2consulting.com

@z2ahmad

I see waste

Scale

London NYC/NJ Chicago

• Began in 2011• Large financial

*services* institution• 7 Cities• 60+ teams (500+

People)

• Focus on education first. CSM, Lean, CleanCode, etc

• Invest in engineering & CI capability up front

• Team self selection• Co-Location• Feature team self managed• Focus on visual management and

lean principles• No ScrumBut baked in at the start• We set out to do this right• Many successes & some failures• 100’s of lessons

Adoption ApproachBackground

Business

Management

Business

Analysts

Project

Management

QAComponent Development Teams Architecture

Product

Owner

Feature team

Feature team

Feature team

Why are Agile adoptions so difficult

Lipstick on a pig adoptions

Business

Management

Business

Analysts

Project

Management

QAComponent Development Teams Architecture

• True agile adoptions are about changing culture. There is nothing harder.

• You are giving true transparency where there once was magic.

• You are giving developers greater accountability where they were once told what to do

• Ignore at your own peril• Cypher vs Mr Smith vs Mr Anderson

Lesson 1 You are changing culture not process

Lesson 2 Eat your own dog food

Agile

1. Create a team2. Create a backlog of the

organization3. Pick the right slice4. Ready for sprint. The red

pill test5. Define the problem you

are trying to solve.6. Pick the right

methodology for the problem

7. Create a definition of done. (e.g. 3 successful sprints releasing valuable high quality code)

8. Create success early. This creates pull.

• Doing Scrum/Kanban are not wins. Shipping software is. Don’t declare success too early

• Billy Bean introduced a new way of selecting players and was shunned by the baseball establishment

• 20 game win streak despite having one of the lowest pay rolls in the industry

• Changed the way baseball is played

Lesson 3 Get *real* wins early

Lesson 4 Hire the best

• Process is not enough• Hire the best engineers• Hire great product people• Hire great coaches

@fahmyboy or contact@ahmadfahmy.com