Have you ever started a game or puzzle with only a few explanations of the rules? It’s like being handed a Rubik’s Cube and told, “Good luck!”
I’m currently hooked on a number puzzle (Easy Brain) that involves random numbers between 1 and 9. The goal is to eliminate numbers that are either the same or add up to 10. You can select and delete numbers that are above, below, or diagonally adjacent. Sounds simple, right? Well, it’s as straightforward as assembling IKEA furniture without the instructions.
The game also offers “hints,” but there’s a catch – you have to watch an ad to access them. These hints reveal additional matches beyond those initially indicated, including matches between the end of one line of numbers and the beginning of the next line. It’s like finding out your IKEA bookshelf has secret compartments you didn’t know about.
This whole situation reminds me of the Definition of Ready when reviewing and selecting stories to be developed during an iteration. Previously, many stories developed during iterations faced questions during the demo, such as, “What about this situation?” or “Did you not consider certain additional information?” It’s like presenting your IKEA bookshelf and someone asking, “But where’s the secret compartment?”
The user story explanations provided by the Product Owner often lacked detailed information, leading to stories not being accepted at the end of an iteration due to being incomplete or incorrect. The amount of detail given to the delivery team depended entirely on the understanding and level of detail known by the Product Owner. It’s like assembling that IKEA bookshelf based on how well the Product Owner remembers the instructions.
As this issue was analyzed further, it became clear that the “analysis” phase, along with associated activities and the role of a business analyst, was often overlooked in adaptive approaches compared to predictive ones. There was a need for a more thorough understanding of the rules, potential sequences, and additional information to fully comprehend the details behind individual user stories. It’s like realizing you need a map, a compass, and a survival guide to navigate the IKEA store.
Consequently, the Definition of Ready was introduced, along with the involvement of a business analyst who could help discover, analyze, and provide additional insight, ensuring that user stories are “ready” for development. This collaboration typically occurs in adaptive approaches, often alongside the Product Owner. During this time, the backlog is also being groomed before final prioritization and presentation to the team during the Iteration Planning Meeting. It’s like having a seasoned IKEA assembler guiding you through the process.
This enhanced understanding of the stories allows the team to estimate effort more accurately and even to break down user stories based on different personas. The inclusion of the Business Analyst role in adaptive approaches, along with the Definition of Ready, has enabled teams to deliver results that are complete, correct, and better aligned with stakeholder expectations. It’s like finally assembling that IKEA bookshelf without any leftover screws.
If only I had a business analyst to provide the additional “rules” for my game, I could have achieved better results more quickly.
Please share your thoughts and experiences. Your insights are valuable and can contribute to our collective understanding, collaboration, and improvement in adaptive and business analysis practices.
#businessanalysis #definitionofready #userstories #adaptiveapproaches
