Presented by: Marek Hajek 02/16/2012

1. Applied Software Project Management(Andrew Stellman & Jennifer Greene)Chapter 4 - Part 1Project Schedules Presented by: MarekHajek 02/16/2012 [Majority of slides created by MarekHajek for CS 709B classroom use at UNR, Spring 2012]

2. Outline • Project Schedule (PS) [+] • PS Prerequisites[+] • Steps in Building a PS [+] • Gantt Chart [+] • How to Reconcile a PS [+] • Meetings[+] • Critical Path [+] • Don’t Abuse Buffers • Summary [+]

3. Project Schedule What is a project schedule? • A calendar that links tasks with resources.

4. Building Project Schedule Project Schedule Prerequisites • WBS – Work Breakdown Structure. • Estimate of effort for each task. • Resource list and their availability. http://www.microsoft.com/global/project/en-us/RichMedia/demos/shifting/player.html?course=shifting Managing Tasks In Project [0:00 – 0:40] [5:07] Managing Time in Project [4:30] Managing Resources In Project [0:00 - 1:45]

5. Building Project Schedule Steps in Building a Project Schedule • Allocate resources to tasks. • Identify dependencies between tasks. • Create the schedule document. • Revise/reconcile schedule with organization needs.

6. Building Project Schedule 1. Allocate Resources to Tasks • Most difficult and time consuming part of effective project management. • Assign 1 or more resources to each task. • Must account for overhead when more than 1 person assigned to task.* http://www.microsoft.com/global/project/en-us/RichMedia/demos/shifting/player.html?course=shifting Managing Resources In Project [1:45 – 2:00]

7. Building Project Schedule Keep in mind… • Parkinson (1958): “Work expands so as to fill the time available for its completion.” • Brooks: “Nine women cannot have a baby in one month.” • Effort <> Duration. • Effort: amount of work spent on a task measured in person hours. • Duration: time from task start to completion.

8. Building Project Schedule 2. Identify Dependencies Dependency: • One task requires a deliverable from another task. • Tasks share the same resource.

9. Building Project Schedule 3. Create the Schedule Document • Typically created using project management software such as Microsoft Project. • Graphically represented as a Gantt chart.

10. Building Project Schedule Gantt Chart and its Elements • Task and its duration = bar • Milestone = black diamond • Summary task = black bar that spans over tasks 4. Dependency = line with arrow http://www.microsoft.com/global/project/en-us/RichMedia/demos/shifting/player.html?course=shifting Managing Time In Project [4:39]

11. Building Project Schedule 4. Reconcile Schedule • Must reconcile when project End date > Needed date • Reorganize/reallocate tasks and resources more efficiently. • Add resources. • Release project in phases.

12. Project Schedule Maintenance Meetings • Review meetings. • Should be part of project schedule. • Review whether schedule is accurate. • Take action if schedule drifted off track: rearrange schedule, overtime, revise vision and scope document. • Milestone review meetings. • Typically scheduled after last task of project phase.

13. Project Schedule Maintenance Important! Report serious problems to your project manager immediately so that he can promptly address issue and potentially rearrange schedule!

14. Project Schedule Maintenance Critical Path • Critical path consists of a sequence of tasks that represent the minimum time required to complete the project. • There is never slack in critical path. • http://office.microsoft.com/en-us/project-help/video-show-the-critical-path-VA101808853.aspx • http://www.microsoft.com/global/project/en-us/RichMedia/demos/shifting/player.html?course=shifting • Tracking With Project [0:00]

15. Project Schedule Maintenance Don’t abuse buffers • A buffer is a task added to the schedule with no specific purpose except to account for unexpected delays. • This practice involves either adding extra tasks or padding existing tasks at strategic points in the schedule where overruns are “expected”. • Buffers can be useful: • On a year-long project, every programmer will take two weeks of vacation • Buffers can be used to account for this known delay • Buffers are often abused • The idea that overruns are expected means that there is an implicit assumption that the estimate is incorrect. • Buffers should not be used to add time to compensate for an inaccurate estimate. *Stellmanand Greene’s Chapter 4 slide content.

16. Part I Summary • Project Schedule Prerequisites • WBS, Estimate of effort per task, resource list/schedule. • Building Project Steps • Allocate resources to tasks, identify dependencies, create the schedule document, reconcile schedule. • Meetings. • Review & Milestone meetings. • Critical Path • A sequence of tasks = minimum time required to complete project. • Don’t abuse buffers • Don’t pad extra space into project schedule for just-in-case scenarios.

17. Chapter 4Project SchedulesThank you for you attention.Questions? Presented by MarekHajek