Is Agile Better

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    1 Favorite

    Is Agile Better - Presentation Transcript

    1. Is Agile Any Better? Damon Poole 2009 Is Agile Any Better?
    2. Agenda
      • How and why Agile works
      • Scaling Agile
      • Benefits of Agile
      • Is Agile any better?
      • Q&A
    3. Basic Approach of Traditional Development Specify Design Code Integrate Write tests Test D C W W T T Specify Design Code Integrate Write Tests Test Cancelled or shelved S D C I W T S S S S D D D D C C C C I I I I W W W W T T T T S I W T I T W C D S D C
    4. User Stories
      • When a customer visits the web site, use a cookie to remember who they are. On each visit, look for the cookie and associate it with their account information. Whenever the customer is looking at an item which may be purchased, present a “buy” button next to the item. When the user clicks on the button, combine the information from the item and the user account to place an order using their default shipping and default credit card information. Allow the user to cancel any order for up to 4 hours after they place an order.
      • “ As a user I want to order what I am browsing with a single click .”
      • As a <user role> I want to <achieve some goal>
    5. Agile At a Glance new reviewed Issue Story Points Effort Remaining State Assignment 432 User wants layout pleasing to the eye 2 reviewed - 420 User wants example templates to choose from 3 reviewed - 419 Admin wants zero installation 5 reviewed - 612 Manager wants dashboard view 5 reviewed - 599 Admin wants LDAP integration 5 reviewed - 831 Admin wants self-serve password reset 2 reviewed - 692 User wants automatic todo list generation 2 reviewed - 432 User wants easy task entry 1 reviewed - 119 User wants subscription-based e-mail notification 5 reviewed - 332 Marketing wants fancy splash screen 3 reviewed - 516 Admin wants 1-click license update 2 reviewed - 533 User wants app to be ready in 3 seconds or less 5 reviewed - 619 User wants app to work using Chrome 5 reviewed -
    6. Agile At a Glance new Backlog (APM) reviewed todo $$$ $
    7. Agile At a Glance new Backlog (APM) reviewed todo wip coded tested done Iteration Burnup 10/2 10/4 10/9 10/11 10/11 10/15 10/17 10/19 10/23 10/25 10 20 30 40 0 Story Points
    8. Agile At a Glance new Retrospective Backlog (APM) reviewed todo wip coded tested done prod 9612 as a user I want… 6921 as a user I want… 6291 as a dba I want… 2196 as an admin I… 1962 as an admin I… 1296 as a casual user I… 1269 as a dba I want… Iteration Review
    9. Agenda
      • How and why Agile works
      • Scaling Agile
      • Benefits of Agile
      • Is Agile any better?
      • Q&A
    10. One Piece Flow (Lean Principle) D S D C W T I S D C W T I S D C W T I S C S D I T W Specify Design Code Integrate Write tests Test C W T I D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S Crunch Time Big Bang
    11. Continuous Integration C S D I T W Continuous Integration D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S D C W T I S I I I I I I I I I I I I I I I I I I I I
    12. Leveraging People’s Memory and Conversations Customers Product Manager Architect Developers Testers 2 months 1 month 4 months Customers 2 months 9 mos. Customers Team Customers 1 month Traditional Development Agile Development days Developer Test & Doc
    13. $5M per lane $11M per lane
    14. “ Complete” Feature Sets $$ Architecture Architecture Highest Value Full Featured Future Proof “ Complete” Traditional Development Agile Development $$
      • Done as a unit
      • Ready at the end
      • Feedback at the end
      • Some features every iteration
      • Feedback every iteration
      • Re-plan after every iteration
      A A A A A A A A A
    15. Collocation
      • 2-4 mega bit
      • High latency
      • Not always avail.
      • Gigabit
      • Low latency
      • Usually available
      4 file servers 4 db servers 4 app servers 4 build machines 4 test environments San Jose Boston Chennai Kiev
    16. Collocation
      • Low bandwidth
      • High latency
      • Not always avail.
      • High bandwidth
      • Low latency
      • Usually available
      San Jose Boston Chennai Kiev Architect Developer Doc writer Product Manager Tester
    17. Collocation Infrequent coordination Constant communcation San Jose Boston Chennai Kiev Architect Developer Doc writer Product Owner Tester
    18. Agenda
      • How and why Agile works
      • Scaling Agile
      • Benefits of Agile
      • Is Agile any better?
      • Q&A
    19. Traditional Development vs. Agile Traditional Development Agile Development Highest Business Value prepare code test Jan Mar May Jul Nov $$ $ $$ $$ $$ $$$ Dec Feb Apr Jun Problems with this release $$ $$ $$ Facebook Facebook Photo SMS Photo SMS RSS feeds Second Life Second Life RSS feeds Facebook Second Life RSS feeds write tests Facebook RSS feeds Photo SMS Facebook Facebook RSS feeds Problems with this release 1 month iterations 2: Options/Flexibility 1: Higher Quality 3: Visibility 4: Higher ROI, sooner 2: Options/Flexibility 1: Higher Quality 3: Visibility 4: Higher ROI, sooner
    20. Benefits for Individuals
      • Less cancelled or shelved work
      • Less pressure/stress
      • More ownership/involvement
      • Increased project success/viability
    21. Agenda
      • How and why Agile works
      • Scaling Agile
      • Benefits of Agile
      • Is Agile any better?
      • Q&A
    22.  
    23. 14 “Critical Mass” Agile Practices Continuous Integration One Piece Flow Whole Teams User Stories “ As a <persona> I want <behavior> Unit Tests Collocation Iteration Review Refactoring Product Owner Backlog Retrospectives ? Daily Standup Short Iterations $$$ $
    24. Many Practices Take Whole Books to Describe
    25. Conclusion
      • Agile leverages people’s strengths
      • Agile teams design code to be changed instead of trying to avoid the need to change code
      • Key differences
        • Whole teams
        • Short iterations
        • Incremental design
        • Frequent feedback
        • Customer involvement
        • Higher visibility
      • There is a large body of knowledge for how to do Agile
    26. Resources/Q&A
      • Damon Poole ( [email_address] ) http://damonpoole.blogspot.com
      • http://www.accurev.com/agile-resource-center.html
      • Continuous Integration, Paul M. Duvall
      • The Toyota Way – Jeffrey Liker
      • Extreme Programming Explained - 2nd Edition, Kent Beck
      • Agile Software Development with Scrum, Ken Schwaber & Mike Beedle
      • Lean Software Development, Mary Poppendieck and Tom Poppendieck

    + MHeusserMHeusser, 1 month ago

    custom

    150 views, 1 favs, 0 embeds more stats

    Damon Poole, founder and CTO of Accurev, presented more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 150
      • 150 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 0
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories