mission impossible - asqf€¦ · mission impossible ... 110 165 220 backlog and velocity 99 207....

Mission Impossible (great vision, no backlog - and a steady delivery?)

That is impossible by Tim Geers taken from Flikr is licensed under CC BY 2.0

Teahupoo - picture taken by an unknown photographer

Wer bin ich

Sven Winkler

seit gestern 34 Jahre

ISO Software Systeme

Agile Monday Nürnberg (XING)

Lean Coffee Nürnberg (XING)

Challenges

New functional scope

New technology

New team (new to Scrum)

New Product Owner

Distributes teams

Component teams

Consulting agency

Enterprise project

No backlog

Set up and constraints

Frascati Rugby by f/orme taken from Flikr is licensed under CC BY 2.0

1 Frontend team

1 ESB team (we)

1 Test team

Given backend systems (barely tested before)

7 Sprints

Yes, we do


But with component teams

Yet another waterfall by pfly taken from Flikr is licensed under CC BY 2.0

…and with a test team

Blue Ridge Waterfall by Forest Wander taken from Flikr is licensed under CC BY 2.0

nevertheless

Generated by wordle.net

http://wordle.net

First question

1. Did we deliver?

Delivery Man by garry knight taken from Flikr is licensed under CC BY 2.0

Yes, we did.

package! by lemon half taken from Flikr is licensed under CC BY 2.0

Velocity chartStory

poin

ts

0

10

20

30

40

Sprints

1 2 3 4 5

First things first

hurdles by ginnerobot taken from Flikr is licensed under CC BY 2.0

Contracts

Old Paperwork by Aviva West taken from Flikr is licensed under CC BY 2.0

Agile contracting

Also take a look at the book “Agile Contracts” by Boris Gloger

Scope creation


Our proposal


Checkpoints


2 Contracts

From my experience


The most important to me

Always start with a backlog

Write down your vision

A real team

Backlog

On the market street bridge by bclinesmith taken from Flikr is licensed under CC BY 2.0

So we needed some traffic

Luoyang Traffic 2 by James Jin taken from Flikr is licensed under CC BY 2.0

Iterative

Source Jeff Patton

4 workflow parts

Splitting strategies

By workflow (reduce risk)

By data (concentrate on value)

By priority (reduce waste)

Splitting - taken by Gordon Matta-Clark

Vision

Bubbles by Tim Geers taken from Flikr is licensed under CC BY 2.0

But not written down

Bubbles by Tim Geers taken from Flikr is licensed under CC BY 2.0

A real team

A shared goal

Small in size

Defined boundary

Constant over time


Experts in technology

Cross-functional

Full-time

Our team

- Able to solve the problem

- Create, develop, test work

- Focus to build and learn


How to tackle it down?


What worked for us1. Get a great Product Owner

2. Solve impediments

3. Create backlog

4. Control your scope

5. Be open

6. Define done

1. Get a great Product Owner

…and start the process.

2. Solve impediments

Sheep Crossing by Todd Anderson taken from Flikr is licensed under CC BY 2.0

3. Create backlog

GOAL: create initial backlog and estimate it

Generate roadmap

Backlog creation workshop

2x Estimation, 2x Refinement

Iceberg in Paradise Harbour, Antartica by Liam Quinn taken from Flikr is licensed under CC BY 2.0

4. Control your scope

DO

Refinement sessions

Triage sessions

Release burndown bar

5. Be open

Open Book by Rubber Dragon taken from Flikr is licensed under CC BY 2.0

Deliver every sprint

Report your

impediments & quality

budget & scope left

Update roadmap/release plan

6. Define done


Know when you are done to avoid legacy, and talk with shareholders about it.

Sprint 0 (tough work)


Tell the vision Coach the people Set limits to outside Create an initial backlog

Sprint 1 (change happens)

Starting with backlog refinement and estimation Starting scope control and scope change Starting the improvement process Deal with organisational change

crossroads by Laenulfean taken from Flikr is licensed under CC BY 2.0

Sprint 2 (shaking the foundation)

3 of 4 selected stories ran into problems

Critical bug in backend systems

Far from technical agreement

Functional negotiation

Negotiations about shifting scope

Technical negotiations and work ethos

Challenge definition of done with test team

Earthquake Damage - Bridge Street by Martin Luff taken from Flikr is licensed under CC BY 2.0

Sprint 2 (consequences)

Postponed one story (bug)

Backlog is growing without estimates

Decreased trust between teams

Waste of time

Next sprint was prepared just in time but in haste

Earthquake Damage - Bridge Street by Martin Luff taken from Flikr is licensed under CC BY 2.0

Sprint 3

Starting with a constant pace

Starting design workshops

More of intensive team coaching

Less of organisational interference


Sprint 4

Starting with specification by example

Starting common user story format

More of design workshops

More of customer collaboration workshops


Sprint 5

Starting study group

More of common user story format

More of examples


Scope control

<velocityforecast-sprint4-5.png>!

Grown backlogStory

poin

ts

0

55

110

165

220

Sprints

1 2 3 4 5

207207202

171148

What is next?

Thank you for your attention!


@svnwnk

www.jedev.org/

www.iso-gruppe.com

Devine icon parts by ipapun is licensed under CC BY 2.0

http://www.jedev.org/

http://www.iso-gruppe.com

Backlog reportsAm

oun

t of

stories

0

15

30

45

60

Stories in backlog

Stories estimated

Stories re-estimated

Stories discarded

15

31

4955

Backlog and velocityStory

poin

ts

0

55

110

165

220

Backlog and velocity

99

207

Backlog and velocityStory

poin

ts

0

75

150

225

300

Sprints

1 2 3 4 5

Definition of done

Component teams

Read more about here: Practices for Scaling Lean and Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum by Craig Larman

Feature teams

Read more about here: Practices for Scaling Lean and Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum by Craig Larman

mission impossible - asqf€¦ · mission impossible ... 110 165 220 backlog and velocity 99 207....

Documents