Refinement sessions as exploration getting to the 'how' via the 'what'
Refinements, invaluable in every phase of a project
Many clients come to rb2 requesting assistance in addressing their most complex technological and process-based issues. In order to find bespoke technological solutions for these issues, it is important that we swiftly grasp every aspect of the problems we face. Here, it’s not necessarily about what we are going to build, but about how we are going to work together. This is also the key question that is asked at a Scrum meeting. To be able to answer it, we have embraced a highly effective process. We did not invent it and it is not new, but it is extremely effective.
How can we address the technological and process-based issues?
- We begin with a few introductory conversations to get know one another better. These are also referred to as sales talks.
- We make a quick inventory of the complex issues. Because we want to know what we’re dealing with. Which complex issues require our expertise?
- We do a deep dive into the technological prerequisites and possible solutions. A probing refinement wherein our architects and analysts consider the situation and freely begin to spar back and forth on the constraints, requirements, goals and other conditions that must be met.
- If necessary, we will hold several intensive refinement sessions. This is not only how we find the ideal technological solution, but we also delve into Epics & User Stories to be able to create a good backlog outline before we start. This will give us insight into the team we need to set up as based on the required expertise and will enable us to map out a work process. By the way, steps 3 and 4 can be carried out separately, but also work well in combination:
- Next, the POC: Proof of Collaboration. In 3 to 6 sprints we validate the conceived work process while simultaneously providing the first functioning increments in the software. This is actually how we work as standard and these increments are part of an ongoing delivery process. We simply choose to employ the POC because it can identify (early) process problems. This enables you to address these and adapt at an early stage, instead of waiting to address the problem.
These steps give a project a flying start and a healthy feeding ground to then initiate a series of sprints designed by inspection, adaptation and effective software.