Core agile values
•Download as PPTX, PDF•
3 likes•960 views
This document discusses core agile values and practices for reducing the cost of mistakes. It outlines six common mistakes that can occur: misunderstood requirements, knowledge silos, changing requirements, integration issues, bugs, and building something users don't like. For each mistake, it recommends agile practices for early detection, easy change, and reduced impact including: on-site customers, pair programming, refactoring, continuous integration, test-driven development, and iterative development. It also provides information on upcoming code camps and teaching kids programming.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Core agile values
Similar to Core agile values (20)
More from Llewellyn Falco
More from Llewellyn Falco (20)
Core agile values
- 2. Core Agile Values SESSION CODE: DPR302 Llewellyn Falco Agile Coach Spun Labs Woody Zuill Scrum Master
- 3. Dice
- 4. DemoCowboy Programming Mistakes : 11 Cost: $2.75
- 5. DemoWaterfall Mistakes : 7 Cost: $1.75
- 6. DemoAgile Mistakes : 19 Cost: 19₵
- 8. Core Agile ValueReduce the Cost of Mistakes Ways to mitigate the cost of mistakes Detection (early) Change (easy) Area of Effect (reduced)
- 9. Mistake #1
- 10. Misunderstood Requirement What was the Mistake? How would you mitigate the cost of mistakes? Detection (early) Change (easy) Area of Effect (reduced)
- 11. Never say NeverMisunderstood Requirement Demo Requirements
- 12. Recap #1Misunderstood Requirement Onsite Customer Detection 1 customer, use your own product Business analyst. Trust. Tunnel Vision Agile Practice Issue First Steps Common Mistakes Resources Lean Software Development by Mary Poppendieck www.industrialxp.org/sittingTogether.html
- 13. Mistake #2
- 14. Knowledge Silo What was the Mistake? How would you mitigate the cost of mistakes? Detection (early) Change (easy) Area of Effect (reduced)
- 15. Recap #2Knowledge Silo Pair Programming Change ½ hour a day, everyday 1 person watching Pair Programming Illuminated by Laurie Williams Agile Practice Issue First Steps Common Mistakes Resources
- 16. Mistake #3
- 17. Changing Requirement What was the Mistake? How would you mitigate the cost of mistakes? Detection (early) Change (easy) Area of Effect (reduced)
- 18. Recap #3Changing Requirement Refactoring Change 2 minute steps. Automatic Refactorings Rewrites, Adding Functionality Working Effectively w/Legacy Code by Michael Feathers Clean Code by Robert Martin Agile Practice Issue First Steps Common Mistakes Resources
- 19. Mistake #4
- 20. Integration What was the Mistake? How would you mitigate the cost of mistakes? Detection (early) Change (easy) Area of Effect (reduced)
- 21. Recap #4Integration Continuous Integration Detection, Area of Effect Automated Build, Source Control Killing the messenger Agile Practice Issue First Steps Common Mistakes Resources CI: TFS, CruiseControl, Hudson, Team City. SourceControl: TFS, SVN, Git, Mercurial, Tortoise* Build: MsBuild, Nant
- 22. Mistake #5
- 23. Bugs What was the Mistake? How would you mitigate the cost of mistakes? Detection (early) Change (easy) Area of Effect (reduced)
- 24. Bugs Start Code QA End Code
- 25. Recap #5Bugs Test Driven Development Detection Write steps in English Test after Frameworks: MSTest, Nunit Book: Test Driven Development, Kent Beck Agile Practice Issue First Steps Common Mistakes Resources
- 26. Test Driven Development ( TDD) // make a new order // buy 10 shirts at R100 each // set sales tax to 10% // verify order total varorder =newOrder(); order.AddItem(“Shirt”, count: 10, price: 100); order.SalesTax = .10; Assert.IsEqual(1100,order.Total);
- 27. Mistake #6
- 28. Built Something Users Didn’t Like What was the Mistake? How would you mitigate the cost of mistakes? Detection (early) Change (easy) Area of Effect (reduced)
- 29. Recap #6Built Something Users Didn’t Like Iterative Development Detection Reduce Scope to 2 weeks. Partial Work doesn’t count. Agile Retrospectives, Esther Derby Succeeding with Agile, Mike Cohn Agile Practice Issue First Steps Common Mistakes Resources
- 30. Iterative Development Requirements 2 Small Circles in Center Line at bottom Rectangle around everything
- 32. CommonAgile Practices On Site Customer Pair Programming Refactoring Continuous Integration Test Driven Development (TDD) Iterative Development (Scrum)
- 33. So Cal Code Camp – Jan 29th & 30th Agile Introduction [repeated] 10.5 Easy Code Excellence Techniques [Refactoring] A Hands On Coding Dojo - Part 1 & 2 [ TDD ]
- 36. Ages 10 ++
Editor's Notes
- 7, 9, 5, 6, 37, 6, 5, 8, 4, 115,9,10
- 7, 9, 5, 6, 37, 6, 5, 8, 4, 115,9,10
- #8 – 2, 10#7 – 2 8#2 – 3 5
- 7 ,8,9,10,117,8,9,10,11,12,6,5,42,3,4,5,6,7,8,9
- We set out to create a purchase system for Acme Corp. After 4 months, we demoed to the customer. They said, what about when we have to have PO orders. I replied, your requirement never mentioned anything other than up front payments, and when we spoke you said you never did any other type. They replied, well we basically never do, it’s only once or twice a year.
- Where would you have liked to know about this?
- A week before the next demo, our DBA fell in love and ran off to get married & honeymoon. We couldn’t do anything, and ended up missing the demo.
- At Mix they announced Windows Phone 7 & how it’s easy to convert from WPF if you’ve been doing proper MVVP. The next day, the client needed it to work on phones. It took 3 weeks before our code base even compiled again, and 3 months before it was working again on the phones.
- By this time there were a few teams to handle the different modules. We
- At Mix they announce Windows Phone 7 & how it’s easy to convert from WPF. The next day, the client needed it to work on phones.
- At Mix they announce Windows Phone 7 & how it’s easy to convert from WPF. The next day, the client needed it to work on phones.
- Lynn