This document outlines ways to undermine agility in an organization from a coach's perspective. It discusses 7 lessons to "kill" an agile transition by making it a checklist and assuming management knows agile without training teams. It also details 12 tips to "save the bugs and kill quality" such as ignoring priorities, leaving no time for testing or bug fixing. Finally, it lists 5 lessons to "save command and control and kill self-organization" like creating hierarchies and assuming teams can't make decisions without oversight. The document aims to identify common anti-patterns and ways to promote true agility instead of undermining it.

1. How to Improve Agility in an organization
A Coach’s perspective

2. Madhur Kathuria
Certified Scrum Coach
CSC,CSP, CSM, CSA
Product Operations Manager, PegaSystems
Chair, India Scrum Enthusiasts Community

3. How to ‘Kill’ Agility in an organization
The Agile Devil’s workshop

4. WHO AM I ?
www.agiletour.org

5. CHAPTER 1
SAVE THE LAST METHOD
KILL THE AGILE TRANSITION

6. Lesson # 1
Make the transition a checklist

7. Lesson#2
Management
knows everything
about Agile.
It’s only the teams
who need training
© www.madhurkathuria.info

8. Lesson#3
Agile Transition
is Easy.
All we need , is
to certify every
team member in
Agile methods

9. Lesson #4
Start the transition bottom-
up. It’s the teams which
need to learn Agile

10. Lesson #5
Product Management, Project
Management, Development , Test
Engineering are all separate departments.
Each should transition
at its own pace

11. Lesson #6
Agile says No
Documentation.
So, No documents
will ever be created
henceforth

12. Lesson #7
• Estimates should
always translate
into hours ~ 1SP=
8 hrs

13. CHAPTER 2
SAVE THE BUGS, KILL THE QUALITY

14. Tip # 1
Ignore the story priorities
X

15. Tip # 2
All stories must complete on last 1-2
days of sprint

16. Tip # 3
Team should
pick up more
stories than it
can test

17. Tip # 4
Make sure DoD is never looked
into during sprint review and is
invisible on team pages too .

18. Tip # 5
Make Sure tasks published on
Scrum task board do not have
test plan review, test execution
and bug fixing

19. Tip # 6
Code changes should continue
till last date of the sprint.

20. Tip # 7
Make Sure Minimum time remains for
bug fixing at the end of sprint.

21. Tip # 8
Make Sure Some bugs are definitely
carried to the next sprint and to the bug
backlog..

22. Tip # 9
Make sure your bugs are not
tagged to stories/ features

23. Tip # 10
Make Sure No Regression
testing is possible in the sprint

24. Tip # 11
Focus only on the tasks
assigned to you.

25. Tip # 12
Make sure your estimates include only
the development complexity/size and
not the test complexity and size.

26. SAVE THE
COMMAND AND
CONTROL,
KILL SELF
ORGANIZATION
CHAPTER 3

27. Lesson # 1
Create as many hierarchies as
possible in the team, everyone
desires a promotion

28. Lesson # 2
Team members should report to
Scrum Master

29. Lesson # 3
Teams are incapable of
taking a collective
decision.
So, it best left to the
experienced people
like Scrum Master and
Product owner

30. Lesson # 4
As team is
inexperienced in
processes,
It doesn’t know what
works for them.
A Coach/ consultant
knows the best that
can work

31. Lesson # 5
Manager is essential for an Agile
team. He/ She should oversee
every thing every day/ every hour

32. The Next Steps
Identify which of these things are common
happenings in your projects
Identify 5 ways that you will thwart the plans for Agile
Devil
www.agiletour.org 32

33. 20 February, 2012 33

34. Questions??
20 February, 2012 34

35. If I can be of any help
Madhur Kathuria
 www.madhurkathuria.com / www.madhurkathuria.info
 Email: madhur@indiascrumcommunity.org
 Twitter: madhurkathuria
 Skype: madhur.kathuria
20 February, 2012 35

36. THANK YOU
www.agiletour.org