Why?
- Refine product backlog items that are too large or poorly understood.
- The items are refined in preparation for the upcoming iterations to avoid a stop-start effect.
- During the sessions team estimates the amount of effort it will take for the story to be completed and provides other technical information.
- Large value items are split and clarified, taking in consideration any business and technical dependencies and constraints.
When?
- Weekly at the same time.
- Take time out of the iteration execution.
- 1 – 2 hours in duration.
Who?
- Team Lead – Facilitates
- Product Owner
- Project Manager
- Business Analyst
- Developer
- Tester
- Subject matter experts
- Country Stakeholders
Inputs
- Product backlog
- Previous estimations to assist with relative sizing
Outputs
- Refined product backlog and defined conditions of satisfaction (also known as acceptance criteria).
- Estimates provided for user stories.
- Epics broken down into ready user stories.
- Business and technical dependencies and constraints are included.
- The Product Owner is equipped with information to help with prioritisation decisions.
Business Analyst Involvement
- Provides estimation based on their own opinion on how long it will take to get done from an analysis perspective.
- Breaks down epics in ready user stories.
- Supports Product Owner with prioritisation.
- Assists with identifying additional stories that may need to be added.
- Clarifying any business rules that may be associated to the user story.
BA Agile Framework 