11 ways to Screw up Agile by Hedwig Baars

New way of working in RM r&d india

Slide title minimum 32 pt

(32 pt makes 2 rows

Text and bullet level 1 minimum 24 pt

Bullets level 2-5minimum 20 pt

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–—‘’‚“”„†‡•…‰‹›⁄€™−≤≥fifl

ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș

ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏ

ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ№

Do not add objects or text in the footer area

10 Ways to Screw up Agile | Ericsson Internal | 2010-06-21 | Page 2

OUR LEARNING’Sfrom Agile community and ///

Slides used from Crisp

Marc Verschueren


(32 pt makes 2 rows









› Not present in the team› Is tech guru› Is too busy› Does not know SCRUM› Does not have an impediment backlog› Conflict between juniors and seniors› To fast changing SM› SM appointed instead of voluntarily

1. Scrum Master

SM

We have work to do.We cannot afford the

overheadOf a Scrum master


(32 pt makes 2 rows









2. Definition of Done

› Don’t have default DoD› Don’t obey it› Is outside the team’s control› Too high level

But you said you wereDone!

= I haven’t messed up the code base

Definition of Done• Unit/Integration tested• Ready for acceptance test• deployed on demo server

Definition of Done• Unit/Integration tested• Ready for acceptance test• deployed on demo server• No increased technical debt


(32 pt makes 2 rows









3. Velocity

› Isn’t known› Isn’t used› Is misused› Team asked to promise dates› Including stories that aren’t done› Yo-yo velocity

What is your velocity?

Huh?

EXAMPLE• Today is Aug 6• iteration length = 2 weeks• Velocity = 30 - 40

What will be done by X-mas?(10 iterations)

PO


(32 pt makes 2 rows









4. Team commitment

› Team is pressured› Team doesn’t track and learn› Always under committing› Always over committing› Velocity = unknown› Not allowing slack› Too much un-planned items

Estimated Actual

30 20

20 18

18 18

18 21

You have to do more!

Estimated Actual

30 20

30 20

30 20

30 20

Estimated Actual

30 20

40 20

50 20

60 20


(32 pt makes 2 rows









5. Technical debt

› Letting it pile up› Not being professional

We don’t have time to write unit test or

refactor code!

velo

city

velo

city

time

Sustainable pace!

Technical debt:- No duplication of code- Same test coverage as before- Readable code


(32 pt makes 2 rows









6. teamwork

› Fixed roles› Personnel backlog› Not helping each other› Implementing all stories in

parallel› External management

Well, at least I finished my stuff!


(32 pt makes 2 rows









7. Product backlog & owner

› PBL doesn’t exist› PBL not visible› Never ending stories› Too big stories› PO surprised at demo› PBL not maintained by PO› PO not prioritizing

I don’t have time tomaintain the damned

product backlog!


(32 pt makes 2 rows









8. Ergophobia

› No done branch› No branch policies› Not synchronizing every day› Not taking responsibility› Hiding behind branches

Merging is pain, so we

Do it as seldom as possible

You can’t get an Agile companyWithout Agile engineering practices

XP, anyone


(32 pt makes 2 rows









Burndown

Unplanned items

Notchecked out Done! :o)

Write f ailing test

DAO

DB design

I ntegr test

Write f ailing test

GUI spec

I mpl. migration

2d0.5d1d

8d

2d

2d

BackofficeLogin

BackofficeUser admin

Write f ailing test

1d2d

I mpl GUI

I ntegr. with

J Boss

Write f ailing test

3d

I mpl GUI

Clarif y require-ments

GUI design (CSS)

1d

Sales support

3d Write whitepaper

4d

SPRINT GOAL: Beta-ready release!

Next

Withdraw

checked out

Write f ailing test

9. Sprint backlog

› Doesn’t exist› Too far from the team› Too complicated› Not used during daily stand-up› Format not chosen by the team› Not owned by the team› Not updated daily› No burn down› Warning signs ignored

Oh you mean that thingThat the team coach

Fiddles with sometimes?


(32 pt makes 2 rows









10. Worrying too much about the problems

› Problems are normal› Never stop looking for problems› Don’t panic, don’t despair› Visible problem = killable problem– = opportunity for improvement!

› Prioritize and fix problems – one by one!› Look back once in a while and pat yourselves on the back

We should stop this Agile

Stuff, since we’reobviously doing it all

wrong!


(32 pt makes 2 rows









11.Transfer of product

› Sending site is not using Agile or not in the same way–We do it different … Agile can be done

in silos–We do not have time for that–Receiving staff are trained by sending

site in non agile–A bit scary to take product

responsibility and agile implementation–……

Agile and transfer does not go hand in hand

Technology

11 ways to Screw up Agile by Hedwig Baars