Friday, May 29, 2009

Step 01: Stage Kick Off

Description

Objective

 

To

 

            -  start the project work on the stage,

 

in a way that

 

            -  gains agreement and commitment to the stage plan from the project team,

 

            -  sets up the project administration,

 

            -  initiates the on-going day by day execution of stage activities,

 

            -  initiates the stage control procedures,

 

so that

 

            -  the project team members can begin to work as a team for the success of the stage and project.

 

Overview

 

Once the Project Board has authorized the project to proceed with the stage, it is important to make a successful start to the work.  Brief the project team on achievements to date, the more detailed plans for the current stage, and their place within the context of the overall project. There may be new team members who need to be briefed on all aspects of the project and existing team members may need to be brought up to date with any changes to the overall project plan.

 

Electronic and hardcopy file structures are set up to consistently maintain and administer project management and development products.

 

All control and documentation procedures for the stage should be established and the team should understand what these are for, how they are used, and what their individual responsibilities are.

 

It is possible that the stage schedule is not at a sufficient level of detail to manage and control the project on a day to day basis.  This level of control may be achieved using a commitment calendar, which details each person's work on the project for a rolling four week window.  This is initiated at stage start up and updated regularly as the project progresses.

Task .010          Setup Stage Administration

The Process Manager will assign each new project a project nmemonic or acronym which is to be used in all naming conventions.

 

Set up the project administration.  Paperbased and electronic versions will be maintained concurrently.  Establish the Directories and create a master index.

 

Setup a hardcopy Project Binder with the following sections and contents:

 

Plans

 

            -  Project Initiation Report,

 

            -  Baselined Stage Schedule,

 

            -  Progress Control Tracking Schedules,

 

            -  Summary Cost Worksheet.

 

Change

 

            -  Change Control Requests,

 

            -  Change Control Log.

 

Issues

 

            -  Issue Log

 

Quality

 

            -  Quality Review Schedule,

 

            -  Quality Review Agendas,

 

            -  Quality Review Exception Item Lists.

 

Status

 

            -  Status Reports

 

            -  Flash Reports

 

            -  Stage End Report(s)

 

            -  Stage End Approval Report(s)

 

Create the following Server based PMC directory structure for the project:

 

Plans

 

            -  Project Initiation Report,

 

            -  Baselined Stage Schedule,

 

            -  Progress Control Tracking Gantts,

 

            -  Summary Cost Worksheet.

 

Change

 

            -  Change Control Requests,

 

            -  Change Control Log.

 

Issues

 

            -  Issue Log

 

Status

 

            -  Status Reports

 

            -  Flash Reports

 

            -  Stage End Report(s)

 

            -  Stage End Approval Report(s)

Task .020          Establish Checkpoint Cycle

Establish the project checkpoint cycle.

 

It is recommended that the checkpoint cycle be of one week duration.  Determine the start and end day.

 

For example, Checkpoint Cycle of Thursday thru Wednesday.  Progress will be captured for the period 8.00am Thursday through to 5.00pm the following Wednesday.  The plans will be updated for the Status Meeting on Thursday.

Task .030          Initiate Stage Version Control

Create one or more Development Product Directories, as appropriate, to file either electronically or on paper where the stage development products will be located.

 

Update the Process Engineer Project File with the Product path for each development product.  This will support document management and access.

 

Products which have a Quality Review status of "QR Complete" or "QR Qualified & Complete"  will be require a baseline version number.  If a product is made up of multiple components, establish a version number for each component.

 

Identify the team member who will exercise configuration control for the development products.  This role will be responsible for controlling the revision of versioned products.

Task .040          Acquire Stage Resources

Acquire the resources required to carry out the stage.

Task .050          Brief The Team

Brief both the project team and the key resources on the expectations for the stage.

 

Walkthrough:

 

            -  stage objective,

 

            -  planned activities,

 

            -  products,

 

            -  organization, roles and responsiblities,

 

            -  metrics,

 

            -  project controls.

Task .060          Initiate Stage Control Procedures

Initiate the control procedures:

 

            -  Checkpoint Cycle,

 

            -  Progress Controls,

 

            -  Status Reporting,

 

            -  Change Control Log,

 

            -  Issue Log,

No comments:

 
hit counter
unique hit counter