Madhur kathuria how to improve agility in a large organization

843 views

Published on

Slideset from Agile devil's workshop at Agile India 2012

Published in: Technology, Business
1 Comment
1 Like
Statistics
Notes
No Downloads
Views
Total views
843
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide

Madhur kathuria how to improve agility in a large organization

  1. 1. How to Improve Agility in an organization A Coach’s perspective
  2. 2. Role • Business Consultant with Consulting and System Integration unit for Retail, CPG, LifeSciences verticalProfile • Provide roadmap and IT strategy for Fortune 2000 organizations • Bidding Consultant Abhishek Kumar Business consultant- CSI, Infosys MBA(IS), BE(Mech), CSoP
  3. 3. Madhur Kathuria Certified Scrum Coach CSC,CSP, CSM, CSAProduct Operations Manager, PegaSystems Chair, India Scrum Enthusiasts Community
  4. 4. How to ‘Kill’ Agility in an organization The Agile Devil’s workshop
  5. 5. WHO AM I ?www.agiletour.org
  6. 6. CHAPTER 1 SAVE THE LAST METHODKILL THE AGILE TRANSITION
  7. 7. Lesson # 1Make the transition a checklist
  8. 8. Lesson#2Managementknows everythingabout Agile.It’s only the teamswho need training © www.madhurkathuria.info
  9. 9. Lesson#3Agile Transitionis Easy.All we need , isto certify everyteam member inAgile methods
  10. 10. Lesson #4Start the transition bottom-up. It’s the teams whichneed to learn Agile
  11. 11. Lesson #5Product Management, ProjectManagement, Development , TestEngineering are all separate departments.Each should transitionat its own pace
  12. 12. Lesson #6Agile says NoDocumentation.So, No documentswill ever be createdhenceforth
  13. 13. Lesson #7• Estimates should always translate into hours ~ 1SP= 8 hrs
  14. 14. CHAPTER 2SAVE THE BUGS, KILL THE QUALITY
  15. 15. Tip # 1Ignore the story priorities X
  16. 16. Tip # 2All stories must complete on last 1-2 days of sprint
  17. 17. Tip # 3Team shouldpick up morestories than it can test
  18. 18. Tip # 4Make sure DoD is never lookedinto during sprint review and is invisible on team pages too .
  19. 19. Tip # 5Make Sure tasks published onScrum task board do not havetest plan review, test execution and bug fixing
  20. 20. Tip # 6Code changes should continue till last date of the sprint.
  21. 21. Tip # 7Make Sure Minimum time remains for bug fixing at the end of sprint.
  22. 22. Tip # 8 Make Sure Some bugs are definitelycarried to the next sprint and to the bug backlog..
  23. 23. Tip # 9Make sure your bugs are not tagged to stories/ features
  24. 24. Tip # 10 Make Sure No Regressiontesting is possible in the sprint
  25. 25. Tip # 11Focus only on the tasks assigned to you.
  26. 26. Tip # 12Make sure your estimates include onlythe development complexity/size and not the test complexity and size.
  27. 27. SAVE THE COMMAND AND CONTROL, KILL SELF ORGANIZATIONCHAPTER 3
  28. 28. Lesson # 1Create as many hierarchies aspossible in the team, everyone desires a promotion
  29. 29. Lesson # 2Team members should report to Scrum Master
  30. 30. Lesson # 3Teams are incapable of taking a collective decision. So, it best left to the experienced peoplelike Scrum Master and Product owner
  31. 31. Lesson # 4 As team is inexperienced in processes,It doesn’t know what works for them.A Coach/ consultantknows the best that can work
  32. 32. Lesson # 5Manager is essential for an Agile team. He/ She should overseeevery thing every day/ every hour
  33. 33. The Next StepsIdentify which of these things are commonhappenings in your projectsIdentify 5 ways that you will thwart the plans for AgileDevil www.agiletour.org 33
  34. 34. 20 February, 2012 35
  35. 35. Questions??20 February, 2012 36
  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: augusta4u20 February, 2012 37
  37. 37. THANK YOU www.agiletour.org

×