Progres reporting in agile context

36
Madrid, 26th to 28th May 2014 Business Progress Reporting in Agile Context Derk-Jan de Grood @DerkJandeGrood Expo:QA: 29 May 2014 1

description

Test progress reporting can be cumbersome. There is a complex story to be told, but it needs to be done in such a way that the business and project stakeholders get the message. Sequential planning techniques such as critical path analysis won’t work in agile, but stakeholders keep asking for an indication of the progress so far, the work that remains, the bottlenecks and dependencies. Within my current project we solved this problem by introducing a visual progress report, the subway map. Subway map reports are derived from the London tube map and contain the following elements: 1) Stations: Activities are represented as a station; they have a description of the benefit for the stakeholder upon completion. 3) Date lines provide status information (the train is expected on time, or not) 3) Bridges: Where two or more lines merge, you can define have a quality gate. They provide extra control on the progress (and of course to celebrate success) In this presentation I will provide examples, a step plan how to make a subway map in Powerpoint and how it can be used for your project, program, etc. Within my organization it has been adopted quickly by various projects, due to its simplicity and clearness. Business finally understood testing.

Transcript of Progres reporting in agile context

Page 1: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Business Progress Reporting in Agile Context

Derk-Jan de Grood

@DerkJandeGrood

Expo:QA: 29 May 2014

1

Page 2: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Goals

1. Explain why ordinary progres reporting fails its purpose

2. Explain why good reporting enabels us to show our added value

3. Introduce the ‘subway map’

4. Get hands on…

2

Page 3: Progres reporting in agile context

Madrid, 26th to 28th May 2014

PROGRESS REPORTING

PROGRESSPROGRESS

Page 4: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Page 5: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Page 6: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Page 7: Progres reporting in agile context

Madrid, 26th to 28th May 2014

GHANT vs PERT

GHANT vs PERT

Page 8: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Page 9: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Why I love PERT

• Gives a better insight in the relations between activities

• Stimulates managing the critical path

• If made well: shows the structure of the project

Page 10: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Nobody likes long lists

Nobody likes long lists

Page 11: Progres reporting in agile context

Madrid, 26th to 28th May 2014

A whole new game !

Page 12: Progres reporting in agile context

Madrid, 26th to 28th May 2014

SCRUM BOARD

Page 13: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Burn Down

Page 14: Progres reporting in agile context

Madrid, 26th to 28th May 2014

BUT…..BUT…..

Page 15: Progres reporting in agile context

Madrid, 26th to 28th May 2014

A Better way to reportA Better way to report

Page 16: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Requirements

• Tell about the strategy of the project

• Predict bottleneck

• Provide progress info

• Each completed step has value

• Visual

• One-pager

Page 17: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Page 18: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Page 19: Progres reporting in agile context

Madrid, 26th to 28th May 2014

44 55

66

11 33

77 88 991111 1212

3. C

redit

man

agem

ent

ensu

res t

hat

only

paid

good

s are

deliv

ered

4. U

ser c

an a

cces

s site

and

crea

te a

ccou

nt

5. P

rodu

ct DB is

corre

ctly

Migr

ated

and

use

r can

add

selec

ted

prod

ucts

to

shop

ping

bask

et

6. U

ser c

an se

lect

and

pay p

rodu

ct

8. O

rder

s can

be

proc

esse

d

7. O

rder

s are

hand

led to

bac

k

offic

e 11. F

ront

Offic

e or

ders

are

proc

esse

d: P

icking

, box

ing

and

deliv

ery

QGQGQG QG

1. P

aym

ents

can

be m

ade

12 P

ilot

11. A

ll thr

ee ch

ains a

re

integ

rate

d. R

eal li

ve te

st22

2. P

aym

ents

are

proc

esse

d on

finan

cial

dept

.

15 J

uly

1 A

ug

.

15

Au

g.

1 S

ept.

15

Sep

t.

1010

To be done (on time)

In progress (on time)

In progress (critical)

Done

Order processing

Front End Web shop

Payment

Delivery

In progress (delayed)

24 July 2013

6a6a

Project XSubway map

Date: <Date >By: <Name>

6a. U

ser

gets

track

and

trace

notifi

catio

ns

Page 20: Progres reporting in agile context

Madrid, 26th to 28th May 2014

What’s on the SUBWAY map

Page 21: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Different lines

Page 22: Progres reporting in agile context

Madrid, 26th to 28th May 2014

44 55

66

11 33

77 88 991111 1212 QGQGQG QG

22

1010

24 July 2013

6a6a

Dependencies & strategy

Page 23: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Benefit based reporting

Page 24: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Stations

Page 25: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Date Lines

Page 26: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Bridges

Page 27: Progres reporting in agile context

Madrid, 26th to 28th May 2014

1 au

g

1Sep

.

1 O

kt.

1 n

ov.

1Dec

.

To be done (on time)

In progress (on time)

In progress (critical)

Done

Business

Netco TI

Netco IT Service & Levering

In progress (delayed)

1jan

.

1feb

.

1mar

.

1ap

r.

1may

.

1ju

n.

1ju

l.

Start

func

tiona

l

des

ign

Netco IT Billing

Page 28: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Produ

ction

imple

men

tatio

n

Page 29: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Page 30: Progres reporting in agile context

Madrid, 26th to 28th May 2014

How to make it

 

If you want to make a subway map, take the following steps:

 

1. Define the lines in your project

2. Investigate dependencies between the various lines, if required make the lines cross

3. Define steps and primary milestones, these are your stations

4. Place the stations on the line taking into account the dependencies and time lines

5. Add benefits to the stations

6. Share your subway map 

 

Page 31: Progres reporting in agile context

Madrid, 26th to 28th May 2014

DIY: A web shop

• Make a draft subwaymap for the development and testing of a website.

• Think about: infrastructure, grafical design (marketing style), creating the content (tekst and photo’s) and of course building the site in your CMS. What would the subway map look like?

Page 32: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Page 33: Progres reporting in agile context

Madrid, 26th to 28th May 2014

WRAP UP

Page 34: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Page 35: Progres reporting in agile context

Madrid, 26th to 28th May 2014

More info

Template and Quick reference card:

http://djdegrood.wordpress.com/2013/10/17/progress-reporting-with-the-subway-map/

In context with other techniques:

http://djdegrood.wordpress.com/2013/11/01/unpack-your-toolkit-becoming-more-effective-with-the-right-tools-and-techniques/

General: djdegrood.wordpress.com

Page 36: Progres reporting in agile context

Madrid, 26th to 28th May 2014

Thanks for listening

Derk-Jan

ValoriColtbaan 4a, 3439NG NIEUWEGEINThe Netherlands

[email protected]+31(0)651807878www.valori.nl@DerkJanDeGroodhttp://djdegrood.wordpress.com

Derk-Jan

36