Kickoff: From digital demand to a well-substantiated Business Case.
A Kickoff breaks down your digital challenge into something you can decide on, plan, and implement. In four weeks, we’ll work together to define the value you expect, who you’re solving the problem for, and what it will roughly cost. You’ll end up with a well-founded business case, a clearly defined scope, and an first prototype.
What is the Kickoff phase at Cube?
The Kickoff is our assessment phase. In a short period of time, we gather the right input in a targeted manner, identify dependencies and risks early on, and lay the foundation for a smooth continuation. Four sessions, four weeks, one shared roadmap. What sets the Kickoff apart from a typical project kickoff: we don’t get bogged down in the question of what we’re going to build, but immediately clarify why. What value do you expect to deliver, for whom, why now, and how will you demonstrate later that it works? This way, a project doesn’t start based on gut feeling, but on a solid rationale that you can share with your own organization.
Why a business case makes all the difference.
Without a business case, scope quickly turns into a wish list. Discussions about priorities are based on gut feelings, and it’s nearly impossible to determine afterward whether the project was a success. With a business case, you have a testable hypothesis: what value do you expect, what KPIs go along with it, what assumptions are you making, and what is a reasonable investment range? That makes it easier to say no to “nice-to-haves,” to make adjustments along the way, and to verify after go-live whether the solution is truly making an impact. Consider the difference between a wish list and a roadmap. A wish list just keeps growing. A roadmap forces you to make choices.
Are you ready?
The three themes of the Kickoff.
Insight and Analysis
Where do we stand now? During the initial meeting with stakeholders, we refine the goal, rationale, and urgency, and define the problem statement and success criteria in a single, clear statement. We also map out the digital landscape: processes, channels, data, and integrations, as well as bottlenecks in processes and the user experience.
Direction and values
Where do we want to go? We describe the desired functionality and map out the digital landscape using the C4 model. We then formulate the value proposition as a hypothesis: where does the value come from (such as cost savings or time savings), and under what assumptions. Finally, we formulate KPIs, including a baseline measurement and an owner.
Scope and prototype
What exactly are we going to do? We define the scope in user stories and prioritize them together with the business and users. We define Phase 1 based on where can you make the biggest impact, and how can you deliver that as quickly as possible? Next steps are outlined in a roadmap, with risks and dependencies clearly identified and an initial prototype.
The Kickoff consists of four sessions.
Session 1
Kickoff
Define the objective, rationale, urgency, and success criteria. Map out the current situation and digital landscape. Identify challenges and opportunities from the perspectives of the business, users, and technology.
Session 2
Desired situation and value.
Describe the desired outcome, outline the digital landscape using the C4 model, develop the value proposition as a hypothesis, and formulate KPIs.
Session 3
Define the scope.
Define the scope in user stories and phases, delineate Phase 1, draw up a roadmap for subsequent phases, and identify risks and dependencies.
Session 4
Presenting a business case.
The business case in a decision-ready format, an explanation of the scope and investment range, a presentation of the prototype, and a look at Design and Build.
Who's joining us from Cube.
A fixed team participates in a Kickoff: a business consultant who thoroughly understands the issue and the value, a software architect for the target architecture, a developer to assess technical feasibility, and a project manager who guides the process and the sessions. They work closely with the experts from your organization, because the knowledge about your processes lies with your people.
From Kickoff to Design and Build.
After the Kickoff, the Design and Build phase of Phase 1 begins. We develop the designs, finalize the technical landscape design, and then begin the technical implementation. Since the scope, risks, and expected value have already been defined, this phase is about building—not figuring things out. For the design work, we use design sprints, after which the implementation of your custom software begins. Growth doesn’t stop at launch. In a impact session, we periodically step back from the daily hustle and bustle to reassess the strategy and roadmap.
All phases fall within the scope of our ISO 27001 and NEN 7510 certifications. Our processes are periodically audited by an external party.
What you'll get from the Kickoff.
A well-reasoned case
What value you expect, which KPIs are associated with it, what assumptions underlie it, and what investment range makes sense. All presented in a format that allows you to make a decision internally.
A clearly defined scope
Prioritized user stories, a clearly defined Phase 1, and a roadmap with follow-up epics. Plus an overview of risks and dependencies you’ll want to know about in advance.
A physical prototype
An overview of the key screens, flows, and content. It’s not a final design, and the technical implementation isn’t ready yet, but it’s enough to test different options and gather feedback.
We help corporations operate like startups, and startups grow into corporations.
Ready to Kickoff? So are we.
Feel free to send us a message, and we'll work with you to explore the possibilities for your organization.
With courage, a level-headed approach, and a focus on quality.
Our team. Your team.
Amber Projectmanager
Bart Developer
Bernard Developer
Bob Test Engineer | Security & Privacy
Demi Officemanager
Dennis Full Stack Developer
Guus Full Stack Developer
Jarno Business Director
Jarno Back-end Developer
Jasper Developer
Jenne Digital Marketeer
Jeroen Back-end Developer
Job CEO | Executive
Joost Tech Lead | Team Pentagon
Jordy Software Architect
Justin Tech Lead | Team Hexagon
Kees Projectmanager
Kevin Developer
Laura Digital Designer
Maartje Content Marketeer
Mans Operations Manager
Marcus Projectmanager
Marleen Projectmanager | Team Lead Octagon
Mart Front-end Developer
Melanie Projectmanager | Team Lead Hexagon
Mick Tech Lead | Team Nexus
Nicky Projectmanager
Onno Business Controller
Remi Software Architect
Rogier Business Consultant
Rosan Manager People & Organization
Roy Full Stack Developer
Ruben Full Stack Developer
Ruben Digital Designer
Sander Developer
Stijn Front-end Developer
Tamara Business Consultant
Thomas Back-end Developer
Tom Tech Lead | Team Octagon
Wesley Projectmanager
Questions? No problem.
A Kickoff lasts four weeks and consists of four group sessions. Between sessions, we work through the results so that each session builds on the previous one.
It seems similar, but it’s not quite the same. This phase used to be called Sprint 0 at Cube. The name has been changed to Kickoff, and the scope has been expanded to include an explicit business case and an initial prototype.
A well-reasoned business case with KPIs and an investment range, a clearly defined scope in user stories with a roadmap, and an initial prototype of the most important screens and flows.
A business consultant, a software architect, a developer, and a project manager. They work together with the experts from your organization, because that’s where the knowledge about your processes lies.