Software Implementation - Paths

The combination of optional processes and alternative processes that is chosen and agreed for any implementation segment is known as a Path.  A number of standard paths can be developed.  These are described in Path Templates, i.e. a list of all processes normally conducted within a segment when a given approach is called for.

Path Templates do not define all possible paths.  On the contrary, Path Templates only define example paths.  An implementation can function with any path, provided that it contains a valid and logical combination of related processes.

The actual combination of processes for any given project is defined in the project’s Path Plan. The Path Plan gives a high-level “management plan” view of the overall project.  It would show the processes and key high-level deliverables along with an initial summary view of resourcing and timescale requirements.  This Path Plan is agreed before or during the Project Launch segment.   

The Project Launch segment explains the basic concepts.  It shows the main choices for the Requirements, Selection and Delivery segments along with inter-segment, management paths.  For each of the work segments, the main illustrated Path Templates allow for a full way of doing things, a faster shorter way, and by-passes situations where the normal work is not required.

Note that the diagram above only illustrates the concept of paths.  One important point to note is that parallel concepts can also apply to the paths and segments.  It is feasible for the paths or segments to overlap, for example, some tasks in a preceding segment may be being finalised while the QA review is taking place, and while the planning and launch for the next segment is being started, and, possibly, where some initial tasks of the following segment are already in progress.

There are other defined path templates dealing with specific cases which have not been shown in the diagram for the sake of clarity and simplicity.  Also note that “Plan/Launch” is an abbreviation for the two templates “Review Path Plan” and “Segment Launch”.

Processes may be mandatory, normal or optional.  Alternative processes may sometimes be defined for the same aspect of a project where there are differing needs and market conditions to address.  In many cases there will be alternative processes depending on the circumstances of the customer or the scope of the business requirements.  In this way we can be left open so that many different valid paths can be defined through the processes.

Where a new need is identified, new or revised processes can be added into this framework without disturbing the overall design of the project.  This allows for an extensible simply and rapidly methodology to meet all needs in the ever-changing marketplace.

Examples of standard Path Templates are defined as follows:

Project Launch

Segment Launch - Requirements Segment

• Requirements - Full
• Requirements - Catalogue
• Requirements - Validate
• Quality Audit - Requirements
• Review Path Plan (Post Requirements)

Segment Launch - Selection Segment

• Selection - Full
• Selection - Short Form
• Requirements/Selection - Fast-Track Selection
• Selection - Confirm
• Quality Audit - Selection
• Review Path Plan (Post Selection)

  Segment Launch - Delivery Segment

• Delivery - Integrated Design Development and Implementation
• Delivery - Brief Delivery
• Delivery - Implementation Only
• Delivery - Quality Audit
• Terminate project