Slideset from Agile devil's workshop at Agile India 2012

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

2. Role
• Business Consultant with Consulting
and System Integration unit for
Retail, CPG, LifeSciences vertical
Profile
• Provide roadmap and IT strategy for
Fortune 2000 organizations
• Bidding Consultant
Abhishek Kumar
Business consultant- CSI, Infosys
MBA(IS), BE(Mech), CSoP

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

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

5. WHO AM I ?
www.agiletour.org

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

7. Lesson # 1
Make the transition a checklist

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

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

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

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

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

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

14. CHAPTER 2
SAVE THE BUGS, KILL THE QUALITY

15. Tip # 1
Ignore the story priorities
X

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

31. 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

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

33. 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 33

34. 20 February, 2012 35

35. Questions??
20 February, 2012 36

36. If we can be of any help
Madhur Kathuria
 www.madhurkathuria.com / www.madhurkathuria.info
 Email: madhur@indiascrumcommunity.org
 Twitter: madhurkathuria
 Skype: madhur.kathuria
 Abhishek Kumar
 www.abhishekaugusta.in
 Email: abhishek@indiascrumcommunity.org
 Twitter/Facebook: augusta4u
20 February, 2012 37

37. THANK YOU
www.agiletour.org