Many customers report to us with the request to fill in their complex issues technologically and process-wise. In order to translate these issues into technical solutions, it is important that we understand the contours of the issue before us as soon as possible. This is not only about what we are going to build, but also about how we are going to work together.
1. We start with some exploratory basic conversations to get to know each other better.
2. We make an initial quick inventory of the complex issue. We want to know what we are talking about. In this way, we determine which expertise we need to realize the solution. We do a “deep dive” into technological preconditions and possible solutions. A coarse refinement in which our architects and analysts listen to the question, provide feedback and spar freely about constraints, requirements, goals, and other conditions that a solution must or can meet.
3. Where necessary, we conduct several detailed refinement sessions. This way we not only find the best technological solution, but we also look further at Epics & User Stories to set up a first good outline of a backlog. This also gives us the insight to form a team based on the required expertise and to map out a work process. Steps 3 and 4 can also be performed separately or in combination.
4. We do a POC: Proof of Collaboration. In 3 to 6 sprints we validate the well-thought-out work process, while at the same time we deliver the first working increment(s) in software. In fact, this is what you do by default and these increments are part of an ongoing delivery process. We choose the POC because it can highlight the potential "process pain". This way you can tackle the problem at an early stage instead of pushing it forward.
These steps give a flying start to the process and sufficient breeding ground to start an endless series of sprints, designed by inspection, adaptation, and working software.