SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
2.
Bob Vincent <ul><li>Product Manager </li></ul><ul><li>XP, Scrum, Lean software projects since 2004 </li></ul><ul><li>CSPO, CSM </li></ul>
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 ."
6.
<ul><li>Describes an objective & motivation </li></ul><ul><li>Does NOT describe the solution </li></ul><ul><li>It’s pretty brief - “a promise for a conversation” </li></ul>Agile Stories
7.
Story Title <ul><li>In order to [provide value] </li></ul><ul><li>[persona(s)] </li></ul><ul><li>want [a feature] </li></ul>
11.
Acceptance Test-Driven Planning GIVEN [an initial context or condition] WHEN [persona] [does something] THEN [expected behavior occurs]
13.
Behavior/Test-Driven Development <ul><li>Process Agnostic </li></ul><ul><li>Participants: </li></ul><ul><ul><ul><ul><li>Testers </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Devs </li></ul></ul></ul></ul><ul><ul><ul><ul><li>UX </li></ul></ul></ul></ul>
14.
Behavior/Test-Driven Development <ul><li>Specify behavior (test) before writing code </li></ul><ul><li>Test all the time </li></ul><ul><li>Refactor </li></ul><ul><li>Design all the time </li></ul><ul><li>Code design needs to flex & grow </li></ul><ul><li>Add spec/tests for new emergent behavior </li></ul>
15.
User testing <ul><li>Usability testing goals: </li></ul><ul><li>Effectiveness </li></ul><ul><li>Efficiency </li></ul><ul><li>Satisfaction </li></ul>A B
-PO may have ATs coming in; create more in planning -GWT format forces ATs to be broken-down somewhat consistently -too many ATs in a story is a smell that the story is too large
Dev + PO + [Designers].
define behavior (solution specific) before code - think thru for better design write more efficient code
focusing on behavior rather than state = less brittle -difficult to predict what comes out of emergent design / expensive to try
May expose new ATs. too many==smell
Opportunity for more user testing (task testing) PO verifies ATs - proclaims DONE.
May expose opportunities for improvement (new stories). Identify features with high risk of iteration & rank them high.
automating all this
cucumber + rspec
0 likes
Be the first to like this
Views
Total views
1,501
On SlideShare
0
From Embeds
0
Number of Embeds
2
You have now unlocked unlimited access to 20M+ documents!
Unlimited Reading
Learn faster and smarter from top experts
Unlimited Downloading
Download to take your learnings offline and on the go
You also get free access to Scribd!
Instant access to millions of ebooks, audiobooks, magazines, podcasts and more.
Read and listen offline with any device.
Free access to premium services like Tuneln, Mubi and more.