26
Measure What Matters An experience report by Munish Malik Project Manager & Agile Coach Crest, Pune

Measure what matters for your agile project

Embed Size (px)

Citation preview

Page 1: Measure what matters for your agile project

Measure What Matters

An  experience  report  by  Munish  Malik  

Project  Manager  &  Agile  Coach  Crest,  Pune  

 

Page 2: Measure what matters for your agile project

“He uses statistics as a drunken man uses lamp posts:���

for support rather than for illumination.” ���

Andrew  Lang  

Page 3: Measure what matters for your agile project

“Most murders are committed by someone who is known to the victim. In

fact, you are most likely to be murdered by a member of your own family on

Christmas day.”  

Mark  Haddon  The  Curious  Incident  Of  The  Dog  In  The  Night  Time  

Page 4: Measure what matters for your agile project

I                                    STORY  POINTS  Do  you  simply  love  to  work  with  esImates,  velociIes  &  burn-­‐up  or  

burn-­‐down  charts?  

Page 5: Measure what matters for your agile project

“Your estimates never hold true!”

Page 6: Measure what matters for your agile project
Page 7: Measure what matters for your agile project

Project completed on time, budget & scope.

Estimates were correct.

But failed when went live to the market.

Page 8: Measure what matters for your agile project

Are  we  measuring  what  really  maLers?  

Page 9: Measure what matters for your agile project

Estimates v/S #NoEstimates

Page 10: Measure what matters for your agile project

Don’t  make  promises  here  

Make  them  down  here  once  you’ve  had  a  chance  to  firm  things  up  

Done  

ConstrucIon  

ElaboraIon  

IncepIon  

Time  à  

EsIm

aIon

 v/S  variability  

1.25x  

2x  

4x  

0.8x  

0.5x  

0.25x  

Cone  of  uncertainty*    

*The  Cone  of  Uncertainty  as  described  by  Steve  McConnel.  Agilenutshell.com  

Page 11: Measure what matters for your agile project

What  can  we  do?  Let  us  see  some  samples  to  

get  an  idea.  

Page 12: Measure what matters for your agile project

SAMPLE  1  

•  Working  with  goals  for  a  development  project  •  Measure  how  the  user  goals  or  business  goals  are  ge\ng  

met  

Page 13: Measure what matters for your agile project

Goal  1  e.g.  Make  Search  results  more  relevant  

Epic  1   Epic  2   Epic  3   Epic  4  

Story  2  

Story  1  

Story  3  

Story  4  

Story  …  

Story  …  

Story  …  

Story  …   Story  

…  

Story  …  

Story  …  

Story  …  

Goal  2  e.g.  Improve  UX  for  

Free  Users  

Story  …  

Working  with  goals  

Page 14: Measure what matters for your agile project

Measuring  goals  

0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%

Business Continuity

Optimize Search

Improve site's visual design

Optimize Data Architecture

Get Feedback (Analytics)

Improve UX for Free Users

Completed Pending

Page 15: Measure what matters for your agile project

SAMPLE  2  

For  a  development  project:  create  (monthly)  dashboards  to  track  goals  or  features.  

Page 16: Measure what matters for your agile project

Homepage  

Search  

SEO  

Technical  

Story  2  …  

Story    …  

Story  …  

Story  …  

Story    …  

Story    …  

Story  …  

Story  …  

Total  Planned   Aggressive  Goal  

Story    …  

Story    …  

Story  …  

Story  …  

Story    …  

Story    …  

Story  …  

Story  …  

New  Scope  

Story    …  

Story    …  

Story  …  

W1   W2   W3   W4  

4   4   2   2  

Weeks  

Dev  Pairs  Availability  0   2   4   6   8   10  

Planned  v/S  Actual  

Actual  

Planned  

Completed   In-­‐progress   Not  picked  up  

QA  

QA  

Dev  

Blocked  

Developer  Capacity  

Focus  is  how  goals  or  features  are  ge\ng  completed  

(Monthly)  Dashboards  to  see  progress  on  user/  business  goals  or  features  

Page 17: Measure what matters for your agile project

SAMPLE  3  

•  For  a  development  project:  Create  (monthly)  dashboards  to  track  goals  or  features  along  with  dependencies  

•  The  project  has  heavy  dependencies  on  data  delivery  &  UXD  •  Features  or  goals  get  blocked  if  the  data/  UX  design  is  not  

available  on  Ime  

Page 18: Measure what matters for your agile project

Homepage  

Search  

SEO  

Technical  

Story  …  

Story    …  

Story  …  

Story  …  

Data   Story  …  

UXD   Story  …  

Tracking  Dependencies  

Features  or  Goals  

New  Scope   Story  …  Tracking  New  Scope  

Story  …  

Story    …  

Story  …  

Story  …  

Story  …  

Story  …  

Story  …  

Story  …  

Story    …  

Story  …  

Story  …  

Story  …  

Story  …  

Story  …  

Story  …  

Story    …  

Story  …  

Story  …  

Story  …  

Story  …  

Story  …  

Story  …  

Story    …  

Story  …  

Story  …  

Story  …  

Story  …  

Completed   In-­‐progress   Not  picked  up   Blocked  

(Monthly)  Dashboards  to  see  progress  on  goals  or  features  w/  Dependencies  

Page 19: Measure what matters for your agile project

SAMPLE  4  

For  a  support/  maintenance  project:  •  The  team  is  spending  Ime  on  different  categories  of  defects  •  Need  to  idenIfy  where  the  team  is  spending  (or  wasIng)  most  

Ime  

Page 20: Measure what matters for your agile project

Nature  of  work  done:  by  a  support/  maintenance  project  

10  5   8   5  

17  23  

21  

16  

8  10   10  

9  

9  

18  

29  

35  

0  

10  

20  

30  

40  

50  

60  

70  

80  

It.  1   It.  2   It.  3   It.  4  

Defects  

Code  Defects    Data  Defects  

ConfiguraIon  Defects   Defects  Answered  to  other  teams  (No  Fix  Reqd.)  

Page 21: Measure what matters for your agile project

SAMPLE  5  

For  a  support/  maintenance  project:  •  Team  supporIng  various  applicaIons.    •  Each  app  having  its  own  product  manager  •  Every  product  manager  wants  his/her  defects  to  get  addressed  first,  

hence  defects  being  given  a  higher  priority  (cosmeIcally)  •  P1  defect  =  S***  has  hit  the  fan.  SIll  P1  stays  open  for  3+  months.  

Then  is  it  really  a  P1?  

Page 22: Measure what matters for your agile project

For  a  support/  maintenance  project:  Aging  report  of  defects  

0   0   1  3  

5   6  

10  

11  6   4  

6   1  

4  

3  

5  

5  

0  

5  

10  

15  

20  

25  

More  than  1  Year   6  Months  to  1  Year   3-­‐6  Months   Less  than  3  Months  

Num

ber  o

f  Defects  

P1   P2   P3   P4  

Page 23: Measure what matters for your agile project

To  sum  up  

•  Think  out  of  the  box  to  measure  the  progress  of  your  project  

•  Make  sure  you  measure  what  really  maLers    •  IdenIfy  what  are  your  project  KPIs  /  success  factors  and  measure  those  

•  Measurements  have  the  power  to  moIvate  people  to  perform  as  per  what  they  represent  

•  Don’t  make  your  staIsIcs  work  like  bikinis  

Page 24: Measure what matters for your agile project

Will  you  slow  down  if  you  see  this?  

Page 25: Measure what matters for your agile project

(EffecIve?)  Speed  (visual)  control  being  used  in  Canada  

Page 26: Measure what matters for your agile project

Thank  you  Munish  Malik  Project  Manager  &  Agile  Coach.  Crest,  Pune  [email protected]  [email protected]  hLp://www.slideshare.net/munishm