deep agile blending scrum and extreme programming
play

Deep Agile Blending Scrum and Extreme Programming Jeff Sutherland - PowerPoint PPT Presentation

Deep Agile Blending Scrum and Extreme Programming Jeff Sutherland Ron Jeffries Separation of XP and Scrum Methods * Largely Historical * XP chose to write more down * XP programmer focus * Successful Scrum Teams use XP-like Practices


  1. Deep Agile Blending Scrum and Extreme Programming Jeff Sutherland Ron Jeffries

  2. Separation of XP and Scrum Methods * Largely Historical * XP chose to write more down * XP “programmer” focus * Successful Scrum Teams use XP-like Practices April 28-29, Deep Agile -- XP and Scrum Ron - 2 2007

  3. Need for “Technical” Practices * Interative Planning and Delivery * Feature Focus * � * Incremental Design * Frequent Testing April 28-29, Deep Agile -- XP and Scrum Ron - 3 2007

  4. XP Practices not Purely Technical * User Stories * Cards * Informative Workspace * Big Visible Charts * Tracking Boards * Planning Game * Small Releases * … etc April 28-29, Deep Agile -- XP and Scrum Ron - 4 2007

  5. Developer Focus * Low in Scrum * (discovery) * Higher in XP * (starting point) April 28-29, Deep Agile -- XP and Scrum Ron - 5 2007

  6. XP’s Project Management Practices * Compatible with / Analogous to Scrum * Small Releases * Whole Team * Planning Game * Iteration Planning * Release Planning * … April 28-29, Deep Agile -- XP and Scrum Ron - 6 2007

  7. XP Practices * What are they? * Their role in Scrum … or any project. April 28-29, Deep Agile -- XP and Scrum Ron - 7 2007

  8. XP Practice * Simple Design * Must proceed incrementally * Must deliver features right away * � * Begin with a simple design April 28-29, Deep Agile -- XP and Scrum Ron - 8 2007

  9. XP Practice * Pair Programming * Design is changing … * How do we know what it is? April 28-29, Deep Agile -- XP and Scrum Ron - 9 2007

  10. XP Practice * Test-Driven Development * System must work all the time; * Must ship every week or two; * How do we know it isn’t broken? * Test it! April 28-29, Deep Agile -- XP and Scrum Ron - 10 2007

  11. XP Practice * Refactoring * Simple Design cannot last! * Are we doomed??? * Design must improve … * Refactoring is the technique * (Refactoring: Martin Fowler) April 28-29, Deep Agile -- XP and Scrum Ron - 11 2007

  12. XP Practice * Continuous Integration * We’ll be integrating at least every two weeks; * Integration is always hell; * Get good at it! April 28-29, Deep Agile -- XP and Scrum Ron - 12 2007

  13. XP Practice * Shared Code * “Any pair can improve any code at any time” * -- Kent Beck * Faster progress * More eyes * Higher Quality April 28-29, Deep Agile -- XP and Scrum Ron - 13 2007

  14. XP Practice * Coding Standard * All eyes on all code * Make it look alike * Don’t go crazy – just make it look alike April 28-29, Deep Agile -- XP and Scrum Ron - 14 2007

  15. XP Practice * Whole Team * All the people you need * When you need them * Technical Resources * Business Resources April 28-29, Deep Agile -- XP and Scrum Ron - 15 2007

  16. XP Practice * User Stories * Card * Conversation * Confirmation April 28-29, Deep Agile -- XP and Scrum Ron - 16 2007

  17. XP Practice * Automated Customer Tests * How often do you need to test this? * How often do you want to test it by hand anyway??? April 28-29, Deep Agile -- XP and Scrum Ron - 17 2007

  18. XP Practice * Informative Workspace * Tracking Boards * Big Visible Charts April 28-29, Deep Agile -- XP and Scrum Ron - 18 2007

  19. XP Practice * Energized Work * Work vigorously * Rest effectively * Be done at the end of every day! April 28-29, Deep Agile -- XP and Scrum Ron - 19 2007

  20. XP Practice * Sustainable Pace * If you go too fast, you’ll go off the road! * Do not push for more stories!! April 28-29, Deep Agile -- XP and Scrum Ron - 20 2007

  21. XP Practice * Slack * Have items on the list that can be dropped * You can always ask for more * Something will come up April 28-29, Deep Agile -- XP and Scrum Ron - 21 2007

  22. XP Practice * Weekly Cycle April 28-29, Deep Agile -- XP and Scrum Ron - 22 2007

  23. XP Practice * Quarterly Cycle April 28-29, Deep Agile -- XP and Scrum Ron - 23 2007

  24. XP Practice * Code and Tests * These are the only documents that count * Generate the rest! April 28-29, Deep Agile -- XP and Scrum Ron - 24 2007

  25. XP Practice * Team Continuity * Software is a work of the mind * Why throw that away? April 28-29, Deep Agile -- XP and Scrum Ron - 25 2007

  26. XP Practice * Single Code Base * Anything else is waste! * Learn to do it right * Generate old versions if you must – Don’t save them April 28-29, Deep Agile -- XP and Scrum Ron - 26 2007

  27. XP Practice * Daily Deployment * Go home clean! * Deliver value instantly! April 28-29, Deep Agile -- XP and Scrum Ron - 27 2007

  28. XP Practice * Incremental Design * (Discussed – Refactoring) April 28-29, Deep Agile -- XP and Scrum Ron - 28 2007

  29. XP Practice * Sit Together * And talk with each other! * Would you rather have a hug from your Mom, or a nice note? April 28-29, Deep Agile -- XP and Scrum Ron - 29 2007

  30. XP Practice * Ten Minute Build * Yes, we really mean it April 28-29, Deep Agile -- XP and Scrum Ron - 30 2007

  31. XP Practice * Real Customer Involvement * Don’t guess – find out. * Set their expectations * Help them learn too April 28-29, Deep Agile -- XP and Scrum Ron - 31 2007

  32. XP Practice * Incremental Deployment April 28-29, Deep Agile -- XP and Scrum Ron - 32 2007

  33. XP Practice * Shrinking Teams * As need declines … * People move on April 28-29, Deep Agile -- XP and Scrum Ron - 33 2007

  34. XP Practice * Root Cause Analysis * “Ask Why Five Times” April 28-29, Deep Agile -- XP and Scrum Ron - 34 2007

  35. XP Practice * … and many many more … * The richness of software development … * And of how to do it … * Cannot be plumbed by any list! April 28-29, Deep Agile -- XP and Scrum Ron - 35 2007

  36. Forces and Responses * These practices are not random, * Nor are they mandatory * But they are needed * And there are reasons why April 28-29, Deep Agile -- XP and Scrum Ron - 36 2007

  37. Forces and Responses * Teamwork * Team Room * 2X Productivity!! * Don’t Specialize * Don’t Hand Off * Pair Programming * Shared Code April 28-29, Deep Agile -- XP and Scrum Ron - 37 2007

  38. Forces and Responses * Business Value * Small Stories * Avoid Tasks * Automated Customer Acceptance Tests April 28-29, Deep Agile -- XP and Scrum Ron - 38 2007

  39. Automated Customer Acceptance Tests * Communcation * Learning * Confidence * Repetition! April 28-29, Deep Agile -- XP and Scrum Ron - 39 2007

  40. Forces and Responses * Continuous Delivery * Grow the Design * Refactoring * Continuous Integration * Ten Minute Build * Shared Code * Energized Work * Sustainable Pace April 28-29, Deep Agile -- XP and Scrum Ron - 40 2007

  41. Forces and Responses * Predictability * Get Done = Done * Tests * Test-Driven Development * Stories vs Tasks April 28-29, Deep Agile -- XP and Scrum Ron - 41 2007

  42. XP and Scrum and XP and … * Fundamental Message * Focus on what your team needs * Focus on Running Tested Features * Done =Done * Not “Is it Scrum?” * Not “Is it XP?” * “Is it working for us?” April 28-29, Deep Agile -- XP and Scrum Ron - 42 2007

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend