Core Agile Values<br />SESSION CODE: DPR302<br />Llewellyn Falco <br />Agile Coach<br />Spun Labs<br />Woody Zuill<br />Sc...
Dice<br />
DemoCowboy Programming<br />Mistakes : 11<br />Cost: $2.75<br />
DemoWaterfall<br />Mistakes : 7<br />Cost: $1.75<br />
DemoAgile<br />Mistakes : 19<br />Cost: 19₵<br />
Methodologies<br />
Core Agile ValueReduce the Cost of Mistakes<br />Ways to mitigate the cost of mistakes<br />Detection (early)<br />Change ...
Mistake #1<br />
Misunderstood Requirement<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (ear...
Never say NeverMisunderstood Requirement<br />Demo<br />Requirements<br />
Recap #1Misunderstood Requirement<br />Onsite Customer<br />Detection<br />1 customer, use your own product<br />Business ...
Mistake #2<br />
Knowledge Silo<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<br />Ch...
Recap #2Knowledge Silo<br />Pair Programming<br />Change<br />½ hour a day, everyday<br />1 person watching<br />Pair Prog...
Mistake #3<br />
Changing Requirement<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<b...
Recap #3Changing Requirement<br />Refactoring<br />Change<br />2 minute steps. Automatic Refactorings<br />Rewrites, Addin...
Mistake #4<br />
Integration<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<br />Chang...
Recap #4Integration<br />Continuous Integration<br />Detection, Area of Effect<br />Automated Build, Source Control<br />K...
Mistake #5<br />
Bugs<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<br />Change (easy...
Bugs<br />Start Code<br />QA<br />End Code<br />
Recap #5Bugs<br />Test Driven Development<br />Detection<br />Write steps in English<br />Test after<br />Frameworks: MSTe...
Test Driven Development ( TDD)<br />// make a new order<br />// buy 10 shirts at R100 each<br />// set sales tax to 10%<br...
Mistake #6<br />
Built Something Users Didn’t Like<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detect...
Recap #6Built Something Users Didn’t Like<br />Iterative Development<br />Detection<br />Reduce Scope to 2 weeks.<br />Par...
Iterative Development<br />Requirements<br />2 Small Circles in Center <br />Line at bottom<br />Rectangle around  everyth...
Iterative Development<br />VS<br />
CommonAgile Practices<br />On Site Customer<br />Pair Programming<br />Refactoring<br />Continuous Integration<br />Test D...
So Cal Code Camp – Jan 29th & 30th <br />Agile Introduction [repeated]<br />10.5 Easy Code Excellence Techniques  [Refacto...
TeachingKidsProgramming.org<br /><ul><li>Do a Recipe  Teach a Kid
Upcoming SlideShare
Loading in...5
×

Core agile values

1,392

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,392
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
25
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • 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 &amp; honeymoon. We couldn’t do anything, and ended up missing the demo.
  • At Mix they announced Windows Phone 7 &amp; 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 &amp; 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 &amp; how it’s easy to convert from WPF. The next day, the client needed it to work on phones.
  • Lynn
  • Core agile values

    1. 1.
    2. 2. Core Agile Values<br />SESSION CODE: DPR302<br />Llewellyn Falco <br />Agile Coach<br />Spun Labs<br />Woody Zuill<br />Scrum Master<br />
    3. 3. Dice<br />
    4. 4. DemoCowboy Programming<br />Mistakes : 11<br />Cost: $2.75<br />
    5. 5. DemoWaterfall<br />Mistakes : 7<br />Cost: $1.75<br />
    6. 6. DemoAgile<br />Mistakes : 19<br />Cost: 19₵<br />
    7. 7. Methodologies<br />
    8. 8. Core Agile ValueReduce the Cost of Mistakes<br />Ways to mitigate the cost of mistakes<br />Detection (early)<br />Change (easy)<br />Area of Effect (reduced)<br />
    9. 9. Mistake #1<br />
    10. 10. Misunderstood Requirement<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<br />Change (easy)<br />Area of Effect (reduced)<br />
    11. 11. Never say NeverMisunderstood Requirement<br />Demo<br />Requirements<br />
    12. 12. Recap #1Misunderstood Requirement<br />Onsite Customer<br />Detection<br />1 customer, use your own product<br />Business analyst. Trust. Tunnel Vision<br />Agile Practice<br />Issue<br />First Steps<br />Common Mistakes<br />Resources<br />Lean Software Development by Mary Poppendieck<br />www.industrialxp.org/sittingTogether.html<br />
    13. 13. Mistake #2<br />
    14. 14. Knowledge Silo<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<br />Change (easy)<br />Area of Effect (reduced)<br />
    15. 15. Recap #2Knowledge Silo<br />Pair Programming<br />Change<br />½ hour a day, everyday<br />1 person watching<br />Pair Programming Illuminated by Laurie Williams<br />Agile Practice<br />Issue<br />First Steps<br />Common Mistakes<br />Resources<br />
    16. 16. Mistake #3<br />
    17. 17. Changing Requirement<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<br />Change (easy)<br />Area of Effect (reduced)<br />
    18. 18. Recap #3Changing Requirement<br />Refactoring<br />Change<br />2 minute steps. Automatic Refactorings<br />Rewrites, Adding Functionality <br />Working Effectively w/Legacy Code by Michael Feathers<br />Clean Code by Robert Martin<br />Agile Practice<br />Issue<br />First Steps<br />Common Mistakes<br />Resources<br />
    19. 19. Mistake #4<br />
    20. 20. Integration<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<br />Change (easy)<br />Area of Effect (reduced)<br />
    21. 21. Recap #4Integration<br />Continuous Integration<br />Detection, Area of Effect<br />Automated Build, Source Control<br />Killing the messenger<br />Agile Practice<br />Issue<br />First Steps<br />Common Mistakes<br />Resources<br />CI: TFS, CruiseControl, Hudson, Team City.<br />SourceControl: TFS, SVN, Git, Mercurial, Tortoise*<br />Build: MsBuild, Nant<br />
    22. 22. Mistake #5<br />
    23. 23. Bugs<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<br />Change (easy)<br />Area of Effect (reduced)<br />
    24. 24. Bugs<br />Start Code<br />QA<br />End Code<br />
    25. 25. Recap #5Bugs<br />Test Driven Development<br />Detection<br />Write steps in English<br />Test after<br />Frameworks: MSTest, Nunit<br />Book: Test Driven Development, Kent Beck<br />Agile Practice<br />Issue<br />First Steps<br />Common Mistakes<br />Resources<br />
    26. 26. Test Driven Development ( TDD)<br />// make a new order<br />// buy 10 shirts at R100 each<br />// set sales tax to 10%<br />// verify order total<br />varorder =newOrder();<br />order.AddItem(“Shirt”, count: 10, price: 100);<br />order.SalesTax = .10;<br />Assert.IsEqual(1100,order.Total);<br />
    27. 27. Mistake #6<br />
    28. 28. Built Something Users Didn’t Like<br />What was the Mistake?<br />How would you mitigate the cost of mistakes?<br />Detection (early)<br />Change (easy)<br />Area of Effect (reduced)<br />
    29. 29. Recap #6Built Something Users Didn’t Like<br />Iterative Development<br />Detection<br />Reduce Scope to 2 weeks.<br />Partial Work doesn’t count.<br />Agile Retrospectives, Esther Derby<br />Succeeding with Agile, Mike Cohn<br />Agile Practice<br />Issue<br />First Steps<br />Common Mistakes<br />Resources<br />
    30. 30. Iterative Development<br />Requirements<br />2 Small Circles in Center <br />Line at bottom<br />Rectangle around everything<br />
    31. 31. Iterative Development<br />VS<br />
    32. 32. CommonAgile Practices<br />On Site Customer<br />Pair Programming<br />Refactoring<br />Continuous Integration<br />Test Driven Development (TDD)<br />Iterative Development (Scrum)<br />
    33. 33. So Cal Code Camp – Jan 29th & 30th <br />Agile Introduction [repeated]<br />10.5 Easy Code Excellence Techniques [Refactoring]<br />A Hands On Coding Dojo - Part 1 & 2 [ TDD ]<br />
    34. 34. TeachingKidsProgramming.org<br /><ul><li>Do a Recipe  Teach a Kid
    35. 35. Free Courseware (recipes)
    36. 36. Ages 10 ++
    37. 37. Microsoft SmallBasic</li></li></ul><li>Contact<br />Woody Zuill<br />wzuill@yahoo.com<br />Llewellyn Falco<br />llewellynfalco.blogspot.com<br />@isidore_us<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×