What is the Scope of a Scope?
We all know that planning is important, but often the nature and structure of planning is more daunting that the project itself. If you're like most of us; the stress of beginning the scoping and planning phase can tempt us to execute the project without any preparation, or stop us from starting the endeavour all together. The first strategy could take you anywhere, and the second; guaranteed to take you nowhere.
So, what then, is the scope of a scope? We need to recognise that project scoping can be done at many levels; not all of them daunting. In this article, we introduce the four levels of scoping Dedication Group uses on technology projects. These principles can be used for any future initiative regardless of the size and complexity faced.
Roadmap Scoping
Roadmap Scoping is a high-level strategic blueprint, and represents a top-down view of the project or endeavour. Roadmap's are drawn from executive and management stakeholder input; gathered from brainstorming and strategy discussions. The outputs of a Roadmap should be very short, presented visually, simply; and primarily used as a communication device. An effective Roadmap will set the direction and high-level goals of the project, possibly setting a target budget, but won't necessary involve a cost estimate.
Big Rocks Scoping
Big Rocks Scoping delves into the next level of detail from the Roadmap by clarifying the key moving parts to the solution. Requirements are gathered from broader range of stakeholders from executive management through to domain specialists. To gain the best results, Big Rock's should involve some level of research to identify similar and previous industry implementations, comparing internal vs vendor delivered solutions.
Most significantly; a Big Rocks Scoping exercise will (1) identify what communication is required between each of the Big Rocks, (2) determine the high-level inputs and outputs of each Big Rock and (3) the high-level model of the integrated solution. Big Rocks Scoping makes headway into providing a cost estimate (with variance - e.g. +/- 40%) which can be balanced against the strategic budget.
Implementation Scoping
Implementation Scoping is a detailed scoping exercise intended for consumption by firm stakeholders at all levels, and by skilled resources and vendors. An Implementation Scope will provide 60-80% of the detail of the final solution; with clear direction on the recommended components at all architectural levels.
Unless incredibly complex at the detailed level (e.g. an algorithmic equity trading engine); the Implementation Scope will often present the level of detail required for most projects. This scope may be documented as a specification or series of requirements briefs; with the information prepared allowing resources and vendors to provide detailed estimates with lower variance.
Contractual Scoping
Contractual Scoping provides not only what is required but also exactly how it is to be done. Contractual Scoping is a mandatory requirement for outsourcing offshore, or when using lower skilled or unqualified resources. From a time and cost perspective; it often comprises 60-100% of the actual implementation budget.
Contractual Scoping is not cost-effective for once-off projects, projects with a high rate of change, or projects which require skilled architectural and technical discretion for the solution delivery. Contractual Scoping yields the greatest benefit where a system or project has a very stable requirements base, requires significant ongoing regression testing (i.e. the same suite of testing repeated every time a change is made for a number of years), and/or where the client staff are not suitably qualified in terms of domain or technical expertise to specify, measure and control the quality outcomes of the solution.
So, how will you get started on your next endeavour?
|
|
