Close the Loop! - facilitatingagility.files.wordpress.com · Close the Loop! Simplifying A3...

Close the Loop!

Simplifying A3 Thinking for Team Retrospectives

Cara Turner South Africa

Agile Coach | User Group Chairman | Facilitation Fanatic

Close the Loop! Simplifying A3 Thinking for Team Retrospectives

Who’s doing TDD?

Why define tests before you start?

What is Continuous Improvement?

… Some Questions …


INSPECT

ADAPT


How do we do that?

Scientific method

Retrospectives

A3 Thinking / Kaizen


Assess implications Look clearly

Implement Experiment

Formulate an idea

The Improvement Process

Question and analyse

Check results

?


A3 Thinking & Kaizen

Kaizen Memo – individuals, small

Cre

dit

: Cla

ud

io P

err

on

e


A3 Report – organization level



? Teams



Product Environment

Where are we now?

Team Factors

Product Factors

Technical Factors

Org Factors

Current State


Product Environment

Where should we be?

Team Factors

Product Factors

Technical Factors

Org Factors

Current State


Product Environment

Where should we be?

Team Factors

Product Factors

Technical Factors

Org Factors

Target Condition


The Simulation

Creating & reviewing an experiment

Before & After Retrospectives

(not the sprint)

Simulation Agenda Study the problem

Retro 1: Define a goal … as an experiment

“By [doing something], we expect [this result]”

Implement the goal

What happens in our Sprint

Retro 2: Review the goal

What happened? What did it change?

? Reflect

On the experiment

What are the factors influencing it?


The Product


The Context

Product, Technical, Team & Organisation Factors

+ Last Sprint


Retrospective 1

Study the problem

Create a testable hypothesis


Study the Problem Look clearly

Product, Technical, Team & Organisation Factors

+ Last Sprint


What Influences Change?

What will accelerate the rate of change? e.g. resolve impediments escalating requirements

What will reduce the rate of change? e.g. stabilize code base discover impediments



Set the Direction

define a Target State (the long term ideal)

describe a Current State (the problem we have now)



Target State: Never have more than two open bugs

Example: Current / Target

Current State: The number of bugs is affecting our velocity, so we need to improve quality across the board


The Retrospective Goal

“Pair Program on Integration Stories”

Formulate an idea

Short-term goal for the next sprint only


Target > Goal Formulate

an idea


Do Science! Hypothesis

“By [doing something] we expect [this result]”

Pass Conditions /

/ Fail Conditions

(we try it and we’re right)

(we try it and we’re wrong)

Formulate an idea


Target > Goal Formulate

an idea


Target > Goal > Hypothesis Formulate

an idea


Write a Goal hypothesis

“By [implementing our goal] we expect [this result]”

Pass Conditions /

/ Fail Conditions

(we try it and we’re right)

(we try it and we’re wrong)

Formulate an idea


Example: Hypothesis

By: sharing domain knowledge and technical skill while coding

Current State: The number of bugs is affecting our velocity, so we need to

improve quality across the board

We expect: to improve our code quality and decrease the number of bugs

Pass Condition: We note improvements and discoveries while pair programming, and our bug count decreases

Fail Condition: We pair program but there are still many new bugs being generated


“Real Life”

The sprint’s events

How your goal is affected


Week 1

The development manager expresses interest in your progress

You discover a dependency on another team’s architect



Week 2

While grooming you discover a potentially large change that affects many

stories in the backlog

An integration issue takes 2 days to resolve



Week 3

The dev manager is unhappy that you’re interrupting the

architect’s team

You make a breakthrough with an architecture change



What happened… The development manager expresses interest in your progress

Accelerates change You hope the Dev manager will use your experiment to sell pairing to all the teams

You discover a dependency on another team’s architect

Decelerates change You invite her to pair with your team members

Goal Progress:

Pairing has started, but not as you expected



What happened (2) While grooming you discover a potentially large change that affects many stories in the backlog

Accelerates change You have to re-plan your release, and you need more time from the architect.

An integration issue takes 2 days to resolve

Decelerates change Your team slows down, but everyone learns a lot about your integration challenges

Goal Progress:

Pairing on integration issue improves knowledge



What happened (3)

The dev manager is unhappy that you’re interrupting the architect’s team

Increases pressure You discuss ways to work with her team in return

You make a breakthrough with an architecture change

Accelerates change Take this into Release Planning, and thank the architect for all her help

Goal Progress:

Pairing has helped you resolve a difficult problem



Retrospective 2

Study the results

Review your hypothesis


What happened…

You’ve missed your sprint

You have to re-plan your

release The architectural breakthrough will help save time

You had to deal with some

organization dynamics

Check results

You did manage to pair quite a

lot

Review your Experiment

“By doing [something] we expect [this result]”

Were our assumptions correct?

Assess implications

Pass Conditions / / Fail Conditions Which of these did we see? What does that tell us?


Example: Hypothesis

By: sharing domain knowledge and technical skill while coding

Target State: Never have more than two open bugs

We expect: to improve our code quality and decrease the number of bugs

Pass Condition: We note improvements and discoveries while pair programming, and our bug count decreases

Fail Condition: We pair program but there are still many new bugs being generated

Not clear yet

Our goal didn’t focus on bug counts



“By doing [something] we expect [this result]”

Were our assumptions correct?

Assess implications

Pass Conditions / / Fail Conditions Which of these did we see? What does that tell us?



How much closer are we

to our Target state?

What might we need to adjust to get there?

Assess implications


Share with the team next to you

2 minutes each way

and then we’ll debrief



What adjustments do we need

to get to our Target state?

What discoveries did you make?


The End Almost


debrief

How do tests help us?

How does reviewing both the outcome and the test, change how we think about improvements?

How can we bring this into our retrospectives?


The End Really

Thank You.


Cara Turner Cape Town, South Africa

Get in Touch

krs.co.za sugsa.org.za

twitter: @cara_faye facilitatingagility.com

Close the Loop! - facilitatingagility.files.wordpress.com · Close the Loop! Simplifying A3...

Documents

Transcript of Close the Loop! - facilitatingagility.files.wordpress.com · Close the Loop! Simplifying A3...