In project management, a schedule is a listing of a project's milestones, activities, and deliverables. Usually dependencies and resources are defined for each task, then start and finish dates are estimated from the resource allocation, budget, task duration, and scheduled events. A schedule is commonly used in the project planning and project portfolio management parts of project management. Elements on a schedule may be closely related to the work breakdown structure (WBS) terminal elements, the Statement of work, or a Contract Data Requirements List.
Overview
editIn many industries, such as engineering and construction, the development and maintenance of the project schedule is the responsibility of a full-time scheduler or team of schedulers, depending on the size and the scope of the project. The techniques of scheduling are well developed[1] but inconsistently applied throughout industry. Standardization and promotion of scheduling best practices are being pursued by the Association for the Advancement of Cost Engineering (AACE), the Project Management Institute (PMI),[2] and the US Government for acquisition[3] and accounting[4] purposes.
Project management is not limited to industry; the average person can use it to organize their own life. Some examples are:
- Homeowner renovation project
- Keeping track of all the family activities
- Coaching a team
- Planning a vacation
- Planning a wedding
Some project management software programs provide templates, lists, and example schedules to help their users with creating their schedule.
Methods
editThe project schedule is a calendar that links the tasks to be done with the resources that will do them. It is the core of the project plan used to show the organization how the work will be done, commit people to the project, determine resource needs, and used as a kind of checklist to make sure that every task necessary is performed. Before a project schedule can be created, the schedule maker should have a work breakdown structure (WBS), an effort estimate for each task, and a resource list with availability for each resource. If these components for the schedule are not available, they can be created with a consensus-driven estimation method like Wideband Delphi.[5]
To develop a project schedule, the following needs to be completed:[6]
- Project scope
- Sequence of activities
- Tasks grouped into 5 project phases (conception, definition & planning, launch, performance, close)
- Task dependencies map
- Critical path analysis
- Project milestones
In order for a project schedule to be healthy, the following criteria must be met:[7]
- The schedule must be constantly updated (weekly works best).
- The EAC (Estimation at Completion) value must be equal to the baseline value.
- The remaining effort must be appropriately distributed among team members (taking vacations into consideration).
The schedule structure may closely follow and include citations to the index of work breakdown structure or deliverables, using decomposition or templates to describe the activities needed to produce the deliverables defined in the WBS.[8]
A schedule may be assessed for the quality of the schedule development and the quality of the schedule management.[9][10][11]
See also
editReferences
edit- ^ A Brief History of Scheduling (PDF)
- ^ Project Management Institute (2003). A Guide to The Project Management Body of Knowledge (3rd ed.). Project Management Institute. ISBN 1-930699-45-X.
- ^ "Scheduling Guide for Program Managers" (PDF). AcqNotes.com. Defense Systems Management College Press. 2001. Retrieved 14 Nov 2017.
- ^ "GAO Schedule Assessment Guide, Best Practices for Project Schedules". General Accounting Office. General Accounting Office. December 2015. Retrieved 3 Jun 2016.
- ^ Stallman, Greene, Applied Software Project Management Archived 2013-06-24 at the Wayback Machine O'Reilly press, Nov 2005
- ^ "Beginner's Guide to Project Scheduling". Genius Project. Retrieved 15 May 2017.
- ^ Cutting, Thomas, Cultivating a Healthy Project Schedule, PM Hut (Last accessed 8 November 2009).
- ^ "Guidelines for Successful Acquisition and Management of Software-Intensive Systems, 7.2.1 Activity Definition". USAF Software Technology Support Center. Archived from the original on 2012-12-30. Retrieved 15 Jan 2016.
- ^ "Program Schedule Quality 101". 16 Oct 2014. Retrieved 24 May 2016.
- ^ "DCMA-EA PAM 200.1 Program Analysis Pamphlet" (PDF). Oct 2012. Archived from the original (PDF) on 1 November 2015. Retrieved 24 May 2016.
- ^ "Planning & Scheduling Excellence Guide (PASEG)" (PDF). National Defense Industrial Association (NDIA). Mar 2016. Retrieved 17 Nov 2017.
Further reading
edit- Chamoun, Yamal (2006). Professional Project Management, The Guide (1st ed.). Monterrey, NL MEXICO: McGraw Hill. ISBN 970-10-5922-0.
- Heerkens, Gary (2001). Project Management (The Briefcase Book Series). McGraw-Hill. ISBN 0-07-137952-5.
- Hendrickson, Chris (1989). Project Management for Construction, chap 10 Fundamental Scheduling Procedures. Prentice-Hall. ISBN 978-0137312665.
- Kerzner, Harold (2003). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (8th ed.). Wiley. ISBN 0-471-22577-0.
- Klastorin, Ted (2003). Project Management: Tools and Trade-offs (3rd ed.). Wiley. ISBN 978-0-471-41384-4.
- Lewis, James (2002). Fundamentals of Project Management (2nd ed.). American Management Association. ISBN 0-8144-7132-3.
- Meredith, Jack R.; Mantel, Samuel J. (2002). Project Management : A Managerial Approach (5th ed.). Wiley. ISBN 0-471-07323-7.
- Woolf, Murray B., PMP (2007). FASTER Construction Projects with CPM Scheduling (1st ed.). McGraw-Hill. ISBN 978-0-07-148660-6.
{{cite book}}: CS1 maint: multiple names: authors list (link)