If we don't get the user needs right, it doesn't matter how well we
execute the rest of the product because the purpose of a
software development project is to build a product that provides
value to a particular set of customers.
We're here to refine the backlog, our list of items that need to be
completed in order to keep our customers happy and continue to
deliver them a product that they find valuable.
This is a good platform to discuss and clarify stories in the
product backlog and update our priorities.
We are all a team collectively responsible for our product
Responsible for our product's vision
Responsible for return on investment
Has the final say
Can't do it all alone, needs the team's help.
What are your current priorities?
A feature is a set of related requirements that allows the user to satisfy a business
objective or need. Features are articulated in the backlog through user stories that
tell who, what, and why a feature would be useful.
As a [role] I want [something] so that [benefit].
If a story doesn't meet the INVEST criteria, it is probably an epic that needs to be
broken down into user stories.
We need to estimate the size of each story (how long it will take) and also decide
what is more important for our customers that we get done first.
Acceptance Criteria can be further added to the story to ensure developers build
what the customer wants.
Given [some precondition] when [I do some action] then [I expect some result].