Your SlideShare is downloading. ×
0
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Scrum club progressiveelaboration-bobvincent
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Scrum club progressiveelaboration-bobvincent

1,203

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
1,203
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
37
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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
  • Transcript

    • 1. Progressive Elaboration & Specificationpart 3Agile Analysis & Design The Trilogy
    • 2. Bob Vincent• Product Manager• XP, Scrum, Lean software projects since 2004• CSPO, CSM
    • 3. Progressive Elaboration "Because of the potential for change, the project management plan is iterative and goes through progressive elaboration throughout the projects life cycle. Progressive elaboration involves continuously improving and detailing a plan as more-detailed and specific information and more accurate estimates become available."
    • 4. Backlog Epics Stories
    • 5. Agile Stories• Describes an objective & motivation• Does NOT describe the solution• It’s pretty brief - “a promise for a conversation”
    • 6. Story Title • In order to [provide value] • [persona(s)] • want [a feature]
    • 7. Acceptance Test-Driven PlanningProcess Agnostic Defining DONEParticipants:Product OwnerTestersDevsUX
    • 8. Acceptance Test-Driven Planning GIVEN [an initial context or condition] WHEN [persona] [does something] THEN [expected behavior occurs]
    • 9. Behavior/Test-DrivenDevelopmentProcess AgnosticParticipants:TestersDevsUX
    • 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. User testing A BUsability testing goals: • Effectiveness • Efficiency • Satisfaction
    • 12. Task
    • 13. “An interactive session with working software is worth a thousand meetings.”
    • 14. Backlog Epics Stories++
    • 15. Thank You!

    ×