More Related Content
Viewers also liked
Viewers also liked (15)
Similar to Agile's Dirty Secret
Similar to Agile's Dirty Secret (20)
Recently uploaded
Recently uploaded (20)
Agile's Dirty Secret
- 1. Agile’s Dirty Secret Tim Gifford Lean TECHniques @TimGifford http://www.flickr.com/photos/93413187@N06/8492516706/
- 4. Lean TECHniques Agile/Lean/XP Coaching Product Strategy Defect Free Software Delivery Money Back Guarantee
- 7. Remember when... agile was a mindset not a process?
- 8. 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
- 10. Sprint Test Sprint Develop Sprint PSI – 8 weeks Design Requirements SAFe Planning Sprint
- 11. PSI Demo
- 12. Planning: Artifacts (or WBS) • Epics • MMF –Features »User Stories • Acceptance Criteria • Examples/GWT
- 13. Planning: List or Map List Profiles Discounts Map Profiles •A •B •C Discounts •A •B •C
- 15. Incremental
- 16. Iterative
- 19. Lessons Learned • Weinberg's - Law of Raspberry Jam • 2nd Team Problem • Incremental & Iterative • Release Planning
- 20. Story: Automated Testing Tragedy http://wlppr.com/2010/10/10/robot-attack
- 22. Testing External Systems Current System External Systems
- 23. Lessons Learned • Test Boundaries • Knowledge doesn’t change behavior • Large Problems need Leadership & Courage – Self Organizing not Self Managed
- 25. 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
- 26. Small Feature Teams • Roll out with constraints – Size – Geography – Co-location – Duration – Separate meetings – Full Stack
- 27. Small Feature Teams – Structure Feature Team Marketing PO Feature Team Feature Team Why and When What and How QA
- 28. Large Teams - Lessons Learned • Inverse relationship with size – Responsibility – Engagement • No Sprint “Defects” • Support emerging leadership • 100% Time
- 30. Done, Done, Done? Backlog In Process Accepted Production
- 31. Agile Confidence - Lessons Learned • Delivery requires constraints • Responding to Change over Having a Plan – Perfection is the enemy of “good enough”
- 32. Story: Drowning in Defects
- 33. 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
- 35. Variability == Angry Customers • • • • Lies! Angry Customers call CEOs CEO prioritizes defects above all else Repeat • Defect age from 2 hours to 2 years
- 36. FIFO
- 37. Defects – Lessons Learned • Prioritization can be waste • Capacity needs to align with demand • Leadership doesn’t come from authority
Editor's Notes
- 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