Recording Templates for Maintenance Issues

Document Sample
Recording Templates for Maintenance Issues Powered By Docstoc
					                      Template Examples Disclaimer

Unless otherwise specifically stated, the information contained herein
is made available to the public by the Department of Human
Services, Office of Information Services, Project Management Office
for use as an example of template content information and may not
reflect the realities of an actual project. The intent of the template
example is to assist an individual creating a new document using the
PMO standard template.

Neither the DHS, OIS, PMO nor any other agency or entities thereof,
assumes any legal liability or responsibility for the accuracy,
completeness, or usefulness of any information, product or process
disclosed in these examples.

Reference herein to any specific commercial product, process,
service by trade name, trademark, manufacturer, or otherwise, does
not constitute or imply its endorsement, recommendation, or favoring
by the PMO or any entities thereof.

The views and opinions of the originators expressed therein do not
necessarily state or reflect those of the DHS, OIS, PMO or any
agency or entities thereof.




C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc   Page i
Last printed 8/1/2011 11:28:00 PM
         Oregon Department of Human Services
             Office of Information Services
             OIS Intranet Communications

                       Integrated Project Plan
                      Approval Date: <mmm dd, yyyy>



                                          Planning




                   Determine work                       Determine work
                 activities, resources,                controls to ensure
                   schedule, costs                    project performance
                  (Core work Plans)                    (Facilitating Plans)
                                                                                    Project Plan

                                  Incorporate planning
                                outputs into one coherent
                                        document
                                (Integrated Project Plan)




                                          Executing




                           Purpose of the Document
The Integrated Project Plan is used to guide both project execution and project
control. It is required to ensure that the various elements of the project are
properly coordinated. It is a document or collection of documents, which
communicate the project’s plan. The integrated plan should be expected to
change over time, as more information becomes available to the project.

The amount of planning performed should be commensurate with the scope of
the project and the usefulness of the information developed.




C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc               Page ii
Last printed 8/1/2011 11:28:00 PM
                         Document Change Activity
The following is a record of the changes that have occurred on this document
from the time of its original approval
#   Change Description                                             Author      Date
1   Changed Kristen to Sponsor and added 4 new members,            Sally       4/16/02
    Bruce Childers, Linda Kilgore, Cathy Madsen and Bob
    Winfield




C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc   Page iii
Last printed 8/1/2011 11:28:00 PM
1   Background ................................................................................ 1
  1.1 Problem/Opportunity ............................................................... 1
  1.2 Context or Alignment .............................................................. 1
  1.3 Planning Inputs or References................................................ 1
2 Scope ......................................................................................... 1
  2.1 Statement ............................................................................... 1
  2.2 Objectives & Measurements ................................................... 1
  2.3 Major Deliverable Milestones .................................................. 2
  2.4 Assumptions ........................................................................... 3
  2.5 Completion Criteria ................................................................. 3
3 Work Plan .................................................................................. 3
  3.1 Work Breakdown Structure (WBS).......................................... 3
  3.2 Schedule ................................................................................ 4
  3.3 Feasibility and Recommendations .......................................... 4
  3.4 Budget Projection ................................................................... 4
4 Organization ............................................................................... 5
  4.1 Project Team Composition...................................................... 5
  4.2 Internal Roles & Responsibilities ............................................ 5
  4.3 Other Group Roles & Responsibilities ..................................... 5
5 Facilitating Controls .................................................................... 5
  5.1 Risk Management Plan........................................................... 5
  5.2 Change Management ............................................................. 5
  5.3 Project Document Standards, Approval, and Controls ............ 6
  5.4 Communication Plan & Management...................................... 6
  5.5 Status Reporting ..................................................................... 6
  5.6 Procurements & Contracts ...................................................... 7
  5.7 Quality Assurance .................................................................. 7
  5.8 Resource Tracking.................................................................. 7
  5.9 Issue & Decision Management ............................................... 7
Appendix A – WBS Dictionary ........................................................... 8




C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc                   Page iv
Last printed 8/1/2011 11:28:00 PM
1 BACKGROUND
1.1     Problem/Opportunity
Expand the Office of Information Services (OIS) Intranet to be the primary
medium for the dissemination of information within OIS. The problem is
that there are no guidelines or procedures, and no recognized ownership
for information residing on the OIS Intranet. The current OIS Intranet is not
widely used within the organization; users do not depend on it because
information is perceived to be neither regularly maintained nor current.

1.2     Context or Alignment

One of the eight OIS short-term reorganization projects has been chartered
to create an infrastructure for the DHS Intranet. This project is currently on
hold.
1.3     Planning Inputs or References

None

2 SCOPE STATEMENT
To establish guidelines and standards for communications posted on the
OIS Intranet. Recommend standards and accountability for maintenance of
any communication assessable from the site. Facilitate and ensure
implementation of the proposed expansion of the OIS Intranet to be the
primary medium for the dissemination of information within OIS.

2.1     Objectives & Measurements

The following are the objectives from the approved product description.


1. Objective-1

      Establish base guidelines for templates, processes and procedures for
      creating OIS Intranet web pages, for posting content to these pages,
      and for ensuring content is current and consistent with OIS standards.



C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc   Page 1
Last printed 8/1/2011 11:28:00 PM
      Measurement-1:
      Guidelines, templates, processes and procedures have been created,
      are easily accessible, and staff have been educated on their use and
      location.
2. Objective-2

      Purchase and install standard web-based tools and software for
      designated OIS staff.
      Measurement-2:
      Tools and software has been purchased and installed for approved OIS
      staff.
3. Objective-3

      Recommend a staffing plan for ongoing maintenance and coordination
      of the OIS Intranet.
      Measurement-3:
      Creation of a staffing plan
4. Objective-4

      Recommend a migration plan for moving existing OIS Intranet web sites
      into the new environment.
      Measurement-4:
      Creation of a migration plan.


2.2      Major Deliverable Milestones
MS# Milestone Description                                                  Planned
                                                                           Complete
MS1 Project Proposal approved by Exec Staff                                <Date>
The product description and charter written and approved by
OIS executive staff.




C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc   Page 2
Last printed 8/1/2011 11:28:00 PM
MS2 Project Plan and Schedule approved by Sponsor                          <Date>
The high level project plan, including the work breakdown
structure, and the initial project schedule are created and
agreed upon.
MS3 Intranet usage guidelines approved by Exec Staff                       <Date>
The guidelines, processes and procedures for use of the
intranet have been established and agreed upon by the OIS
Executive Staff.
MS4 Current Organization Analysis completed                                <Date>

MS5 OIS Intranet Site Creation Manual completed                            <Date>
MS6 Product Communication Plan created                                     <Date>
MS7 Modification Plan Created                                              <Date>
MS8 Operations Manual/Staffing plan created                                <Date>
MS9 Intranet successfully turned over to maintenance                       <Date>
and closed
Maintenance of the Intranet guidelines, and content will be
turned over to OIS staff, and the project will be closed.


2.3    Assumptions

None

2.4    Completion Criteria
The project will be complete once all objectives have been met, and the
maintenance of the OIS Intranet has been turned over to OIS Staff.



3 WORK PLAN
3.1    Work Breakdown Structure (WBS)

The Work Breakdown Structure (WBS) dictionary is a grouping of project
elements that organizes and defines the total scope of the project: work not
in the WBS is outside the scope of the project. This WBS dictionary is
intended to confirm a common understanding of project scope. Each
descending level of the WBS dictionary represents an increasingly detailed


C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc   Page 3
Last printed 8/1/2011 11:28:00 PM
  description of the work required to manage the project and deliver the
  customers request.

  The WBS Dictionary is located in the appendix of this document due to the
  page orientation and size.

  3.2       Schedule

               Task                       Duration                          Assigned to

  Initiate Project (charter,                                        Kristen, Cathy, Tara,
  product description)                                              Cherry, Sally, Carol

  Create Project Plan                                               Kristen, Cathy, Tara,
                                                                    Cherry, Sally, Carol

  Establish guidelines,                                             TBD
  processes, procedures

  Educate OIS Staff                                                 TBD

  Migrate current sites to                                          TBD
  new structure

  Close Project                                                     Kristen, Cathy, Tara,
                                                                    Cherry, Sally, Carol



  3.3       Feasibility and Recommendations
  This project stemmed from a need to improve communications within OIS.
  It was approved by OIS Executive Staff as a low-priority project.  No
  feasibility study is required.



  3.4       Budget Projection
  Approximate staff resource requirements for the project is as follows:
2002            Jan    Feb   Mar    Apr     May    Jun   Jul    Aug    Sep    Oct    Nov   Dec

Staff FTE       .25    .25   .5     .5      .5     .5    .5     .5     .5     .5     .5    .5


  C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc           Page 4
  Last printed 8/1/2011 11:28:00 PM
Other Costs




  4 ORGANIZATION
  4.1     Project Team Composition

  Sponsor: Kristen Duus

  Team Lead: Sally Gilbert
  Team Members: Cathy Rondema, Carol Ito, Tara Torres, Cherry Bailey,
  Bruce Childers, Linda Kilgore, Cathy Madsen and Bob Winfield


  4.2     Internal Roles & Responsibilities

  N/A
  4.3     Other Group Roles & Responsibilities

  T&S -
  NDS -

  5 FACILITATING CONTROLS
  5.1     Risk Management Plan

  N/A

  5.2     Change Management

  All changes will be logged and evaluated for impact to the scope, schedule,
  and cost of the project. The project team and sponsor will recommend
  whether to incorporate the changes or hold changes for a future release.




  C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc   Page 5
  Last printed 8/1/2011 11:28:00 PM
5.3    Project Document Standards, Approval, and Controls

Document Standards – the project will use a consistent document style and
layout for internal and external products produced. The standard word
process tool will be MS Word.

All internal work products being drafted or revised will be located in a
shared area.

A standard electronic            project    directory     will    organize      the   project
documentation.

5.4    Communication Plan & Management
The purpose of the project Communication Plan is to determine
communication needs of all people within the organization and possibly
external to the organization that will be affected by the project:; who needs
what information, when will they need it, and how it will be given to them.

The communication plan that will:

 Identify “Who” the recipients or groups of recipients of communication
  are intended to be.

 Identify “What” type of communications, in what type of media, (e.g.
  email, memo, letter, newsletter, personal conversation, status update)
  will be delivered to the various recipient groups.

 For each of the recipient group, identify who is responsible for delivering
  the communication (e.g. Communication Manager, Project Manager,
  Cabinet Members)

 For each recipient group outline “When” the schedule or dates of
  communication, e.g. weekly, monthly, a specific day…are to occur.



5.5    Status Reporting
Status Reporting will be delivered to the Exec Staff and sponsor by the
project manager on a periodic basis.



C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc        Page 6
Last printed 8/1/2011 11:28:00 PM
5.6    Procurements & Contracts
No procurement or contracting activities are anticipated for the project.


5.7    Quality Assurance

No formal Quality Assurance will be conducted on this project.

5.8    Resource Tracking

Time tracking on this project will be informal.



5.9    Issue & Decision Management

Issues raised formally or informally that impact the scope, schedule, cost or
quality of the project will be tracked by the project team on an issue –
tracking document. Issues that the Project Manager cannot resolve will go
to the Sponsor and/or or OIS Exec Staff for resolution.




C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc   Page 7
Last printed 8/1/2011 11:28:00 PM
APPENDIX A – WBS DICTIONARY
The Work Breakdown Structure (WBS) is a grouping of project elements
that organizes and defines the total scope of the project: work not in the
WBS is outside the scope of the project. This WBS dictionary is intended
to confirm a common understanding of project scope. Each descending
level of the WBS dictionary represents an increasingly detailed description
of the work required to manage the project and deliver the selected PMO
functions.

The Layout or description of the template is as follows:

First Column – Indicates the WBS grouping and numbering convention.
The groupings are a hierarchy of Phase, Activity, Task, and Milestone.

The numbering convention is standard engineering numbering.
       The Phase level is represented by a single number(i.e. 1.).

       The Activity level is represented by a 2 digit number (i.e. 1.1),
       The Task level is represented by a 3 digit number (i.e. 1.1.1).

       The Milestone is represented by a four digit number (1.1.1.1)

Second Column – Indicates the Phase, Activity, Task, or Milestone name
and a brief description that describes the work at each level. The activity
level is the level for status and change control. The task and milestone
level describe the specific work assignment to be accomplished.
Third Column – Indicates, at the task and milestone levels only, the
assigned deliverable name.

Fourth Column – Indicates, at the task level only, the anticipated “effort in
hours” to fully accomplish the defined task.

Fifth Column – Indicates, at the task and milestone levels only, the other
tasks that this task or milestone is critically dependent on.

Sixth Column – Indicates, at the task and milestone levels only, the type of
resource recommended, or most likely to have the skills to complete the
assignment.

C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc   Page 8
Last printed 8/1/2011 11:28:00 PM
                                                                                                                            Del Name & #   Eff   Critically   Resp
#               WBS Dictionary                                                                                                             Est   Depend

                                                                                                                            N/A
1. Phase        Initiate – Obtaining agreement on the business requirement and charting the project.
                                                                                                                            N/A
1.1. Activity   Develop the Business Requirement – Establish a common understanding of the
                base requirements that are to be addressed by the project.
                                                                                                                            Product                           PM
1.1.1. Task     Create the Product Description – define, scope, and give context to the product & services that the
                                                                                                                            Description
                project will be chartered to develop, deliver, and support.
                                                                                                                            Project
1.1.2. Task     Prepare and Review the Product description – depending on audience preference, summarizes the
                                                                                                                            Proposal,
                content of the product description into an executive summary and deliver it or prepare and conduct a
                                                                                                                            Document
                review of the product description. Obtain approval to charter a project that will assign initial planning
                                                                                                                            Approval
                resources to develop the project plan.
                                                                                                                            N/A
1.2. Activity   Charter the Project – Obtain the commitment and agreement between the sponsor
                and project team indicating how the project will be conducted and who needs to be
                involved.
                                                                                                                            Project                           PM
1.2.1. Task     Create the Project Charter – define the mission, authority, and level of project planning and controls
                                                                                                                            Charter
                necessary for the project, and indicate the personnel or groups expected to be involved in the project.
                Assign the project manager, sponsor, and any required resources to complete the overall project planning.
                                                                                                                            N/A                               PM
                Project Proposal Approved by OIS Executive Staff
1.2.1.1. Milestone
                                                                                                                            N/A
2. Phase        Plan – Creation and approval of the core work plan and facilitating plans that will guide
                project execution and control.
                                                                                                                            N/A
2.1. Activity   Develop the Core Work Plan (CWP) – The development of the work scope,
                supporting schedule, budget, and project organization that focuses and guides the project
                work effort.
                                                                                                                            CWP –                             PM
2.1.1. Task     Develop the Scope Statement – Develop the scope statement that indicates an agreement on work
                                                                                                                            Scope
                scope, project objectives and measurements, hi-level deliverables, assumptions, and completion criteria.
                                                                                                                            Statement


     C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc                 Page 9
     Last printed 8/1/2011 11:28:00 PM
                                                                                                                              Del Name & #   Eff   Critically   Resp
#               WBS Dictionary                                                                                                               Est   Depend

                                                                                                                              CWP –                             PM
2.1.2. Task     Develop the WBS – Define the work Activities, sequencing, effort estimates, and deliverables. Indicate the
                                                                                                                              WBS
                type of resource (people, equipment, materials, facilities) needed to complete the work activities. Review
                and obtain agreement of the WBS work activities with the sponsor, and management of other groups
                expected to support the project.
                                                                                                                              CWP –                             PM
2.1.3. Task     Develop the Project Schedule – Develop approximate cost estimates of all the types of resources. Build a
                                                                                                                              Schedule
                project schedule from the WBS and cost estimates.
                                                                                                                              and Budget
                                                                                                                              Projection
                                                                                                                              CWP –                             PM
2.1.4. Task     Organize Project & Staff Acquisition – provide an overall framework to describe the roles, responsibilities
                                                                                                                              Organization
                and membership of the Project. Obtain the staff needed for the core team and staff need from other groups
                in the organization that will be cross-committed to the project. Obtain from management commitment of all
                non-contracted personnel
                                                                                                                              N/A
2.2. Activity   Develop the Facilitating Plans for Controls (FPC) – The plans for ongoing
                work required to ensure that the project can anticipate possible problems, solve, and
                make coordinated work plan adjustments.
                                                                                                                              FPC – Chg
2.2.1. Task     Change Management – Outline a simple change management process to coordinate approved changes
                                                                                                                              Mgmt
                in the project plan.
                                                                                                                              FPC – Stds,
2.2.2. Task     Project Standards, Approval, And Document Controls – Define and setup the documentation
                                                                                                                              Apvls, Cntls
                standards, document storage locations, project notebook, document approval and promotion process, and
                securities.
                                                                                                                              FPC –
2.2.3. Task     Communication Plan and Management – Outline a plan that identifies “who” needs “what”
                                                                                                                              Comm. Plan
                communications, in “what” media, “how” often and by “whom”.
                                                                                                                              & Mgmt
                                                                                                                              FPC –
2.2.4. Task     Status Reporting – Define how status will be reported, by whom, how often, and in what formats and
                                                                                                                              Status Rptg
                media.
                                                                                                                              FPC- QA
2.2.5. Task     Quality Assurance – Identify the project’s relevant quality standards and determine how to satisfy them.

                                                                                                                              FPC – Time
2.2.6. Task     Time Tracking – Determine what level to track time at, how time will be tracked, how frequently, and
                                                                                                                              Tracking
                administer the time tracking activities.


     C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc                  Page 10
     Last printed 8/1/2011 11:28:00 PM
                                                                                                                         Del Name & #   Eff   Critically   Resp
#               WBS Dictionary                                                                                                          Est   Depend

                                                                                                                         FPC – Iss. &
2.2.7. Task     Issue and Decision Management – Determine process for raising and resolving project issues that impact
                                                                                                                         Decision
                the scope, schedule, cost or quality of the project.
                                                                                                                         Mgmt
                                                                                                                         N/A
2.3. Activity   Develop the Project Plan – Integrating the results of the other planning activities
                into a coherent document to guide the project execution and control.
                                                                                                                         Project Plan
2.3.1. Task     Plan Integration – Summarize and incorporate the outputs of the planning activities into a single
                reference document – the OIC Project Plan. The plan is the reference document for work to be performed
                by all involved in the project and must be made easily accessible to all in electronic format.
                                                                                                                         Presentation
2.3.2. Task     Plan Presentation and Review – Distribute, review and obtain approval of the project plan from the
                                                                                                                         & Document
                project directing authority(s) and managers who have staff assigned to the project.
                                                                                                                         Approval
                                                                                                                         N/A            0                  PM
                Plan
2.3.2.1. Milestone and Schedule Approved by OIS Executive Staff

3. Phase        Execute – Definition of the required work activities to define, construct,
                pilot and implement the product scope or selected system functions

3.1. Activity   Analysis of Current Processes - Review existing policies, standards,
                and processes
3.1.1. Task     Identify existing OIS Intranet sites (content, owner, difficulty to modify to new                                       3
                environment, complexity, etc)

3.1.2. Task     Identify existing staff roles & responsibilities as related to OIS Intranet                                             1


3.1.3. Task     Identify current processes, policies and guidelines (OIS / DHS / DAS)                                                   1


3.1.4. Task     Identify any existing security standards as related to OIS Intranet                                                     .5


3.1.5. Task     Identify existing standards for web tools                                                                               0




     C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc               Page 11
     Last printed 8/1/2011 11:28:00 PM
                                                                                                            Del Name & #   Eff   Critically   Resp
#               WBS Dictionary                                                                                             Est   Depend


3.1.6. Task     Identify committees (DHS / DAS) working on Intranet activities, and identify relationship                  2


                Assemble Current Organization Analysis Document                                                            2
3.1.7. Task

                Current
3.1.7.1. Milestone        Organization Analysis completed

3.2. Activity   Define Guidelines, Processes and Procedures (to be constructed)
3.2.1. Task     Establish new guidelines / policy for intranet (look and feel, design)                                     32


3.2.2. Task     Create templates for processes, procedures & communications                                                24


3.2.3. Task     Establish guidelines for review and maintenance of processes                                               24


3.2.4. Task     Establish standard naming conventions to be used                                                           24


3.2.5. Task     Develop processes and Procedures for OIS Intranet creation

3.2.6. Task     Identify and recommend content categories (kinds of items) to include on Intranet
                                                                                                            OIS Intranet   40
3.2.7. Task     Create OIS Intranet Site Creation Manual                                                    Site
                                                                                                            Creation
                                                                                                            Manual
                OIS
3.2.7.1. Milestone    Intranet Site Creation Manual completed

3.3. Activity   Define Product Communications
                Identify forum for new Communications                                                                      4
3.3.1. Task

                Identify audience (routine communications, standards, maintenance, procedures, etc.)                       4
3.3.2. Task



     C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc          Page 12
     Last printed 8/1/2011 11:28:00 PM
                                                                                                   Del Name & #   Eff   Critically   Resp
#               WBS Dictionary                                                                                    Est   Depend


                Define types of communication needed, who delivers and when (standards, develop,                  4
3.3.3. Task
                maintain, etc.)

                Establish communication processes for approval / denial, changes (standards)                      10
3.3.4. Task
                                                                                                   Product        16
3.3.5. Task     Create Product Communication Plan                                                  Communicat
                                                                                                   ions Plan
                Product
3.3.5.1. Milestone        Communication Plan completed

3.4. Activity   Define Standard Tools
                Identify tools for which there is no standard                                                     4
3.4.1. Task

                Standard
3.4.1.1. Milestone         tools identified

3.5. Activity   Define Modification Strategy
                Determine which sites should be updated to new standards                                          40
3.5.1. Task

                Estimate resources needed for modification of existing sites                                      8
3.5.2. Task

                Create a timeline for modification of existing sites                                              8
3.5.3. Task

                Recommend maintenance responsibilities going forward                                              20
3.5.4. Task

3.5.5. Task     Create step-by-step guide for modification of existing site
                                                                                                   Modification
3.5.6. Task     Create a Modification Plan                                                         Plan




     C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc          Page 13
     Last printed 8/1/2011 11:28:00 PM
                                                                                                                             Del Name & #   Eff   Critically   Resp
#               WBS Dictionary                                                                                                              Est   Depend


                Modification
3.5.6.1. Milestone             Plan Completed

3.6. Activity   Define staffing needs
                Identify roles and responsibilities and recommended staffing for ongoing maintenance                                        16
3.6.1. Task
                (skills, time commitment, etc)

                Identify recommended training / classes for standard tools                                                                  4
3.6.2. Task
                                                                                                                             Operations     24
3.6.3. Task     Create Operations Manual / Staffing Plan                                                                     Manual/Staff
                                                                                                                             ing Plan
                Operations
3.6.3.1. Milestone           Manual / Staffing Plan Created
                                                                                                                             N/A
4. Phase        Controls – Administer and manage work controls to ensure project
                performance.
                                                                                                                             N/A
4.1. Activity   Project Procedures and Controls –
                                                                                                                             FPC – Risk
4.1.1. Task     Risk Management – Manage risks by responding to identified risk indicators as they occur.
                                                                                                                             Id and Mgmt
                                                                                                                             FPC – Chg
4.1.2. Task     Change Management – Identify, plan, and conduct ongoing change control of the project. Ensure that the
                                                                                                                             Mgmt
                requirements, budget, and schedule milestones remain in line with the current approved project plan or are
                changed officially providing new requirements, budget, or schedule milestones.
                                                                                                                             FPC – Stds,
4.1.3. Task     Project Standards, Approval, And Document Controls – Conduct administration of approvals, project
                                                                                                                             Approvals, &
                library, administrative filing, and securities.
                                                                                                                             Cntls
                                                                                                                             FPC –
4.1.4. Task     Communication Management – Deliver communications or facilitate communication delivery and conduct
                                                                                                                             Comm. Plan
                ongoing administration of communications
                                                                                                                             & Mgmt




     C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc                  Page 14
     Last printed 8/1/2011 11:28:00 PM
                                                                                                                             Del Name & #   Eff   Critically   Resp
#               WBS Dictionary                                                                                                              Est   Depend

                                                                                                                             FPC –
4.1.5. Task     Status Reporting –Conduct ongoing project status reporting of work activities, budgets achievements and
                                                                                                                             Status Rptg
                issues.
                                                                                                                             FPC- QA
4.1.6. Task     Quality Assurance – monitor and identify way to eliminate causes of unsatisfactory quality performance.

                                                                                                                             FPC – Time
4.1.7. Task     Time Tracking – administer the time tracking activities and team recording of individual time
                                                                                                                             Tracking
                                                                                                                             FPC – Issue
4.1.8. Task     Issue and Decision Management – Administer the issue and decision process.
                                                                                                                             and
                                                                                                                             Decision
                                                                                                                             Mgmt
                                                                                                                             N/A
5. Phase        Close – Evaluate the projects achievement of scope, objectives, and measurements.
                Identify the maintenance plan, turn-over to maintenance, and release project resources.
                                                                                                                             N/A
5.1. Activity   Project Evaluation – Recognize the achievements and lessons learned of
                the project, and determine readiness to close the project.
                                                                                                                             Project                           PM
5.1.1. Task     Prepare a project evaluation – Review the project’s completion criteria, scope, objectives,
                                                                                                                             Evaluation &
                measurements, and lessons learned. Document and analyze the information and review with the
                                                                                                                             Lessons
                sponsors. Obtain agreement from the sponsors on readiness to proceed with project closure.
                                                                                                                             Learned
                                                                                                                             N/A
5.2. Activity   Plan for Maintenance and Turn-over – Coordinate “what” will be
                maintained and prepare supporting materials to enable smooth transition to
                maintenance. Close Project.
                                                                                                                             Maintenanc
5.2.1. Task     Coordinate Maintenance Turn-over – Identify all items or components, and their production
                                                                                                                             e Turn-over
                version/location, which will become maintenance responsibility. Ensure change request log is accurate and
                up-to-date. Ensure all issues and prior decisions are documented for turn-over. Identify maintenance staff
                and any associated budgets. Meet with maintenance lead and review this information.
                                                                                                                             Project
5.2.2. Task     Close out Project – Prepare for and celebrate project closure. Release project resources.
                                                                                                                             Celebration
                                                                                                                             Closing


     C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc                   Page 15
     Last printed 8/1/2011 11:28:00 PM
                                                                                   Del Name & #   Eff   Critically   Resp
#             WBS Dictionary                                                                      Est   Depend

                                                                                   N/A            0
                Project successfully turned-over to maintenance and closed
5.2.2.1. Milestone

5.2.3. Task




     C:\Docstoc\Working\pdf\c9c9100a-7d13-4187-99c9-55ca8b7b35dd.doc     Page 16
     Last printed 8/1/2011 11:28:00 PM

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:35
posted:8/2/2011
language:English
pages:20
Description: Recording Templates for Maintenance Issues document sample