planning planification eng - DOC by 5SxAc56H

VIEWS: 0 PAGES: 6

									Planning the Project                                                           February 06, 2002
V1.3


Revision History


       Date            Version                           Description

 Jan-24, 2002          1.0       Initial version.
 Feb 03, 2002          1.1       Corrected EPA and PPA in activity table.
 Feb 06, 2002          1,2       Added test plan and IM plan.
                                 Revised the Project Log(s) output.
 Mar 15, 2002          1,3       Added “plan” to output descriptions and made deliverable
                                 description a hyperlink in output table.




                                                                                     Page 1 of 6
Planning the Project                                                             February 06, 2002
V1.3



Planning the Project

Purpose

Project planning includes development of the overall project structure, the activities and
workplan/timeline that will form the basis of the project management processes employed throughout
the project lifecycle.

Your approach to project planning will follow your Department’s procedures and guidelines. However,
if your project requires Treasury Board Approval (detailed in the next section), you will also need to
consider and address those issues outlined in the Treasury Board Project Approval submission,
approval, and review processes.

Thorough Project Planning provides the structure and procedures to ensure that adequate time and
effort is put into identifying the project scope, deliverables, resource requirements, and risks. The
Planning Process also sets out procedures that will be used within the project for tracking progress,
using tools and methodologies, communicating with the project team members, users and other
stakeholders, resolving issues and problems, acceptance, performance reporting and addressing change
requests.

Upfront planning alleviates the risk of the Project Manager having to operate "on the fly" to develop
contingency approaches when the project execution doesn't go "as expected". Project Planning also
allows for the management of expectations of all project team members and support resources by
outlining exactly what is required, how it is intended to be delivered, and the timeline that will be
followed.


Activities

For projects requiring TB approval, this project planning process is executed first to prepare the PPA at
a sufficient level of detail to permit the initial assessment. Where TB PPA approval is attained, this
planning process is executed again to produce more detailed plans and estimates required to prepare
the EPA submission.

 No.         Activity                      Detail of Activities and Remarks
  1    Requirements         Identify stakeholder needs and translate into product
       Management            requirements.
                            Based on the requirements, enumerate the project deliverables.
                            Note: This is a critical project activity and should be performed
                             rigorously. It may constitute a significant portion of the project
                             and a separate plan may be required depending on the project
                             characteristics.
  2    Identify             Identify the project’s corporate processes required to meet the
       corporate             project requirements.
       processes




                                                                                       Page 2 of 6
Planning the Project                                                         February 06, 2002
V1.3


 No.       Activity                      Detail of Activities and Remarks
  3    Decompose          Breakdown the project deliverables into manageable components
       Requirements        thereby creating the Work Breakdown Structure (WBS).
                          Review WBS with project stakeholders.
                          If requirements are divided into interdependent individual
                           projects a multi project plans will be required to cover
                           interdependencies and integration.


  4    Estimate           Estimate Product Size for each product element using your
       Product Size        organisation’s estimation methods, tools and techniques.
  5    Estimate           Estimate Project Resources using your organisation’s estimation
       Project             methods, tools and techniques.
       Resources
  6    Develop         Describe the project management processes that will be used
       Project         through the project lifecycle including the ongoing management of:
       Management
       Plan               Schedule
                          Cost budget
                          Acceptance
                          Gating
                          Start-up
                          Tracking (reporting, issue/problem management, requirement
                           management)
                          Change management
                          Reporting requirements
                          Note: For projects requiring TB approval, the project plan and
                           estimates are created in preliminary (for EPA) and detailed (for
                           PPA) versions as described in “Approving the Project”.


  7    Develop            Corporate plans include Quality, Risk, HR, Communications,
       Corporate           Performance, Configuration, Procurement, Requirements, IM/IT
       Plans               (Software development), and Validation and Verification plans.
                          The detail planning of the corporate processes may be
                           documented in the Project Management Plan or in separate
                           documents. There may be not a need to develop a Requirements
                           plan if a Requirement Specification is produced in the Planning
                           Stage.
                          Depending on the project characteristics the corporate plans
                           may be incorporated into one plan, or the overall project
                           management plan
  8    Negotiate          Review project plan(s) with project stakeholders to obtain
       commitment          commitment and approval to proceed to the next project stage.
       and approval




                                                                                    Page 3 of 6
Planning the Project                                                               February 06, 2002
V1.3



Inputs

 No.     Input             Detail of Inputs and Remarks                             Entry criteria
 1       Approved             Scope statement, that includes project                     Yes
         Scope                 justification, project scope and summary-level
         Statement, or         deliverables, in addition to product/service
         Project Charter       description
                              Charter: for details see the deliverable
                               description.
     2   Approved          For details see the deliverable description.                  Yes
         Business Case
     3   Organization’s
                           Project Planning needs to taken into account and be
         approaches and
                           tailored to existing organization’s approaches and
         constraints
                           constraints such as:

                                  Government-wide and Department specific
                                   policies and standards

                                  Pre-defined organizational processes, roles
                                   and responsibilities, tools and techniques,
                                   etc.

                                  Stakeholders knowledge, skills, availability,
                                   etc.
     4   Project
                           Extent and detail of project planning activities and
         Characteristics
                           effort is dependent on project characteristics such
                           as:

                                  Business Impact

                                  Technical Impact

                                  Budget

                                  Type of product/service (new system,
                                   replacement, enhancement, pilot)

                                  Technology (state of the art, leading edge,
                                   proven)




Outputs




                                                                                         Page 4 of 6
Planning the Project                                                             February 06, 2002
V1.3


 No.     Output            Detail of Outputs and Remarks                            Exit Criteria
  1      Approved          For details see the deliverable description.                 Yes
         Project
         Management
         Plan
  2      Approved          For details of the:                                          Yes
         Corporate
                              Quality plans: Quality Management Plan refer to
         process plan(s)
                               the deliverable description and for Test Plan
                               refer to the deliverable description.
                              Risk Management Plan refer to the deliverable
                               description.
                              Communications Plan refer to the deliverable
                               description.
                              Performance Plan refer to the deliverable
                               description
                              HR Management Plan refer to the deliverable
                               description.
                              Configuration Management Plan refer to the
                               deliverable description.
                              Procurement Management Plan refer to the
                               deliverable description.
                              Requirements Management Plan refer to the
                               deliverable description.
                              IM/IT plans: Software Development Plan refer to
                               the deliverable description and for Information
                               Management Plan refer to the deliverable
                               description.


  3      Approved          See the Requirements Specification deliverable               Yes
         Requirement       description.
         Specification
  4      Project           For details related to the:
         Tracking Log(s)
                              Project Tracking Log refer to the deliverable
         & Risk Log
                               description.
                              Risk Log refer to the deliverable description.




Policies & Standards

The following is a list of Treasury Board project policies and standards with a brief overview:

Policy




                                                                                       Page 5 of 6
Planning the Project                                                              February 06, 2002
V1.3

<<Content to be displayed based on selection from the reference database. Display references where
the reference type = policy and the subject = project management. Display the references using the
reference name (with hyper link) followed by the reference description. A listing of the initial
reference content will be provided separately. >>

Standards

<<Content to be displayed based on selection from the reference database. Display references where
the reference type = standard and the subject = project management. Display the references using the
reference name (with hyper link) followed by the reference description. A listing of the initial
reference content will be provided separately. >>


Supporting Tools and Techniques

<<Content to be displayed based on selection from the reference database. Display references where
the reference type = all identified in Navigation Specification Appendix and the subject = project
management. The section should display organized by reference type (alphabetically) and by reference
name (alphabetically within for each reference type. Display the references using the reference name
(with hyper link) followed by the reference description. A listing of the initial reference content will be
provided separately.>>




                                                                                        Page 6 of 6

								
To top