Core agile values
•Download as PPTX, PDF•
3 likes•961 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.
Report
Share
Core agile values
- 2. Core Agile ValuesSESSION CODE: DPR302Llewellyn Falco Agile CoachSpun LabsWoody ZuillScrum Master
- 3. Dice
- 4. DemoCowboy ProgrammingMistakes : 11Cost: $2.75
- 5. DemoWaterfallMistakes : 7Cost: $1.75
- 6. DemoAgileMistakes : 19Cost: 19₵
- 8. Core Agile ValueReduce the Cost of MistakesWays to mitigate the cost of mistakesDetection (early)Change (easy)Area of Effect (reduced)
- 9. Mistake #1
- 10. Misunderstood RequirementWhat was the Mistake?How would you mitigate the cost of mistakes?Detection (early)Change (easy)Area of Effect (reduced)
- 11. Never say NeverMisunderstood RequirementDemoRequirements
- 12. Recap #1Misunderstood RequirementOnsite CustomerDetection1 customer, use your own productBusiness analyst. Trust. Tunnel VisionAgile PracticeIssueFirst StepsCommon MistakesResourcesLean Software Development by Mary Poppendieckwww.industrialxp.org/sittingTogether.html
- 13. Mistake #2
- 14. Knowledge SiloWhat was the Mistake?How would you mitigate the cost of mistakes?Detection (early)Change (easy)Area of Effect (reduced)
- 15. Recap #2Knowledge SiloPair ProgrammingChange½ hour a day, everyday1 person watchingPair Programming Illuminated by Laurie WilliamsAgile PracticeIssueFirst StepsCommon MistakesResources
- 16. Mistake #3
- 17. Changing RequirementWhat was the Mistake?How would you mitigate the cost of mistakes?Detection (early)Change (easy)Area of Effect (reduced)
- 18. Recap #3Changing RequirementRefactoringChange2 minute steps. Automatic RefactoringsRewrites, Adding Functionality Working Effectively w/Legacy Code by Michael FeathersClean Code by Robert MartinAgile PracticeIssueFirst StepsCommon MistakesResources
- 19. Mistake #4
- 20. IntegrationWhat was the Mistake?How would you mitigate the cost of mistakes?Detection (early)Change (easy)Area of Effect (reduced)
- 21. Recap #4IntegrationContinuous IntegrationDetection, Area of EffectAutomated Build, Source ControlKilling the messengerAgile PracticeIssueFirst StepsCommon MistakesResourcesCI: TFS, CruiseControl, Hudson, Team City.SourceControl: TFS, SVN, Git, Mercurial, Tortoise*Build: MsBuild, Nant
- 22. Mistake #5
- 23. BugsWhat was the Mistake?How would you mitigate the cost of mistakes?Detection (early)Change (easy)Area of Effect (reduced)
- 25. Recap #5BugsTest Driven DevelopmentDetectionWrite steps in EnglishTest afterFrameworks: MSTest, NunitBook: Test Driven Development, Kent BeckAgile PracticeIssueFirst StepsCommon MistakesResources
- 26. Test Driven Development ( TDD)// make a new order// buy 10 shirts at R100 each// set sales tax to 10%// verify order totalvarorder =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 LikeWhat 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 LikeIterative DevelopmentDetectionReduce Scope to 2 weeks.Partial Work doesn’t count.Agile Retrospectives, Esther DerbySucceeding with Agile, Mike CohnAgile PracticeIssueFirst StepsCommon MistakesResources
- 30. Iterative DevelopmentRequirements2 Small Circles in Center Line at bottomRectangle around everything
- 32. CommonAgile PracticesOn Site CustomerPair ProgrammingRefactoringContinuous IntegrationTest 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 ]
- 34. TeachingKidsProgramming.orgDo a Recipe Teach a Kid
- 36. Ages 10 ++
- 37. Microsoft SmallBasicContactWoody Zuillwzuill@yahoo.comLlewellyn Falcollewellynfalco.blogspot.com@isidore_us
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