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 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."
14. 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
15. User testing A
B
Usability testing goals:
• Effectiveness
• Efficiency
• Satisfaction
-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
