SCHEDULE MANAGEMENT PLAN

(1)

SCHEDULE MANAGEMENT PLAN

GS – E-COMMERCE WEBSITE

December 7, 2015

GENERAL SUPPLIES 41 Spring Hill Pkwy SE

Smyrna, GA 30080

(2)

2 Prepared By

Document Owners Organizational Risks Gayathri Gangadharan QA Tester Prashaanth Jagannathan Developer Josephine Nord Architect Chukwuma Obiekwe Support Specialist

Rob Wade Business Analyst

Schedule Management Plan Version Control

Version Date Author Change Description

A 12/7/2015 Gayathri Gangadharan Creation of Schedule Management Plan.

(3)

3

The purpose of the schedule management plan is to establish the foundation of proper development and control of the project schedule. This document will define the approach used by the Star Consulting team to develop the project roadmap. When followed properly, the schedule management plan provides any involved party (the project team, the client team, the project sponsor, or any other stakeholders) with the project’s estimated status at any given point in time.

This plan also covers the processes used to monitor the project schedule and manage any changes to the baseline that occur along the project’s timeline.

SCHEDULEMANAGEMENTAPPROACH

The project schedule will be created in MS Project using the activities, milestones and deliverables identified in Work Breakdown Structure (WBS). Each activity will be further defined by the start and end dates, and the resources required to complete each deliverable. The details for each activity can be found in the Activity Attributes documentation. In order to determine the sequence of activities, activity sequencing was used to assigned relationships between the activities as identified on the MS Project file. Activity duration estimates and activity resource requirements will be determined using a variety of techniques such as three-point estimating and project management software such as MS Project.

Once the baseline has been developed, the project team will review the plan for any discrepancies. In order for the project to ahead, the project team and any required resources must agree to completing the proposed plan. This includes all details related to the activity durations and project schedule. After approval from the project team is obtained, the plan will be presented to the project sponsor for review and approval. Once approved, the schedule will be baselined in the MS Project file.

Milestones

The following will be designates as milestones for the project schedule:

• Sign off project schedule

• Sign off business case

• Sign off planning

• Sign off design

• Sign off development

• Sign off testing

• Sign off launch (website implementation)

• Acceptance of final deliverables

• Project closure Roles and Responsibilities

The project manager will be responsible for completing the work package definition, sequencing and duration/requirement estimates with the project team. This individual will also be

(5)

5 responsible for creating the MS Project file and obtaining approval of the schedule from the project team and later the project sponsor. Once the schedule is approved, the project management will be responsible for setting the schedule baseline.

During this phase, the project team is responsible for assisting the project manager in the sequencing and duration/requirement estimates. After initial completion of the schedule, the project team will need to approve the document before it is sent to the project sponsor for review and approval. Upon approval from the project sponsor, the project team is responsible for performing the activities as proposed by the project schedule.

The project sponsor is responsible for providing the final approval on the proposed schedule before it is baselined.

The project stakeholders will be allowed to participate in initial review of the proposed schedule and help in obtaining approval from the project sponsor.

SCHEDULECONTROL

The project schedule will be reviewed and updated as necessary on a weekly basis by the project manager. The actual start, actual finish and completion percentages will be provided by the task owners, who are individuals in the project team. These changes will be made during a weekly catch up meeting. The project manager is responsible for conducting these weekly meetings, determining the impact of schedule variances, overseeing schedule change requests and reporting schedule status to the project sponsor (based on the Communication Plan).

The project team is responsible for participating in the weekly meetings. They will be expected to communicate any schedule changes that have occurred or are forecasted.

The project sponsor will be responsible for schedule status awareness and approve/reject any schedule change requests submitted by the project manager.

SCHEDULECHANGESANDTHRESHOLD

In the event that any schedule changes need to occur, the project manager and project team will meet to review the change. The topic of this discussion will include:

• Is this change necessary?

• How will this change impact the overall schedule?

• What tasks will be affected by this change? How?

• What will be the schedule variance following this change?

• Alternative resolution activities that may mitigate the effects of this change.

If the impact of the change is significant and changes the project schedule considerably, the change will then be submitted to the project sponsor by the project sponsor. To consider a change significant, the following conditions must be true:

• The change will increase or decrease the duration of a work package by 15% or more.

• The change will increase or decrease the overall baseline schedule by 15% or more.

(6)

6 Any changes that do not fit these criteria can be approved by the project manager and need not be submitted to the project sponsor.

If a change request has been reviewed and approved by the project sponsor, the project manager is responsible for making the change in the project schedule and adjusting for the change accordingly. If a change request has been rejected by the project sponsor, then the project manager and the project team is responsible for determining an alternative solution that mitigates the impact of not implementing the change. Any change to the project schedule must be documented and communicated to all entities involved with the project (project team, project sponsor, and stakeholders). The responsibility of appropriate documentation and communication falls on the project manager.

SCOPECHANGE

In the case of any changes to the project scope approved by the project sponsor, the project team will be required to reevaluate the impact on the current schedule. If the project manager and team decide the impact is significant, then the schedule may need to be re-baselined according to the scope changes. This request for a new baseline will need to be approved by the project team and the project sponsor before the schedule is baselined again.

SPONSORACCEPTANCE

12/07/2015

____________________________________________________ _______________________

Project Sponsor Date

SCHEDULE MANAGEMENT PLAN