Agile's Dirty Secret

1,165 views

Published on

Published in: Business, Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,165
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
12
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • The tale of 2 teams from 2 citiesAGILE MANDATE - 1 team has a huge legacy release product that is earning$$UsersBig(ish) dataAgile is a mandate the prevents work from getting doneTDDMeetings1 Teams is pre-releaseAgile mindedTechnical PracticesCommon Values?Agile Manifesto
  • The new RUP?Largest Process seems to get the most attention.Larger process must have more answers
  • WaterfallPSI Thinking
  • 1.) Points Focus!Customer value is at MMF and FeaturesDelivery/Scrum teams are focused on delivering user stories2.) Work BreakdownHard to deliver iteratively – User Profile Management is ONE ITEM
  • LinearAssumes a single release for each activityMapSurfaceMultiple release per activity
  • Large team of 20 developersAgile is a process, not a mindsetLarge Legacy productHistory of system reliability/stability problemsLittle success with TDD behaviorsLong regression cycle -> Automated Regression TestingBrittle and long runningNO LOCAL DATABASE
  • What do I do?1.) Validate external system2.) Write a broken automated test for each defect at the smallest boundary possible3.) Overtime…clusters will form
  • In the beginning – Teams were smallishOver time they grew and were not rebalanced
  • Negotiation generates options
  • Responsibility“My story is done, but the other team isn’t done with with their work. Should I split the User Story?”FEEDING – Bad PO results in failureENVIRONMENT -
  • Lessons:ConstraintsPerfectionAgile Mindset/Continuous ImprovmentContinuous DeploymentFeature Hiding Toggle User/Groups Hierarchy?When asked a questionNever ReleasedLife after acceptance
  • Agile's Dirty Secret

    1. 1. Agile’s Dirty Secret Tim Gifford Lean TECHniques @TimGifford http://www.flickr.com/photos/93413187@N06/8492516706/
    2. 2. Lean TECHniques Agile/Lean/XP Coaching Product Strategy Defect Free Software Delivery Money Back Guarantee
    3. 3. What’s the secret? http://www.flickr.com/photos/bestraft/
    4. 4. Remember when... agile was a mindset not a process?
    5. 5. Manifesto for Agile Software Development • Individuals and interactions over processes and tools • Working software over comprehension documentation • Customer collaboration over contract negotiation • Responding to change over following a plan
    6. 6. Sprint Test Sprint Develop Sprint PSI – 8 weeks Design Requirements SAFe Planning Sprint
    7. 7. PSI Demo
    8. 8. Planning: Artifacts (or WBS) • Epics • MMF –Features »User Stories • Acceptance Criteria • Examples/GWT
    9. 9. Planning: List or Map List Profiles Discounts Map Profiles •A •B •C Discounts •A •B •C
    10. 10. Incremental and Iterative
    11. 11. Incremental
    12. 12. Iterative
    13. 13. Lessons Learned • Weinberg's - Law of Raspberry Jam • 2nd Team Problem • Incremental & Iterative • Release Planning
    14. 14. Story: Automated Testing Tragedy http://wlppr.com/2010/10/10/robot-attack
    15. 15. Testing Boundaries ~230 10 10 1000 100 10 10 100 10 1 10 10 100 10 ~1
    16. 16. Testing External Systems Current System External Systems
    17. 17. Lessons Learned • Test Boundaries • Knowledge doesn’t change behavior • Large Problems need Leadership & Courage – Self Organizing not Self Managed
    18. 18. Story: Large Teams http://www.flickr.com/photos/cncphotos/
    19. 19. Large Teams – How did we get here? • Initially – 7 +/- 2 • More people => fewer questions => less learning • More meetings/communication • Interpersonal issues on a team • Diluted Responsibility
    20. 20. Small Feature Teams • Roll out with constraints – Size – Geography – Co-location – Duration – Separate meetings – Full Stack
    21. 21. Small Feature Teams – Structure Feature Team Marketing PO Feature Team Feature Team Why and When What and How QA
    22. 22. Large Teams - Lessons Learned • Inverse relationship with size – Responsibility – Engagement • No Sprint “Defects” • Support emerging leadership • 100% Time
    23. 23. Story: Agile Confidence http://www.flickr.com/photos/reidmix/
    24. 24. Done, Done, Done? Backlog In Process Accepted Production
    25. 25. Agile Confidence - Lessons Learned • Delivery requires constraints • Responding to Change over Having a Plan – Perfection is the enemy of “good enough”
    26. 26. Story: Drowning in Defects
    27. 27. Value Stream Map CS submits defect Devs “triage” defect Devs fix defect Release to production 10 minutes 1-2 hours 1-2 days 2 hours 1-3 days 30-120 days 2-30 days Efficiency: 1.6% - 7.5% 2.5 days 33-153 days
    28. 28. Prioritization Priority Severity Customer Characterization High High Angry High Low Angry Low High Angry Medium High Angry
    29. 29. Variability == Angry Customers • • • • Lies! Angry Customers call CEOs CEO prioritizes defects above all else Repeat • Defect age from 2 hours to 2 years
    30. 30. FIFO
    31. 31. Defects – Lessons Learned • Prioritization can be waste • Capacity needs to align with demand • Leadership doesn’t come from authority
    32. 32. Thank you Tim Gifford @timgifford tgifford@leantechniques.co CelebrityAgilist.com/agileday

    ×