LogoLogo
Equal ExpertsContact UsPlaybooks
  • Inceptions
  • Foreword
  • Introduction
    • Why run an inception?
    • What is an Inception?
    • What’s the outcome of an Inception?
    • Inception Complete, What now?
    • Inception or Discovery?
    • Getting buy-in
    • What does good look like?
  • Run an Inception
    • Overview
    • Set-up
    • Design
      • Design inception agenda
      • How we do it
      • Inception agenda blueprint
      • Blueprint in a table
    • Plan
      • Creating a schedule
      • Example inception schedule
    • Run
    • Wrap-up
  • Cheat sheets
    • Types of inceptions
    • Contributors’ cheat sheet
    • Facilitator’s cheat sheet
    • Inception facilitation kit
    • Setting up the space
    • Playback & wrap-up
    • Principles we apply
  • Deep dives
    • Design an inception agenda
      • The Opportunity
      • The Domain
      • The Solution
      • Plan
    • Plan an inception
      • The Inception team
      • Creating the Schedule
      • Frame, Top and Tail
  • Closing thoughts
  • Get in touch
    • How to contribute
    • Licence
  • Contributions
    • The Equal Experts network
    • Special Thanks
    • The Authors
  • Our Playbooks
  • Equal Experts
Powered by GitBook
On this page
  • 1 - UNDERSTAND THE PROBLEM / OPPORTUNITY
  • 2 - UNDERSTAND CONTEXT AND DOMAIN
  • 3- IDENTIFY AND DEFINE SOLUTION OPTIONS
  • 4 - IDENTIFY DELIVERY APPROACH AND PLAN DELIVERY

Was this helpful?

  1. Run an Inception
  2. Design

Design inception agenda

PreviousDesignNextHow we do it

Last updated 5 years ago

Was this helpful?

As mentioned earlier, a good agenda has a narrative, a logical flow through which we run activities that give us insight to ultimately fulfil the goals of the inception:

1 - UNDERSTAND THE PROBLEM / OPPORTUNITY

We start with aligning on what the problem, vision and goals are:

  • Why are we doing this?

  • Where do we want to be?

2 - UNDERSTAND CONTEXT AND DOMAIN

We then analyse the current and future states covering people, process and technology:

  • Where are we now and where do we want to be?

  • What are we dealing with?

3- IDENTIFY AND DEFINE SOLUTION OPTIONS

We then head into top level to-be solution design: We define scope (usually feature / epic-level overall and story-level for the immediate next sprints) and functional / technical solution design. We agree how to prioritise, identify risks and dependencies, and define ways of working:

  • What are potential solution options?

  • What will the solution look like?

4 - IDENTIFY DELIVERY APPROACH AND PLAN DELIVERY

Finally, we make a recommendation (continue, pivot or stop).

When we continue, we define a delivery approach, team-shape, plan/roadmap and ultimately an estimate. This results in a statement of work and actionable immediate next steps:

  • How do we get there?

  • How do we deliver?

Most inceptions will follow this high level agenda: this is all that’s needed to confirm desirability, viability and feasibility of the initiative.