measuring improvement

7/28/2019 Measuring Improvement

1/16

Marco Melas / PARSHIP / 2012-Oct-22

Ready, set, go!

Measuring Improvement


2/16

Who am I?

Marco MelasItalian German

Age 38

Married with kid

Live in Hamburg

Head of Delivery Management &Engineering

Engineering

Agile Coaching Project Management

Favorite sentence at work:

Irgendwas ist ja immer Shithappens

22.10.2012

2


3/16

Present in 12 European

countries and Mexico

160 employees

Subsidiary of the Georg vonHoltzbrinck publishing group

Premium brands: PARSHIP.com

and gayPARSHIP.com

EUR 55 mio. turnover in 2010

PARSHIP: Leading online matchmaking

agency in Europe

3


4/16

22.10.2012

4

PARSHIP

Product Development Team in a nutshell

Product Management

4 PO

2 UX

1 Designer

Engineering (5-6 ppl/team)

3 Scrum teams internal

1 Scrum team external (Kiev, Ukraine)

1 Kanban Team

IT-Ops (5 ppl)

1 Kanban Team


5/16

Improving is deciding

What KPIs do you use for makingbusiness decisions?e.g. how do you know if your website is

successful?

22.10.2012

5


6/16

What KPIs do you use for making IT-

decisions?e.g. how do you decide about product quality?

We need to know more!

22.10.2012

6


7/16

Some sample questions for KPIs:Do we have the most relevanttopics on our plan?

Is the current development in linewith the corporatestrategy?

What is the time-to-marketfor an idea?

How to measure successof Scrum-Teams?

22.10.2012

7


8/16

22.10.2012

8

CollectStakeholder

InputFirst Ranking Second Ranking Final Ranking

Quarter

Proposition

Product

List

Unsorted

Product

List

1. Business Value

2. Fits business

strategy

3. Rough Estimation

(S, M, L, XL, XXL)

4. Ranking

1. Product Show

2. Management

Presentation

3. Audience Input

4. Team Estimations

Final

Product

List:

Roadmap

TeamsDevPOPO PO PO

Do we have the most relevant topics on our plan?

The quartely roadmap process


9/16

Is the current development in line with thecorporate strategy?

22.10.2012

9

We know on how many Epics/Projects from

the Roadmap (and corporate strategy) wework.

We know how much we did that was not on

the Roadmap.


10/16

22.10.2012

10

How to improve time-to-market for an idea

Based on this KPI concrete projects resulted, e.g.

Continuous Deployment Deploy components independently

Introduce SW-Kanban to EngineeringA fastlane always exists!


11/16

22.10.2012

11

How to measure success of Scrum-Teams?

Time: did we deploy when we wanted to deploy?

Yes/No

Scope: is the PO happy with the amount the teamdeveloped?

1 yes, overachieved, 3 below expectation,

2 yes, as expected, 4 no

Quality: is the Requestor happy with the feature?1 yes, overachieved, 3 below expectation,

2 yes, as expected, 4 no


12/16

12

Ensure Delivery

Be the Scrummaster/Agile Coach Create Transparency

Responsibility for the Deliveryprocess - from idea to

deployment

A key role for Measuring Improvement is

Delivery Management

22.10.2012


13/16

Key take-aways of this session

1. Improvement is measurable

2. There are more indicators than system-

based/financial3. Creating and collecting KPIs is no Voodoo! Still

its hard work and DM or a similar role is

essential for a successful implementation

4. You need a target in order to know what andwhy you need to measure

22.10.2012

13


14/16

14

14

22.10.2012

And in the spirit of improving


15/1622.10.2012

15

More questions or comments?

Marco Melas

[email protected]

@mmelas74

Head of Delivery Management

& EngineeringPARSHIP GmbHSpeersort 10

D - 20095 Hamburg


16/16

Excursus:How to measure?

Systemic Indicators a.k.a. hard facts:

Conversion, OrderEntry, Availibility, # known bugs

Systems measure and display defined values

Soft facts:

Polls, Interviews,

22 10 2012

16

because Perception Is Reality

measuring improvement

Documents