Docstoc

Project Contract Management Plan

Document Sample
Project Contract Management Plan Powered By Docstoc
					                                              Project Management Healthcheck
   Project Name:                   Doc. Version No:     (N.X) Date: (dd/month/yyyy)
              (e.g. Draft, Final, Release #)
   Status: Status: (e.g. Draft, Final, Release #)         (Doc. Version No. and Date are used for configuration control of delivera



                                   Project Management Healthcheck

   Prepared for:

   1.0     Communication Management

           The Communication Management Function aids the project manager in effectively
           determining what kind of messages to send, who should receive them, and when to send
           them.

           Yes = Exists, documented, communicated, and effectively used in meeting project
                 requirements, objectives, and goals.
           No = Does not exist, or exists, but is not effectively used in meeting project
                 requirements, objectives, and goals because of difficult circumstances
                 (ex. cost, schedule, or quality compromises).
                                                                                                            Y
           NA = Not applicable for this project.
                                                                                                           N
           U = Unknown at this time.
                                                                                                           NA
                                                                                                           U

   1.1     The project has a committed client sponsor.

   1.2     A strong team atmosphere exists between the EDS project team and the client.

           A Communication Plan, documenting the required project communications, exists and is
   1.3
           being followed.
           A Project Announcement was made to both the client's organization and EDS to increase
   1.4
           project awareness.

   1.5     After each formal meeting, minutes are prepared and distributed to all affected parties.

   1.6     Project status reporting procedures are established and are followed.

   1.7     An Issues/Decisions process for the project is established and is being followed.

   1.8     Variance Analysis for schedule, budget, and effort is communicated on a regular basis.

           Project status review meetings are held regularly with EDS leadership, the client, and
   1.9
           suppliers.
           Project successes are documented for inclusion in a Close-Down Announcement and
   1.10
           Success Story.
                                                                                           Total Y+NA       0




Template Version Control                    Template Version 1.0 -- 10 May, 1999
119eb50c-465a-4c83-8c1b-7bf62e402ddc.xls             Saved 7/13/2011                                         Page 1 of 8
                                                Project Management Healthcheck
   Project Name:                   Doc. Version No:      (N.X) Date: (dd/month/yyyy)
              (e.g. Draft, Final, Release #)
   Status: Status: (e.g. Draft, Final, Release #)          (Doc. Version No. and Date are used for configuration control of delivera



                                   Project Management Healthcheck

   Prepared for:

           Comments:




   2.0     Risk Management

           The Risk Management Function aids the project manager in systematically assessing the
           risk factors of a project and identifying specific risk items. Risk is managed by taking
           action to accept, to transfer, or to mitigate risk. Create contingency plans to reduce
           related uncertainties and consequences. Risk management includes maximizing the
           results of positive events and minimizing the consequences of adverse events.

           Yes = Exists, documented, communicated, and effectively used in meeting project
                 requirements, objectives, and goals.
           No = Does not exist, or exists, but is not effectively used in meeting project
                 requirements, objectives, and goals because of difficult circumstances
                 (ex. cost, schedule, or quality compromises).
           NA = Not applicable for this project.                                                             Y
           U = Unknown at this time.                                                                        N
                                                                                                            NA
                                                                                                            U

   2.1     A High-Level Risk Assessment is completed and reviewed by the project team.

           Major project characteristics such as size, effort, and cost are included in the High- Level
   2.2
           Risk Assessment.

   2.3     The high-level risks are categorized into low, medium, and high risks.

   2.4     Potential risks to the project are documented using the Risk Identification List.

   2.5     The Risk Assessment/Handling Plan exists and has been reviewed by the project team.

   2.6     Project risks were evaluated for priority, probability, and impact.

   2.7     The approach for handling each accepted risk is documented.

   2.8     A risk action plan exists for each risk to be mitigated or transferred.

   2.9     Contingency plans for accepted risks exist.

   2.10    A review of the project's risks is part of the regularly scheduled project status meetings.

                                                                                               Total Y+NA    0




Template Version Control                     Template Version 1.0 -- 10 May, 1999
119eb50c-465a-4c83-8c1b-7bf62e402ddc.xls              Saved 7/13/2011                                         Page 2 of 8
                                              Project Management Healthcheck
   Project Name:                   Doc. Version No:     (N.X) Date: (dd/month/yyyy)
              (e.g. Draft, Final, Release #)
   Status: Status: (e.g. Draft, Final, Release #)         (Doc. Version No. and Date are used for configuration control of delivera



                                   Project Management Healthcheck

   Prepared for:

           Comments:




   3.0     Scope Management

            The Scope Management Function aids the project manager in identifying requirements
            and deliverables. Scope Management involves ensuring that the project completes all
            the work, and only the work, required. Its primary focus is on controlling what is and
            what is not included in the project.

            Yes = Exists, documented, communicated, and effectively used in meeting project
                  requirements, objectives, and goals.
            No = Does not exist, or exists, but is not effectively used in meeting project
                  requirements, objectives, and goals because of difficult circumstances
                  (ex. cost, schedule, or quality compromises).                                             Y
            NA = Not applicable for this project.
                                                                                                           N
            U = Unknown at this time.
                                                                                                           NA
                                                                                                           U

   3.1     A Project Summary exists for the project.

   3.2     The client participated throughout the development of the Project Scope Statement.

           The Project Approach Alternatives and Recommendation exists and has been reviewed
   3.3
           with EDS leadership and the client.
           Project requirements are clearly documented and are reviewed with the project team and
   3.4
           the client on a regular basis.
           A Work Breakdown Structure Dictionary (WBSD) exists which contains detailed
   3.5
           descriptions of the project's work.
           Change control procedures are defined and documented for managing changes to the
   3.6
           Project Plan.
           All deliverables referenced in the Statement of Work (SOW) are reflected in the Project
   3.7
           Plan.

   3.8     The baselined Project Plan has the endorsement of all project participants.

           Potential changes to the baselined Project Plan are reviewed according to the change
   3.9
           control procedures.
           Approved changes to the baselined Project Plan are communicated to the project team
   3.10
           and the client.
                                                                                           Total Y+NA       0




Template Version Control                    Template Version 1.0 -- 10 May, 1999
119eb50c-465a-4c83-8c1b-7bf62e402ddc.xls             Saved 7/13/2011                                         Page 3 of 8
                                               Project Management Healthcheck
   Project Name:                   Doc. Version No:     (N.X) Date: (dd/month/yyyy)
              (e.g. Draft, Final, Release #)
   Status: Status: (e.g. Draft, Final, Release #)         (Doc. Version No. and Date are used for configuration control of delivera



                                   Project Management Healthcheck

   Prepared for:

           Comments:




   4.0     Schedule Management

           The Schedule Management Function aids the project manager in creating a project
           schedule that encompasses all deliverables and resources required within the project
           scope. The project manager evaluates the viability of the schedule, ensures that work is
           accomplished, validates that resources are expended as planned, and updates the
           schedule as the project progresses.

           Yes = Exists, documented, communicated, and effectively used in meeting project
                 requirements, objectives, and goals.
           No = Does not exist, or exists, but is not effectively used in meeting project
                 requirements, objectives, and goals because of difficult circumstances
                 (ex. cost, schedule, or quality compromises).
           NA = Not applicable for this project.                                                            Y
           U = Unknown at this time.                                                                       N
                                                                                                           NA
                                                                                                           U
           The project's Work Breakdown Structure (WBS) includes all the work that is required to
   4.1
           complete the project requirements .
           The project Schedule is developed based on the project's Work Breakdown Structure
   4.2
           (WBS) and Resource Estimate Documentation.

   4.3     All assumptions made while developing the project schedule are documented.

           Schedule constraints driven by the client, technology, supplier, or leadership are identified
   4.4
           in the project's schedule.
           Dependencies, effort, and resources are assigned to all work elements in the project
   4.5
           schedule.
           A critical path analysis is completed for the project schedule to identify work elements on
   4.6
           the critical path.

   4.7     The time estimates and duration are tracked in the project schedule.

   4.8     A resource-constrained and resource-leveled schedule is created and maintained.

   4.9     The project schedule is optimized to conform with contract requirements.

           Project team kickoff meetings were held, and the project team understands its
   4.10
           assignments, responsibilities, and authority.

                                                                                           Total Y+NA       0




Template Version Control                    Template Version 1.0 -- 10 May, 1999
119eb50c-465a-4c83-8c1b-7bf62e402ddc.xls             Saved 7/13/2011                                         Page 4 of 8
                                               Project Management Healthcheck
   Project Name:                   Doc. Version No:      (N.X) Date: (dd/month/yyyy)
              (e.g. Draft, Final, Release #)
   Status: Status: (e.g. Draft, Final, Release #)          (Doc. Version No. and Date are used for configuration control of delivera



                                   Project Management Healthcheck

   Prepared for:

           Comments:




   5.0     Quality Management

            The Quality Function aids the project manager in defining performance requirements and
            in creating a plan to achieve these requirements. All project participants are involved to
            ensure that the plans and procedures are followed. Performance counter to the project's
            requirements, goals, and standards is analyzed, and progress is inspected at appropriate
            points to ensure compliance with the expectations of both the customer and the project
            team.

            Yes = Exists, documented, communicated, and effectively used in meeting project
                  requirements, objectives, and goals.
            No = Does not exist, or exists, but is not effectively used in meeting project
                  requirements, objectives, and goals because of difficult circumstances
                  (ex. cost, schedule, or quality compromises).
            NA = Not applicable for this project.                                                            Y
            U = Unknown at this time.                                                                       N
                                                                                                            NA
                                                                                                            U

   5.1     A project workbook exists along with procedures for updating the workbook.

   5.2     A Configuration Management Plan exists and is being followed.

   5.3     A Quality Assurance Plan exists and is being followed.

           The project team reviewed Start-Up documentation to ensure that the project is effectively
   5.4
           organized.
           Standards and procedures for technical performance, business performance, quality, and
   5.5
           metrics are established, documented, and are being followed.
           A Project Plan walk-through was conducted before baselining the Project Plan, thus
   5.6
           ensuring that it is complete and contains no inconsistencies or gaps.
           The current status of the project schedule and project costs are monitored against the
   5.7
           baselined Project Plan on a regular basis.

   5.8     Project metric data is collected and analyzed to identify project trends.

   5.9     The project workbook is current, with updates occurring as the project progresses.

   5.10    Quality reviews are conducted as defined in the project's Quality Assurance Plan.

                                                                                            Total Y+NA       0



Template Version Control                     Template Version 1.0 -- 10 May, 1999
119eb50c-465a-4c83-8c1b-7bf62e402ddc.xls              Saved 7/13/2011                                         Page 5 of 8
                                               Project Management Healthcheck
   Project Name:                   Doc. Version No:      (N.X) Date: (dd/month/yyyy)
              (e.g. Draft, Final, Release #)
   Status: Status: (e.g. Draft, Final, Release #)          (Doc. Version No. and Date are used for configuration control of delivera



                                   Project Management Healthcheck

   Prepared for:

           Comments:




   6.0     Financial and Contract Management


           The Financial and Contract Management Functions aid the project manager in
           establishing the financial infrastructure to support the estimating, forecasting, budgeting,
           and tracking of project economics. The project manager identifies the legally binding
           requirements that involve the customer, project team, and suppliers. The project
           manager monitors adherence to the requirements to ensure fairness and to reduce legal
           exposure. The project manager establishes commitments with the subcontractor on the
           work to be performed, coordinates the subcontractor's activities, and tracks and reviews
           the subcontractor's performance and results.

           Yes = Exists, documented, communicated, and effectively used in meeting project
                 requirements, objectives, and goals.
           No = Does not exist, or exists, but is not effectively used in meeting project
                 requirements, objectives, and goals because of difficult circumstances
                 (ex. cost, schedule, or quality compromises).
           NA = Not applicable for this project.                                                             Y
           U = Unknown at this time.                                                                        N
                                                                                                            NA
                                                                                                            U
           Responsibility centers are set up so actual project expenditures can be tracked and
   6.1
           compared to specific line items of the project budget.

   6.2     The project management environment supports gathering data for financial reports.

           Financial Standards and Procedures are established for the project and are being
   6.3
           followed.

   6.4     The project team has received training in the financial Standards and Procedures.

   6.5     Resource estimates and the resource plan provide the basis for the project budget.

   6.6     Actual costs are tracked and reconciled with the original estimated costs.

   6.7     All estimating and costing assumptions are documented.

           All cost categories such as travel, hardware, facilities, overhead, and training are included
   6.8
           in the project budget.
           Contractual issues that must be closed before project sign-off are identified and
   6.9
           documented.

   6.10    A plan exists for completing all financial procedures to close the project.

                                                                                            Total Y+NA       0
Template Version Control                     Template Version 1.0 -- 10 May, 1999
119eb50c-465a-4c83-8c1b-7bf62e402ddc.xls              Saved 7/13/2011                                         Page 6 of 8
                                               Project Management Healthcheck
   Project Name:                   Doc. Version No:      (N.X) Date: (dd/month/yyyy)
              (e.g. Draft, Final, Release #)
   Status: Status: (e.g. Draft, Final, Release #)          (Doc. Version No. and Date are used for configuration control of delivera



                                   Project Management Healthcheck

   Prepared for:

           Comments:




   7.0     Resource Managment

           The Resource Management Function aids the project manager in creating the strategy
           and determining the procedures for timely, cost-effective acquisition, use, and reallocation
           of resources to provide quality products and services to the customer.

           Yes = Exists, documented, communicated, and effectively used in meeting project
                 requirements, objectives, and goals.
           No = Does not exist, or exists, but is not effectively used in meeting project
                 requirements, objectives, and goals because of difficult circumstances
                 (ex. cost, schedule, or quality compromises).                                               Y
           NA = Not applicable for this project.                                                            N
           U = Unknown at this time.                                                                        NA
                                                                                                            U

   7.1     A Staffing Plan exists and is followed for staffing the project team.

           Roles and responsibilities are defined and documented. Team members were selected to
   7.2
           match these requirements.
           The size (lines of code, function points, pages of documentation, and so on) of the
   7.3
           product was estimated according to a documented process.
           Resource needs for all types of resources (hardware, software, space, and so on) are
   7.4
           documented.

   7.5     All assumptions made during the estimating process are documented.

   7.6     An Organizational Breakdown Structure exists to show lines of responsibility.

   7.7     Estimates for client resources are planned and documented.

   7.8     Project skills and experience needs are defined and documented.

           Training and developmental needs are identified, planned, and completed for all team
   7.9
           members.
           Client and EDS project team members are recognized for outstanding commitment or
   7.10
           performance.

                                                                                            Total Y+NA       0




Template Version Control                     Template Version 1.0 -- 10 May, 1999
119eb50c-465a-4c83-8c1b-7bf62e402ddc.xls              Saved 7/13/2011                                         Page 7 of 8
                                                     Project Management Healthcheck
   Project Name:                   Doc. Version No:            (N.X) Date: (dd/month/yyyy)
              (e.g. Draft, Final, Release #)
   Status: Status: (e.g. Draft, Final, Release #)                (Doc. Version No. and Date are used for configuration control of delivera



                                   Project Management Healthcheck

   Prepared for:

           Comments:




             Communication Management                                                                              0
             Risk Management                                                                                       0
             Scope Management                                                                                      0
             Schedule Management                                                                                   0
             Quality Management                                                                                    0
             Financial and Contract Management                                                                     0
             Resource Managment                                                                                    0

             AVERAGE FOR PROJECT                                                                                  0.0

                                       Intensive           Critical       Fair        Good        Excellent
                                         Care




                   Communication Management


                              Risk Management


                            Scope Management


                         Schedule Management


                            Quality Management


             Financial and Contract Management


                          Resource Managment


                     AVERAGE FOR PROJECT


                                                 0     1      2       3    4     5    6   7   8   9    10




Template Version Control                           Template Version 1.0 -- 10 May, 1999
119eb50c-465a-4c83-8c1b-7bf62e402ddc.xls                    Saved 7/13/2011                                         Page 8 of 8

				
DOCUMENT INFO
Description: Project Contract Management Plan document sample