Purpose of Backlog Refinement
The purpose of the backlog refinement process is to make sure that the development team finds the requirements clarified enough to complete an iteration.
In other words, as per the definition of “Agile V2 Extension” of IIBA, a product backlog refinement is used to ensure enough detail and clarity for items in the backlog so that the delivery team can complete an iteration.
More about Backlog Refinement…
Backlog Refinement is a continual technique that may be done in parallel with a Workshop, to prepare the product backlog items for the development team to deliver. The technique incorporates stakeholder feedback, learnings and any refinement to the requirements on an ongoing basis. This process assists the delivery team to deliver high value and quality solutions within an iteration.
Usually, business analysis practitioners or product owners collaborate with the team members, stakeholders or customers to get their needs clarified and addressed. Once done, a set of refinement activities like
Story Elaboration
Story Decomposition
Prioritization
Sequencing will be used, that ensures the items with less/ more priorities are ordered accordingly.
Also, this refinement activity ensures that the large items are split into smaller items meeting the INVEST criteria. (Independent, Negotiable, Valuable, Estimable, Sized appropriately and Testable). The refinement process will be complete once sufficient information is available to the development team to execute.
Thus, the final outcome of carrying out the Backlog Refinement technique is, the team gets a common understanding of what is required to deliver from the Product Backlog.
Elements
Four basic criteria that will help to complete the refinement sessions are,
Backlog
Backlog Item
Refinement Meeting
Definition of Ready
Backlog
First and foremost, an ordered list of features, requirements or items is needed to start with the refinement session, without which the desired outcome cannot be achieved.
Backlog Item
An item in a backlog represents one or more requirements. Items that are in the top order should be sized and have enough details for the team to complete the next iteration. Items that are in the bottom order can be larger or less refined, which will be taken up later as the work progresses.
Item can be represented as
User Stories
Job Stories or
Wireframes
Refinement Meeting
The purpose of this meeting is to review the items that are in the top order of the backlog. The outcome of the meeting is to make sure that these items are ready for the next iteration and clarify any information if required. It is usually led by a product owner or the required customer representative.
Definition of Ready
It is a set of criteria based on which the team agrees that the item is considered as “Ready” for the next iteration.
Backlog Refinement in POA Domain
Now let’s see how the Backlog Refinement technique fits in the Product Ownership Analysis (POA) perspectives,
Applying Foundational concepts
Cultivate customer intimacy
Engage the whole team
Make an Impact
Deliver often
Learn fast
Obsess about value
Limitations:
This technique can be ineffective if,
There is a frequent change in the roadmap.
The whole team are not aligned participatory in the refinement sessions.
References: Learnings from "IIBA-CPOA"
Comentarios