Published on April 6, 2011

This post was previously on the Pathfinder Software site. Pathfinder Software changed its name to Orthogonal in 2016. Read more.

Inception is critical to get a project started down the right path. Get it right and you accelerate your product development. Get it wrong and you end up in analysis paralysis. Bob Moll and Glenn Bernsohn illustrate the how and why of Inception in 5 slides.

Slide Notes
  1. Inception begins with listening to each stakeholder’s project goals.  There is usually a wide disparity in the overall vision and scope at this stage.
  2. Each stakeholder provides their perspective on expected business benefits, success criteria, marketing strategy, and technology assumptions.  This information is captured visually for everyone to see.
  3. An iterative series of structured workshops enable us to drill down into more detail and gain new insights into the solution space.
  4. Inception concludes with a shared vision for the project and prepares the team for an agile delivery phase.
  5. Inception uses a set of enabling practices and follows a regular pattern which prepares the team for agile development iterations.