Ester Derby wrote that 60% of a project odds depends on its preparation. This preparation is usually called an Inception.
A.Buzzacarro, former CTO of France Television digital, put it this way : "Any time we cut corners on Inception, we paid 10 times the price later. Projects preparation is where the attention of a CTO should be, not into steering comitees."

Working with pairs consultants, I have been facilitating inceptions throughout the last 10 years of my career. The process I had learn originally was basic. Over time it has been improved by UX designers, software architects, coders, facilitators, agile coachs, delivery managers.
Different versions of this process were run through dozens of Agile Inceptions: projects big and small, in a hurry or a soft pace, on domains varying from banking to media. As to help teams starting their project on rails, we have been experimenting, adjusting, simplifying or enriching, again and again, rince and repeat.
Today it has become a stable process with consistent result to help team launch their project on the right rails :
- a sequence of 8 mandatory questions
- a few guidelines to understand which style so workshops is effective in your context

My ambition is to give you one big takeaway in one unique session : every steps and every tools used for Inception. We will cover the overall process with drawing and pictures, then just enough details to run the workshops by yourself (with homework).


Outline/Structure of the Experience Report

  • big picture : 40 seconds
  • overall process : 5 minutes
  • details : 20 minutes
  • Q/A (or more details)

Learning Outcome

  • the end to end process of an inception 
  • when to do it perfectly and when to do it quick and dirty
  • a list of workshops : for each step, the ideal workshop, and the shortcut versiom  

Target Audience

Anyone leading or facilitating a project inception : product owner, scrum master, project manager, ux, agile coach

schedule Submitted 4 years ago