 |
|
Requirements Planning Structure |
|
Indented
bulleted lists can be collapsed or expanded by clicking on the
paragraph headings (not
all browsers)
Right clicking a hyperlink provides
the option to open a new window which can then be set to full
screen viewing
|
|
-
Requirements
/ planning structure - used to meet single, multiple,
simple or complex requirements and to plan. Planning enables
us to structure requirements to reduce complexity, understand dependencies, consider
options / alternatives and determine the correct
solutions
-
A requirement
that has been sanctioned / approved is placed at the correct level in the
five level Requirements / Planning
Structure. The level determines the type of actions to be taken
and preceding and succeeding dependencies
-
Although
a
single level can be used on its own to meet simple requirements
dependencies are taken into account to ensure time, money and effort are
not wasted on incorrect or incomplete requirements
-
A
complex requirement can be simplified and risks reduced by breaking the
requirement down into its component types, placing them at the correct
levels and understanding the dependencies between them
-
Yes
/ no options or alternatives are considered for each level and subjected
to the decision process for comparison, selection and the best course
of action
-
An
approved requirement at one level becomes the starting point for the
next lower level requirement. For example the correct objective (s) must be
established before strategies are considered and strategies must be
correct before tactics and resources are considered
Extensive and complex requirements like
strategic planning can be met by repeating the plan for different divisions / levels of the organization.
The output from a higher level plan becomes the starting point for the
next lower level
Each
level of the structure must be correct before spending, and possibly
wasting, ever increasing amounts of time, money and effort on lower
levels
|