Focus Statement: Depth

Depth is how much detail of the operations must be explored to produce the appropriate deliverables. Often, it is hard to quantify depth in objective terms, so the goal many times is to give stakeholders a sense of how deep the project is attempting to go.

During Phase 2 (June 2001 - December 2002), the project team is targeting the following depth:

• Complete Analysis tasks:
  To confirm and tighten the models, then create Functional Specifications, the team is targeting 85% or more of the business requirements being flushed out and clearly specified. The team does not want to do less than 80%, and where time permits, we are pursuing more depth to minimize the analysis in the Design Phase. Yet we recognize the risk of getting stuck in analysis, so we want to avoid targeting too much depth in Phase 2.
  
  
• Transition to Design tasks:
  The Transition to Design Work does not have to meet the tightness of true "Design" work, yet to the extent that we get this correct, the less re-work will have to be done in the Design Phase. Therefore, we are pursuing 65-80% depth here.