Successfully reported this slideshow.

Scrum club progressiveelaboration-bobvincent

1

Share

Loading in …3
×
1 of 23
1 of 23

More Related Content

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Scrum club progressiveelaboration-bobvincent

  1. 1. Progressive Elaboration & Specification part 3 Agile Analysis & Design The Trilogy
  2. 2. Bob Vincent • Product Manager • XP, Scrum, Lean software projects since 2004 • CSPO, CSM
  3. 3. Progressive Elaboration "Because of the potential for change, the project management plan is iterative and goes through progressive elaboration throughout the project's life cycle. Progressive elaboration involves continuously improving and detailing a plan as more-detailed and specific information and more accurate estimates become available."
  4. 4. Backlog Epics Stories
  5. 5. Agile Stories • Describes an objective & motivation • Does NOT describe the solution • It’s pretty brief - “a promise for a conversation”
  6. 6. Story Title • In order to [provide value] • [persona(s)] • want [a feature]
  7. 7. Acceptance Test- Driven Planning Process Agnostic Defining DONE Participants: Product Owner Testers Devs UX
  8. 8. Acceptance Test-Driven Planning GIVEN [an initial context or condition] WHEN [persona] [does something] THEN [expected behavior occurs]
  9. 9. Behavior/Test-Driven Development Process Agnostic Participants: Testers Devs UX
  10. 10. Behavior/Test-Driven Development • Specify behavior (test) before writing code • Test all the time • Refactor • Design all the time • Code design needs to flex & grow • Add spec/tests for new emergent behavior
  11. 11. User testing A B Usability testing goals: • Effectiveness • Efficiency • Satisfaction
  12. 12. Task
  13. 13. “An interactive session with working software is worth a thousand meetings.”
  14. 14. Backlog Epics Stories++
  15. 15. Thank You!

Editor's Notes

  • notes...\n
  • \n
  • \n
  • \n
  • -may also have UI mockups/Prototypes/User research & other artifacts leading into release.\n-time for Qualitative research: discover unmet needs\n
  • \n
  • \n
  • Rank the backlog - just enough to meet objectives (release date, MMF)\n
  • Sprint / Iteration / Rolling-wave Planning (V1 experimentation)\n
  • define Done\n
  • -PO may have ATs coming in; create more in planning\n-GWT format forces ATs to be broken-down somewhat consistently\n-too many ATs in a story is a smell that the story is too large\n
  • Dev + PO + [Designers]. \n
  • define behavior (solution specific) before code - think thru for better design\nwrite more efficient code\n\n
  • focusing on behavior rather than state = less brittle\n-difficult to predict what comes out of emergent design / expensive to try\n\n
  • \n
  • May expose new ATs. too many==smell\n
  • Opportunity for more user testing (task testing)\nPO verifies ATs - proclaims DONE.\n\n\n
  • \n
  • May expose opportunities for improvement (new stories).\nIdentify features with high risk of iteration & rank them high.\n
  • \n
  • automating all this\n
  • cucumber + rspec\n
  • \n
  • ×