NRS SDLC Master Project Plan Documents

Supporting project plans may be required for the overall master project plan.

The mandatory deliverables are the minimum required for a project. Additional deliverables will be decided on with the project management office (PMO).

Supporting Project Plans

A Budget and Cost Management Plan sets out the activities and criteria for planning, structuring and controlling costs (Project Management Body of Knowledge Guide, PMBOK, PMBOK®).

Budget and cost monitoring and controlling is a separate task.  

Standards and Guidelines

The standard is to complete a plan to inform appropriate stakeholders.  The Budget and Cost Management plan may be an appendix of the Master Project Plan.

Templates

  • No template is available at this time.  As an interim guide, refer to the Master Project Plan template, Section 11.

Deliverable Requisite

A Budget and Cost Management Plan is mandatory for moderate and complex project levels, is optional for the simple level and maintenance categories, and is not applicable for all other categories though can always be considered optional. 

Planning and monitoring of the project budget for all projects with budget allocation.

Samples

A sample is not available at this time

Monitoring and controlling the budget and costs of the project allows for identification and reporting of actual expenditures, forecasts, and variances to the cost baseline.  

Refer to the Budget and Cost Management Plan when planning for how the budget will be managed.

Standards and Guidelines

The Project Manager must maintain a budget spreadsheet to represent the project budget and report regularly on the status of the budget in relation to the project progress. A template is provided below but may not fit all circumstances.

Templates

Deliverable Requisite

Planning and monitoring of the project budget is mandatory for all projects with a budget allocation.

Samples

Sample figures (not real data) are shown in the template above

The capacity plan will define the estimates for the anticipated data volumes of the data in the database and on the file server, and the expected increase/growth in volume over the next 5 years.

The estimates are usually based on entity/table sizes by adding up the size of each column, and estimating the number of rows to be captured for each entity/table. Specific requirements for special data formats e.g. documents, blobs, need to be planned for up-front.

The information required for capacity planning should be captured as part of the Business Process Requirements Document. Only summary information is required by Ministry staff.

Standards / Guidelines

The following summary information is required to size the database:

  • Initial Load Size (in Gigabytes - GB)
  • Annual Growth (in GB)
  • Test DB Sizing Required (in GB)
  • Prod DB Sizing Required (in GB) = A X 3 (Production, Backup and Reporting Data Base)
  • Will the system store any Large Objects (Character CLOBS and Binary BLOBS)?
  •  If so, this must be included in the estimates above.
  • Are there Data Warehouse requirements for this project?  Yes or No.

Templates

Deliverable Requisite

The Deliverable is mandatory for Moderate and Complex projects.

Samples

A sample is not currently available

The Change Management Plan documents the mechanisms and processes to manage changes to the project. 

Project changes are initiated when there is a need to change the scope, time, cost, or content of one or more previously approved project deliverables.  The Change Log and Change Request are separate documents that are used to record the changes and associated activities.

Standards and Guidelines

The standard is to complete a plan using the template provided to guide the content of the plan. The change management plan may be an appendix of the Master Project Plan.

Templates

Deliverable Requisite

The Change Management Plan is mandatory for simple, moderate, and complex project levels and optional for all other categories.  The Change Management Plan may be an appendix of the Master Project Plan.

Samples

There is no sample currently available

The Communications Plan identifies the types of messages to be communicated, responsibilities, the audience, and methods of delivery and schedule for each communication.

The Communications Plan should provide:

  • How various types of information will be gathered and from whom.
  • A structure that shows how and to whom the information will flow. This structure must be compatible with reporting relationships on the project organization chart.
  • A description of each kind of information to be produced and distributed.
  • Schedules showing when each type of communication will be produced, with procedures for obtaining feedback.
  • A method for updating the communications plan.

Standards and Guidelines

The standard is to complete a plan using the template provided to guide the content of the plan.  The Communications Plan may be an appendix of the Master Project Plan.

Templates

Deliverable Requisite

A communications plan is mandatory for moderate and complex project levels, is optional for simple and maintenance levels, and is not applicable for all other categories though can always be considered optional.  The communications plan may be an appendix of the Master Project Plan.

Samples

There is no sample currently available

The Implementation Plan provides a schedule of activities to be accomplished during production migration of a new system or major enhancement.

Implementation has occurred when the deliverables are accepted by the client and the system is put into use.  The plan consists of a overview document and an excel workbook that contains the tasks required with the beginning and end dates of each task, task dependencies, who is responsible and resources required.

The Implementation Plan is initially created during the Requirements phase.  It is reviewed and updated as necessary during the Design and Build phases. It is executed in the Implementation Phase.

Standards / Guidelines

The standard is to use the templates provided below.

Templates

Deliverable Requisite

An Implementation plan is mandatory for all project complexity levels.

Samples

There is no sample currently available

The issue plan identifies the approach to managing issues, where issue documentation resides, the role responsible for maintaining the documentation and the frequency of review of issues. 

The issue note and issue log are separate documents that are used to record the issues and associated activities.

Standards and Guidelines

The standard is to complete a plan using the template provided to guide the content of the plan.  The issue plan may be an appendix of the master project plan.

Templates

Deliverable Requisite

An issue plan is mandatory for moderate and complex project levels, is optional for simple, and is not applicable for all other categories though can always be considered optional.  The issue plan may be an appendix of the master project plan.

Samples

A sample is not available at this time.

The Release Plan defines the release(s) of applications, software, or hardware and describes the approach to development and the release(s).

The plan defines the release and release units, explains risks and business impacts of the release, lists necessary resources, and specifies estimated timeframes.  The Release Plan is a deliverable in the design phase of the NRS Systems Development Life Cycle (SDLC) for new development and maintenance releases but may be started in an earlier phase.

Standards / Guidelines

  • The standard is to complete the Release Plan using the template provided.

Templates

  • No template currently available

Deliverable Requisite

The Deliverable is mandatory for all projects.

Samples

  • Samples are not available at this time.

The Retirement/Archive plan identifies the retention period for the new application datasets and the archival plan of the application data.

This document will identify any datasets to be retired or archived as a result of the project being implemented.  Retention schedules must be identified (prior) for these datasets and these will determine the possible timing for the datasets being retired or archived.

Standards/Guidelines

Follow the application retirement process.

Refer to the Government Records Service Process for Disposing or Archiving Application Data process.

Refer to the Application Retirement Process Folder Readme Sample.

Templates

Deliverable Requisite

An assessment is mandatory for all project complexity levels.

Samples

There is no sample currently available

Risk management is conducted to increase the probability and impact of positive events and decrease the probability and impact of negative events in the project (para-phrased from Project Management Body of Knowledge Guide (PMBOK®) Fourth Edition P414). 

The Risk Management Plan defines how the project will perform activities to manage project risks.  A risk assessment should be completed early on in the project and monitored/revised as needed throughout the project.  The Risk Register is a separate document that is used to record the risks and associated activities.

Standards and Guidelines

The standard is to complete a plan using the template provided to guide the content of the plan.  The Risk Management Plan may be an appendix of the Master Project Plan.

Core Policy references risk management and can be found in Core Manual, s, 14 – Risk and Core Manual ,s, 15 - Security.

Templates

Deliverable Requisite

A Risk Management Plan is mandatory for moderate and complex project levels, is optional for the simple level and maintenance category, and is not applicable for all other categories though can always be considered optional. The Risk Management Plan may be an appendix of the Master Project Plan.

Samples

A sample is not available at this time

The Training Needs Assessment identifies gaps in the knowledge, skills or abilities of impacted end-users compared to levels required to support and sustain the changes being implemented as a result of the new system.

The Training Needs Assessment is used to identify end-user groups, required knowledge, skills and abilities (KSAs), and objectives/priorities in order to develop appropriate training activities.

Standards / Guidelines

There is no standard currently available.

Templates

Deliverable Requisite

A Training Needs Assessment is mandatory for all project complexity levels.

Samples

There is no sample currently available.

A new application system will require that staff and potentially external users to be trained in how it works.

At the Design Phase the training team must draft a formal training plan.  This will be closely linked to the Implementation Plan for the systems project.  At this phase an outline of the training plan can be included with the overall project communications to stakeholders.  Consider ongoing training requirements and methods to achieve.

Standards / Guidelines

Templates

Deliverable Requisite

A training Plan is required for all project complexities.

Samples

There are no samples available