Competitive Advantage to get to market faster
How do we fill in technological / process related issues?
- We start with some exploratory basic conversations to get to know each other better. Also known as sales calls.
- We do a first quick inventory of the complex issue. We want to know what we are talking about. For which complex issues is our expertise required?
- We do a “deep dive” into technological preconditions and possible solutions. A rough refinement in which our architects and analysts listen to the question, provide feedback and freely discuss constraints, requirements, goals and other conditions that a solution must or can meet.
- Where necessary, we do several real refinement sessions. In this way we not only find out 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. Incidentally, steps 3 and 4 can be performed separately, but also certainly combined.
- We do a POC: Proof of Collaboration. In 3 to 6 sprints we validate the devised 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 only choose the POC because it can bring out the possible “process pain”. This way you can tackle and apply it immediately at an early stage, instead of pushing the problem forward.
These steps give a flying start to the trajectory and provide sufficient breeding ground to subsequently set in motion an endless series of sprints, shaped by inspection, adaptation and working software.