Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Death to project documentation with eXtreme Programming

1,839 views

Published on

How to connect the agile principle "Working software over comprehensive documentation" with eXtreme Programming values of Honest communication and Rapid feedback and practices as TDD, Continuous integration, Whole team and Small releases.

We will analyze why blending those ideas and techniques together in the real world, remove any need of upfront documentation and increases quality, communication and confidence.

Published in: Technology
  • Read this fabulous site and invested in a steam shower and never glanced back, fantastic resources on this website cannot say thanks enough. HelpWriting.net
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Death to project documentation with eXtreme Programming

  1. 1. Death to project documentation with XP
  2. 2. Yet Another Perl Conference Europe Fundation 2015
  3. 3. Yet Another Perl Conference Europe Fundation 2015
  4. 4. “As developer I find project documentation very useful and I love to keep it up to date”
  5. 5. “As developer I find project documentation very useful and I love to keep it up to date” - no one - - never -
  6. 6. Documentation is...
  7. 7. Documentation is... Simply duplication
  8. 8. Requirements document Emails Technical Analysis Domain model Test Plan Task tracker Code
  9. 9. Documentation is... Hard to keep up to date
  10. 10. Requirements document Emails Technical Analysis Domain model Test Plan Tasks tracker Code Requirements document Requirements documentTechnical Analysis Technical Analysis Technical Analysis Code Code Code Test Plan Domain model Domain model Emails Emails Emails Emails Domain model Task tracker Requirements document Emails Test PlanRequirements document Requirements document Test Plan Domain model
  11. 11. Requirements document Emails Technical Analysis Domain model Test Plan Tasks tracker Code Requirements document Requirements documentTechnical Analysis Technical Analysis Technical Analysis Code Code Code Test Plan Domain model Domain model Emails Emails Emails Emails Domain model Task tracker Requirements document Emails Test PlanRequirements document Requirements document Test Plan Domain model
  12. 12. Documentation is... Inefficient
  13. 13. Documentation is... Tedious
  14. 14. Simply duplication Hard to keep up to date Inefficient Tedious
  15. 15. Simply duplication Hard to keep up to date Inefficient Tedious
  16. 16. Documentation is... S.H.I.T.
  17. 17. What do we want?
  18. 18. “Create flow by eliminating waste” - Lean Thinking -
  19. 19. “Working software over comprehensive documentation” - Agile Manifesto -
  20. 20. RTF: Running tested features http://ronjeffries.com/xprog/articles/jatrtsmetric/
  21. 21. “Open, Honest communication” - XP Principle -
  22. 22. “Rapid feedback” - XP Principle -
  23. 23. How we do it?
  24. 24. How we do it? True Story
  25. 25. Cross-functional-flat teams D T B Developer Tester Business Analyst Product OwnerP D D D T B D D D D T B D D D D T B D P
  26. 26. Cross-functional teams ● Small ● Same table ● Collaborative
  27. 27. Cross-functional teams ● Small ● Same table ● Collaborative Rapid feedback Communication
  28. 28. Story driven iterations ● Smallest unit of work with value ● Short iterations ● Prioritize every iteration
  29. 29. Story driven iterations Backlog Ready to Dev Ready to Test Ready to Close Release
  30. 30. Prioritize Backlog Backlog Backlog D T B P ● Customer focus ● Business value
  31. 31. Prioritize Backlog Backlog Backlog D T B P ● Prioritize ● Customer focus ● Business valueCommunication Eliminatewaste Rapid feedback Workingsoftware
  32. 32. 3 Amigos Backlog B Ready to Dev T D ● Acceptance criteria ● Split stories ● Solve questions
  33. 33. 3 Amigos Backlog B Ready to Dev T D ● Acceptance criteria ● Split stories ● Solve questions Rapidfeedback Communication
  34. 34. Development Ready to Dev Ready to Test D ● ATDD/TDD ● Pair programming ● CI
  35. 35. Development Ready to Dev Ready to Test D ● ATDD/TDD ● Pair programming ● CICommunication Eliminatewaste Rapid feedback Workingsoftware
  36. 36. Testing Ready to Test Ready to Close ● ACs vs AT review ● Exploratory testing T
  37. 37. Testing Ready to Test Ready to Close ● ACs vs AT review ● Exploratory testing T Rapid feedback Communication
  38. 38. Sign-off Ready to Test Ready to Release ● ACs + AT review B T D
  39. 39. Sign-off Ready to Test Ready to Release ● ACs + AT review ● B T D Communication Eliminatewaste Rapid feedback Workingsoftware
  40. 40. Acceptance tests ● Define/prove system behaviour ● Sync and related to code ● Collaborative ownership
  41. 41. Q&A Alex Fernandez @_alexfdz alexfdz afernandeznogueria

×