SCHEDULE MANAGEMENT PLAN
ELECTRONIC BALLAST FOR 200W INDUCTION
LAMP
Date of Issue: < 07/09/2010 >
Document Revision #: < 1.0 >
Project Manager: < Dr. Farrukh Kamran >
docsity.com
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Schedule Management Plan Example-Engineering Project Management-Handout, Exercises of Software Project Management
This handout is to explain concepts of Engineering Project Management course with help of examples. It was distributed by Dr. Maaz Khan at Shree Ram Swarup College of Engineering and Management. It includes: Schedule, Management, Plan, Electronic, Ballast, Wbs, Dictionary, Requirements, Definition, Approval, Implementation
Typology: Exercises
2011/2012
1 / 3
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Schedule Management Plan Example-Engineering Project Management-Handout and more Exercises Software Project Management in PDF only on Docsity!
SCHEDULE MANAGEMENT PLAN
ELECTRONIC BALLAST FOR 200W INDUCTION
LAMP
Date of Issue: < 07/09/2010 >
Document Revision #: < 1.0 >
Project Manager: < Dr. Farrukh Kamran >
I NTRODUCTION
The project schedule is the roadmap for how the project will be executed. Schedules are an important part of any project as they provide the project team, sponsor, and stakeholders a picture of the project’s status at any given time. The purpose of the schedule management plan is to define the approach the project team will use in creating the project schedule. This plan also includes how the team will monitor the project schedule and manage changes after the baseline schedule has been approved. This includes identifying, analyzing, documenting, prioritizing, approving or rejecting, and publishing all schedule-related changes.
SCHEDULE MANAGEMENT APPROACH
Project schedules will be created using MS Project 2007 starting with the deliverables identified in the project’s Work Breakdown Structure (WBS). Activity definition will identify the specific work packages which must be performed to complete each deliverable. Activity sequencing will be used to determine the order of work packages and assign relationships between project activities. Activity duration estimating will be used to calculate the number of work periods required to complete work packages. Resource estimating will be used to assign resources to work packages in order to complete schedule development.
Once a preliminary schedule has been developed, it will be reviewed by the project team and any resources tentatively assigned to project tasks. The project team and resources must agree to the proposed work package assignments, durations, and schedule. Once this is achieved the project sponsor will review and approve the schedule and it will then be baselined.
The following will be designates as milestones for the project schedule: Completion of scope statement and WBS/WBS Dictionary Baselined project schedule Approval of final project budget Project kick-off Approval of roles and responsibilities Requirements definition approval Completion of data mapping/inventory Project implementation Acceptance of final deliverables
Roles and responsibilities for schedule development are as follows:
The project manager will be responsible for facilitating work package definition, sequencing, and estimating duration and resources with the project team. The project manager will also create the project schedule using MS Project 2007 and validate the schedule with the project team, stakeholders, and the project sponsor. The project