32
CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

Embed Size (px)

Citation preview

Page 1: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 1

CS 5150 Software Engineering

Lecture 4

Project Management

Page 2: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 2

Administration

Quiz 1

• Quiz 1 is next Thursday. Information is posted on the web site.

Projects

• Announcements by project teams

Page 3: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 3

Source Code Management

See the slides on the Web site.

There is a link from Lecture 4 on the Syllabus page.

Page 4: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 4

OS 360

The operating system for the IBM 360 was two years late.

Question: How does a project get two years behind schedule?

Answer: One day at a time!

Fred Brooks Jr., The Mythical Man Month

Page 5: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 5

The Aim of Project Management

To complete a project:

• On time

• On budget

• With required functionality

• To the satisfaction of the client

• Without exhausting the team

To provide visibility about the progress of a project

Page 6: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 6

Aspects of Project Management

Planning

• Outline schedule during feasibility study

• Detailed schedule at the beginning of a project or phase of a project

Progress tracking

• Regular comparison of progress against plan

• Regular updating of the plan

Final analysis

• Analysis of project for improvements during next project

Page 7: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 7

Terminology

Deliverable

Work product that is provided to the customer (report, presentation, documentation, code, etc.)

Milestone

Completion of a specified set of activities (e.g., delivery of a deliverable, completion of a process step)

Page 8: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 8

Terminology

Activity

Part of a project that takes place over time (also known as a task).

Event

The completion of a group of activities.

Dependency

An activity that cannot begin until some event is reached

Resource

Staff time, equipment, or other limited resources required by an activity.

Page 9: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 9

General Approach to Project Planning

Identify deliverables and milestones

Divide project into activities (tasks)

For each activity estimate:

• time to complete from when activity begins

• dependencies on events before beginning

• resource requirements (e.g., personnel)

Build a model that uses this data to create a work-plan, including schedule, resource allocation, and flexibility

Page 10: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 10

Project Planning Methods

Critical Path Method, Gantt charts, Activity bar charts, etc.

• Build a work-plan from activity data.

• Display work-plan in graphical form.

Project planning software (e.g., Microsoft Project)

• Maintain a database of activities and related data

• Calculate and display schedules

• Provide progress reports

Page 11: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 11

A Simple Gantt Chart

Source: Microsoft using Excel

Page 12: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 12

Gantt Charts

• Dates run along the top (days, weeks or months).

• Each row represents an activity. Activities may be scheduled sequentially, in parallel or overlapping.

• The schedule for an activity is a horizontal bar. The left end marks the planned beginning of the task. The right end marks the expected end date.

• The chart may be updated by filling in each activity to a length proportional to the work accomplished.

• Progress to date can be compared with the plan by drawing a vertical line through the chart at the current date.

Page 13: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 13

A More Complex Gantt Chart

Source: SmartDraw

Page 14: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 14

Activity Graph

An activity (task)

A dummy activity (dependency)

An event

A milestone

A scheduling technique that emphasizes dependencies

Page 15: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 15

Example: Activity Graph for a Distance Learning Course

START

Edit 1

Script TV

Make TV

Edit 2

Prototype Software

WriteSoftware

DocumentSoftware

Mail

Plan TV

Plan 1

Write 1

Plan 2

Plan Software

Write 2

Typeset 1

Typeset 2

Print

Page 16: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 16

Scheduling: Background

PERT

Program Evaluation and Review Technique introduced by the U.S. Navy in 1957 to support the development of its Polaris submarine missile program.

PERT/Time

Activity graph with three time estimates (shortest, most probable, longest) on each activity to compute schedules.

PERT/Cost

Added scheduling of resources (e.g., facilities, skilled people, etc.)

Page 17: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 17

Critical Path Method

Uses Activity Graph with single time estimate for each activity to estimate:

earliest start date -- every activity begins at first possible time

latest start date -- every activity begins at the last possible time

slack -- difference between the latest and earliest start dates

A standard method for managing large construction projects.

On big projects, activity graphs with more than 10,000 activities are common.

Page 18: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 18

Time Estimates for Activities (Weeks)

6

4

2

2

3

3

3

3

82

1 1

4

12

12

1

4

Page 19: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 19

Earliest Event Dates and Earliest Start Dates

Activities: a directed edge of the graph.

Earliest start date: the earliest date that it is possible to start an activity.

Earliest event date: the date that all the activities ending at that node will be completed, assuming that every activity begins at its earliest start date.

Earliest project completion date: the date on which the project is completed assuming that every activity begins on its earliest start date.

Page 20: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 20

Earliest Event Dates and Earliest Start Dates

6

4

2

2

3

3

3

3

82

11

4

12

12

1

4

0

1

12

12

4

17

19

23

5

2522

17

17

15

15

8

2023 24

Earliest dates for an event are in red

Page 21: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 21

Latest Event Dates and Latest Start Dates

Latest start date: the latest date that it is possible to start an activity and still complete the project by the earliest project completion date.

Latest event date: the latest date that all the activities ending at that node must be completed, in order to complete the project by the earliest project completion date.

Page 22: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 22

Latest Event Dates and Latest Start Dates

6

4

2

2

3

3

3

3

82

11

4

12

12

1

11

12

14

13

15

20

23 24 25

4 22

0

17

17

10

1817

2019

Each event must be achieved by the date shown or the final date will not be met.

Latest event dates in blue

Page 23: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 23

Slack and Critical Path

Slack: the difference between the latest start date and the earliest start date of an activity

Critical path: a path through the graph where every activity has zero slack

If an activity on the critical path is not started on its earliest start date or takes longer than the predicted time to complete, then the project completion date is delayed.

Page 24: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 24

Slack

0/0

1/11

17/17

23/24

1

22

12/12

12/14

4/13

15/15 17/17

17/17 19/20

22/23 25/25

4

8

123 2

312

4

4

3

3

6

1 1

10 10

00 0

0

00

9

9

2

2

23

11

11

5

Slack in purple

Page 25: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 25

Critical Path

0/0

1/11

12/12

12/14

4/13

15/15 17/17

17/17

17/17

19/20

22/23 23/24 25/25

Every activity on the critical path must begin on the earliest start date.

Critical path in orange

Page 26: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 26

Estimating the Time for an Activity

With experienced staff, estimating the actual time to carry out a single task is usually fairly accurate, but ...

The little bits and pieces are underestimated

• The time from almost "done" to completely "done" is much longer than anticipated. (There's just one thing to tidy up. I need to put the comments into better shape. I really should get rid of that patch.)

• The distractions are not planned for. (My system crashed and I decided to upgrade the software. My child's school was closed because of snow. I spent the day showing visitors around.)

Some things have to be done twice.

Page 27: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 27

Start-up Time

On a big project, the start-up time is typically three to six months:

• Personnel have to complete previous projects (fatigue) or be recruited.

• Hardware and software has to be acquired and installed.

• Staff have to learn new domain areas and software (slow while learning).

• Clients may not be ready.

Page 28: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 28

Final Analysis with Critical Path Method

Administrative computing department at Dartmouth used the Critical Path Method for implementation phase of major projects (plan developed after project was well-understood).

Experience: Elapsed time to complete projects was consistently 30% to 40% longer than predicted by model.

Analysis:

• Some tasks not anticipated (incomplete understanding)• Some tasks had to be redone (change of requirements, technical changes)• Key personnel were on many activities (schedule conflicts)• System ZZZ (non-billable hours)

Page 29: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 29

Adding Resources to Activity Graph or Gantt Chart

Each activity is labeled with resources, e.g.,

Number of people (e.g., 2 Java programmers)

Key personnel (e.g., chief system architect)

Equipment (e.g., 3 servers with specified software)

Facilities (e.g., video conference center)

Each resource is labeled with availability, e.g.,

Hiring and training

Vacations

Equipment availability

Page 30: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 30

Using Critical Path Method for Resources

Assume every activity begins at earliest start date:

In each time period, calculate:

resources required

resources available

Identify shortage / surplus resources

Adjust schedule

acquire extra staff (e.g., consultants)

rearrange schedule (e.g., change vacations)

change order of carrying out activities

The earlier that a problem is known, the easier it is to fix.

Page 31: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 31

Key Personnel: The Mythical Man Month

In computing, not all people are equal

• The best are at least 5 times more productive.• Some tasks are too difficult for everybody.

Adding more people adds communications complexity

• Some activities need a single mind.• Sometimes, the elapsed time for an activity can not be

shortened.

What happens to the project if a key person is sick or quits?

Page 32: CS 5150 1 CS 5150 Software Engineering Lecture 4 Project Management

CS 5150 32

The Project Manager

• Create and maintain the schedule.• Track progress against schedule.• Keep some slack in the schedule (minimize risk).• Continually make adjustments:

Start activities before previous activity completeSub-contract activitiesRenegotiate deliverables

• Keep senior management informed (visibility).

The project manager needs the support of the head of the development team and the confidence of the team members.