Why?
- Plan items the team will aim to convert to working product during the iteration.
- The Product Owner describes which items are the highest priority features.
- The team will select the amount of work they can implement by answering the following questions:
- “What can we deliver by the end of this iteration?” (The team asks questions to understand the requirements to enable them to forecast what they can deliver during the iteration).
- “How will we do the work?”
When?
- At beginning of iteration.
- One hour per week of iteration length for each part.
Who?
- Team Lead – Facilitates
- Product Owner
- Project Manager
- Business Analyst
- Developer
- Tester
- Subject matter experts
- Country Stakeholders
Inputs:
- Refined product backlog.
- Improvements from previous Iteration Retrospective.
- Iteration Goal (if already known).
Outputs:
- Iteration goal
- Iteration product backlog
- Broken done tasks per story to outline what needs to be done.
- Blockers / external dependencies which need to be dealt with.
Business Analyst Involvement:
Provide more information for user stories from analysis perspective to support feature team to take on the right user stories.
BA Agile Framework 