Failing With Agile


Published on

Presentation for Mile High PMI Workshop on November 15, 2008


There are always people who want agile projects to fail. This will probably be the case until agile is the preferred process methodology used for projects. Are you one of them? In this workshop Bob Hartman will give participants a how-to guide for causing agile process failure. Attendees will learn various failure modes and how to cause them. There will be group discussions and exercises exploring how the failure modes can manifest themselves in real projects. At the end of this workshop each attendee should have the ability to cause agile project failure in a variety of ways and under a variety of conditions.

Obviously the first paragraph is a bit tongue-in-cheek. Hopefully project managers do not want agile projects to fail, but they need to know how they could fail. This knowledge will translate into an ability to recognize the failure modes and take corrective action. Interestingly, many of the agile project failure modes are also failure modes in other project process methodologies. All project managers on agile projects or in organizations that are considering using an agile process should attend this workshop. Project managers in organizations which typically struggle with projects may also gain insight into their project failure modes.

Published in: Technology, Business
1 Comment
  • <br /><iframe width="350" height="288" src="" frameborder="0" allowfullscreen></iframe>
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Is 50% even any good? Don’t we want to be a lot better than that?
  • What are some examples
  • The process allowed it – rules of engagement
  • Communication overhead is ridiculous
  • Knowledge is power – command and control’ish
  • You will fall further and further behind – remember doing the right thing wrong
  • Failing With Agile

    1. 1. Failing with Agile:A How-to Guide<br />Don’t end up with an apple instead of an Apple®!<br />Presented byBob HartmanPresident, Agile For<br /><br />Presentation Copyright © 2008, Agile For All, LLC. All rights reserved.<br />
    2. 2. Before We Start<br />Cell phones, pagers, PDA’s, etc. to silent<br />If you have a question, please ask it. Don’t wait! It is better to answer the question while we are still in the same area than to go back.<br />We will take a break after about 90 minutes<br />Failing with Agile<br />2<br />
    3. 3. Introductions<br />
    4. 4. Bob Hartman (Agile Bob)<br />30+ years of software industry experience<br />Certified Scrum Practitioner<br />Bachelor and Masters degrees in Computer Science<br />Roles included Tester, Developer, Dev Manager, QA Manager, Product Manager, Project Manager, VP…<br />Started with agile in 1999<br /><br />303-766-0917<br />Failing with Agile<br />4<br />
    5. 5. Who are you?<br />Please introduce yourself including:<br />Name<br />Company and role<br />Agile experience<br />AboutMe<br />Failing with Agile<br />5<br />
    6. 6. Framing the problem<br />
    7. 7. Software project success rates<br />Source: The Standish Group<br />Success increasing by 1.7% per year. Will not reach 50% until 2014!<br />Failing with Agile<br />7<br />
    8. 8. Industry realities<br />Most “successful” projects were deliberately over-estimated at the start (Standish – 2001)<br />The average project exceeds its schedule by 63% (Standish – 2001)<br />50% of project failures are due to missing or misunderstood requirements (Ravenflow – 2006)<br />Executive support and customer involvement are the two biggest critical success factors in project success by far (many studies in the past 10 years)<br />Failing with Agile<br />8<br />
    9. 9. More industry realities<br />56% of defects are attributable to missing or misunderstood requirements<br />82% of defect fixing time and dollars go to fixing requirements related defects<br />NIST has estimated that 0.6% of the GDP is lost due to software defects<br />NIST also estimates that 1/3 of that money could be saved by using a process allowing earlier detection and correction of defects<br />Failing with Agile<br />9<br />
    10. 10. Things I sometimes ponder…<br />Why do we make all important decisions on projects when we have the least information?<br />Why do managers always think things will take less time than everyone else? Why do we let them estimate at all?<br />Why has the software industry never improved the ability to estimate accurately?<br />If we know that an average of 30% of requirements will change during a project, why do we use a process that is intolerant to change?<br />Why do companies say that quality is important while internally they give QA less time than originally allocated to do their job?<br />Why do developers always do the easiest things first?<br />If the customer is always right, why do we only ask them their opinion AFTER we have completed the entire project?<br />Failing with Agile<br />10<br />
    11. 11. Doing the right thingbut doing it wrong<br />But this is supposed to work!!!<br />
    12. 12. Getting things to “done” – sort of!<br />Iteration 1 – coded and tested! <br />Iteration 2 – coded and tested! <br />Iteration 3 – coded and tested! <br />Iteration 4 – coded and tested! <br />Where’s the problem?<br />No regression testing – “done” for an iteration means all previous testing passes as well! The above scenario leads to:<br />Final validation testing – FAILS! <br />Failing with Agile<br />12<br />
    13. 13. Identifying tasks – but not all of them<br />Failing with Agile<br />13<br />
    14. 14. The daily stand-up of death<br />Yesterday I did that, today I’ll do this, nothing blocking me. Next…<br />Failing with Agile<br />14<br />
    15. 15. Inadvertent sabotage<br />Hurting by helping!<br />
    16. 16. Working ahead<br />I know we are only initeration 1, but I did story3 and knew that story 322depended on it, so I did thatone too! Cool huh!<br />Failing with Agile<br />16<br />
    17. 17. The return of command and control<br />I thought agile was supposed to empower us?!?<br />Failing with Agile<br />17<br />
    18. 18. Hmm, how should I do this?<br />I don’t really know how to solve this, but that’s ok, I’ll just think like a customer<br />Good developers will try to think like a customer – THEN they will make the wrong decision!<br />Failing with Agile<br />18<br />
    19. 19. Invite complexity<br />Mr. Product Champion, which way should I go?<br />It doesn’t affect the user, so pick either!<br />Complex – Yeah!<br />Failing with Agile<br />19<br />
    20. 20. Small Group Exercise<br />Describe inadvertent sabotage you have experienced. What were the results and how it was first detected?<br />Failing with Agile<br />20<br />
    21. 21. Failures caused by management<br />
    22. 22. Lack of sufficient agile training<br />Dilbert knows agile! <br />Or, maybe not <br />Failing with Agile<br />22<br />
    23. 23. Asking “How are we doing?”<br />Hey George, how are we doing?<br />Apparently executives and managers have no eyes!<br />Failing with Agile<br />23<br />
    24. 24. Early hiccup = total failure<br />See! Iteration 1 wasn’t perfect. I told you agile wouldn’t work!!!<br />Failing with Agile<br />24<br />
    25. 25. Seeding doubt<br />Psst. Be careful. I’m pretty sure this agile stuff will fail.<br />Failing with Agile<br />25<br />
    26. 26. Always follow the chain of command!<br />I don’t care if it worked. This is the org chart and you should have asked me (even if it would have taken 5 extra days).<br />Let’s make some spaghetti to show this in action!<br />Failing with Agile<br />26<br />
    27. 27. Small Group Exercise<br />List a few different forms of management failure you have experienced and what happened.<br />Failing with Agile<br />27<br />
    28. 28. Failures caused by Waste<br />
    29. 29. What is waste?<br />Anything that does not add value!<br />Meetings, research that is never utilized, unfinished code, untested code, undocumented/unusable features…<br />What else?<br />Failing with Agile<br />29<br />
    30. 30. Building what you don’t need<br />Question: What percentage of software features are NEVER used?<br />Failing with Agile<br />30<br />
    31. 31. Poor requirements gathering technique<br />Failing with Agile<br />31<br />
    32. 32. Building infrastructure first<br />Slices = less<br />work to do<br />Layers = All<br />work done<br />Which is easier to change?<br />Failing with Agile<br />32<br />
    33. 33. Being dogmatic about process<br />Agile says we have to have daily stand-ups. It doesn’t matter that part of the team is in Sri Lank 12.5 time zones away!<br />Failing with Agile<br />33<br />
    34. 34. Small Group Exercise<br />What are some types of waste in your organization that you can start to eliminate immediately?<br />Failing with Agile<br />34<br />
    35. 35. Team failure modes<br />
    36. 36. Play the blame game<br />It’s your fault!<br />Failing with Agile<br />36<br />
    37. 37. It’s ok to move things to the next iteration<br />This didn’t finish, so move it from iteration 1 to iteration 2, no 3, I mean 4.<br />Failing with Agile<br />37<br />
    38. 38. Teams that are too large<br />Will this stand-up ever end?<br />Failing with Agile<br />38<br />
    39. 39. Make silos even deeper<br />Testers vs. DevelopersIs anyone a team member any more???<br />Failing with Agile<br />39<br />
    40. 40. Poor communication<br />Failing with Agile<br />40<br />
    41. 41. Not my job<br />See, right there it says it isn’t my job to do that!<br />It’s not my fault the team failed the iteration because I didn’t press “Run”<br />Failing with Agile<br />41<br />
    42. 42. Small Group Exercise<br />Even successful teams are held back in many ways by the way they do things. What “failures” are your current teams dealing with today?<br />Failing with Agile<br />42<br />
    43. 43. Product Champion based failures<br />
    44. 44. Keep the plan in your head…<br />Don’t ever tell anyone else what the plan is. That way they need to rely on you, right???<br />Failing with Agile<br />44<br />
    45. 45. Be efficient – have more than one role<br />It’s great being a team member, Scrum Master and Product Champion! All have to bow to me!!! Oh, and all my stuff gets done first – sweeeeeeet!<br />Failing with Agile<br />45<br />
    46. 46. Testing failures<br />
    47. 47. Confusing unit tests and acceptance tests<br />Automated(QA)<br />Business Facing<br />Manual(Anyone)<br />UsabilityTesting <br />ExploratoryTesting<br />Acceptance Tests<br />Business Intent(Design of the Product)<br />When possible<br />Support Programming<br />Critique Product<br />During Iteration<br />PropertyTesting<br />Response, SecurityScaling,…<br />Unit Tests<br />Developer Intent (Design of the Code)<br />Automated(Developer)<br />Tool-Based(Expensive)<br />Technology Facing<br />from Brian Marick<br />Failing with Agile<br />47<br />
    48. 48. Testing at the end of an iteration<br />Code Freeze<br />Day 10<br />Day 1<br />Day 2<br />Day 3<br />Day 4<br />Day 5<br />Day 6<br />Day 7<br />Day 8<br />Day 9<br />Coding<br />Testing<br />Q: What are developers doing during the testing period?<br />Failing with Agile<br />48<br />
    49. 49. Coding in one iteration, testing in the next<br />Each tester<br />40% of time writing tests for current iteration<br />20% of time running tests for current iteration<br />40% of time regression testing<br />Iteration 1 this tester has 40% slack time<br />Iteration 2 this tester has 20% slack time<br />40% writing new tests, 20% running new tests, 20% running tests from iteration 1<br />Iteration 3 this tester has 0 slack time<br />40% writing new tests, 20% running new tests, 20% running tests from iteration 1, 20% running tests from iteration 2<br />Iteration 4 we can no longer complete all testing!<br />This is most often caused by dependence on manual testing<br />Failing with Agile<br />49<br />
    50. 50. Lack of automated testing<br />Failing with Agile<br />50<br />Regression Deficit Disorder<br />
    51. 51. Group discussion<br />What testing challenges currently exist in your organization?<br />Failing with Agile<br />51<br />
    52. 52. Failures due tolack of trust<br />
    53. 53. Measure inappropriately<br />You will get what you measure!!!<br />DILBERT: © Scott Adams/Dist. by United Feature Syndicate, Inc.<br />Failing with Agile<br />53<br />
    54. 54. The “no power” Product Champion<br />I know you told the team to do that, but I’m your manager and I think it’s wrong, so change it!<br />Failing with Agile<br />54<br />
    55. 55. Agile in name only<br />Here is the scope and the date, now be agile and deliver it all on time!<br />Failing with Agile<br />55<br />
    56. 56. Micromanagement<br />This project is important and as CTO, I want to make sure we’re measuring up every day!<br />Failing with Agile<br />56<br />
    57. 57. Process failures<br />
    58. 58. Changing process before it is understood<br />This is a simple process, why do we need to meet each day to discuss things?<br />Failing with Agile<br />58<br />
    59. 59. Lack of commitment to improvement<br />Woohoo! A new record! That retrospective only took 2 minutes!!!<br />Failing with Agile<br />59<br />
    60. 60. Watching metrics, not the people<br />Great job! Another successful iteration.<br />Failing with Agile<br />60<br />
    61. 61. Fixing failure<br />
    62. 62. Small Group Exercise<br />Talk about some fixed failures and how they were fixed. Talk about some failings that are not yet fixed and what might be done to fix them.<br />Failing with Agile<br />62<br />
    63. 63. Agile Expectations<br />
    64. 64. What others are seeing<br />Failing with Agile<br />64<br />
    65. 65. VersionOne Survey Results (2008)<br />Survey asked people: Please try to estimate SPECIFIC IMPROVEMENTS you have actually realized from implementing Agile practices.<br />Source: VersionOne 2008 State of Agile Development Survey<br />NOTE: All 2008 data is within 2% of 2007 data implying these numbers are not one-time anomalies<br />Biggest causes of company-wide agile failure:<br /> Company philosophy or culture could not be overcome – 23%<br /> Lack of experience with agile – 21%<br />Failing with Agile<br />65<br />
    66. 66. Agile is a Proven ApproachSome Agile Companies (there are MANY more)<br />Failing with Agile<br />66<br />
    67. 67. Resources<br />
    68. 68. Places to go for help<br />My website!<br />Organizations<br />Agile Alliance (<br />Agile Project Leadership Network (APLN – <br />Yahoo Groups<br />PMI Agile (pmiagile) – giving direction to people that will be responsible for the Agile PMI Virtual Community to be formed in 2009<br />Agile Denver (agiledenver)<br />APLN Denver (apln-denver)<br />Failing with Agile<br />68<br />
    69. 69. Retrospective<br />
    70. 70. Help me out!<br />I’m doing this again at the PMI Mile Hi Symposium in March 2009 and I want to make sure it is as good as possible!<br />What went well?<br />What went less well?<br />How can I improve things next time?<br />Failing with Agile<br />70<br />
    71. 71. Final questions?<br />
    72. 72. Thank you!<br />Please fill out evaluation forms<br />Get on my mailing list if you want to receivea PDF of this presentation via email<br />