Hakan Altun // Allianz Türkiye – Agile Coach
We are witnessing times when the agile working universe evolves from a somewhat unconscious and somewhat compulsory transition to a much more conscious and voluntary transition, and we are driven by its gravity force. In this process, it is not just our transition that has evolved. Our fantastic beasts that we have created for this new universe are also evolving with us.
In this adventure I'll remind you of the first "beast": Yes, I'm talking about The Rituals that doesn't leave us time to do business because of the meetings we continuously hold. We all remember that we raised this cute monster, which we approached with prejudice before we had enough experience to see the benefits of the rituals determined in the agile framework, in our hasty comments. Today, we can say that this beast has completed its evolution process and remained in our memories. I can see from your smiles that you think I'm right.
So is it over? Have we left the beasts era behind in the new universe?
Let's explore together our new fantastic beasts and where they live: We start with the huge, impregnable, ancient(!) Product Backlog beast.
Has our Product Backlog, which we took very fondly at the beginning and was like a cute puppy for us, started to grow rapidly and lose its cuteness? -At this point, I would like to put down a social responsibility note: Abandoning our lovely friends, the "house pets," as the law calls them, is a monstrous, conscientious problem that is nowhere near fantastic. It is a crime according to the Animal Protection Law.-
However, in every sprint planning, are we facing the reality that the Product Backlog ready items are too small to feed the Sprint Backlog? So, let's take a look at the symptoms that indicate that the Sprint Backlog cannot be fed healthily from the Product Backlog:
- If the Product Backlog is growing rapidly and aging at lightning speed,
- If the priorities we set so confidently no longer reflect the present,
- If we often find ourselves nurturing or improving the Product Backlog by creating new PBIs in the planning meeting,
- If we encounter many question marks about the work(s) included in the Sprint Backlog while running the sprint,
- If the work we take for the sprint does not go as we expected, it gets longer and longer, if the dependencies are on our feet,
- If the product that comes out with the Sprint target does not meet the customer's expectations, does not make our customers happy, or if we have difficulties in product delivery,
- If the retrospective actions are only a memory in the retrospective report. This is not the way to collect memories ☺
This means it's time to intervene in nutrition. Our diet, which will keep our Product Backlog in ideal dimensions, is very simple.
- We follow our diet with regular Backlog Refinement / Grooming meetings, ideally 1-2 hours for a 2-week sprint.
- We activate our diet with the stakeholder/customer catalyst. This part is important. This formula does not work if we do not include the stakeholder/customer. In other words, the right ratio of stakeholders/customers is essential as a catalyst.
- We remove PBIs that feed the Invest Criteria and Product Backlog badly from our diet.
What is the key to overcoming all these symptoms: Backlog Refinement / Grooming? How is it done? Let's talk briefly and start by remembering the definition in the HEY! Dictionary:
Backlog Refinement / Grooming: A method to keep the Product Backlog up-to-date, clean and organized. It is a fundamental process in Scrum. It is the general name given to the activities in which the squad members mature, detail and break up the work during the sprint.
Backlog Refinement / Grooming is carried out in the following sequence:
- The Product Owner takes the expectations of the customers/stakeholders,
- Under the responsibility of the Product Owner (ideally as a team), the needs are transformed into PBIs by filtering the strategy-target compatibility.
- Under the responsibility of the Product Owner (ideally by the team), priorities are determined on the axis of MVP-Needs-Market Conditions.
- Maturation is done by the team, taking into account the Invest criteria and the Definition of Ready Checklist.
- Ultimately, PBI is made ready to be handled following the team estimates.
- The Product Backlog is reviewed prior to each sprint planning; priorities can change, new requirements can be added, requirements can be canceled, size estimates can change.
Finally, whenever you feel that you are facing The Product Backlog beast, Product Backlog Anti-patterns will guide you to protect yourself from the beast.
Ufak bir not: Bu konu hakkında merak ettiklerini sormak için buraya tıklayarak bize ulaşabilirsin.
Sources:
PEM360
scrum.org
easyagile.com
Fantastic Beasts and Where to Find Them (thanks to J. K. Rowling)
* In reference to the Fantastic Beasts Series by J.K. Rowling, author of the Harry Potter Series... For those who haven't seen it, this time the series is about magical adventures in the adult world.
Comments