Management I Project Management-Software Engineering-Lecture Slides, Slides of Software Engineering

Download Management I Project Management-Software Engineering-Lecture Slides and more Slides Software Engineering in PDF only on Docsity!

CS 501: Software Engineering

Fall 2000

Lecture 4

Management I: Project Management

Administration

• Assignment 1 has been posted to the web site. Note that submission is by email to the senior Teaching Assistant.
• Remember to copy email about the course to the Teaching Assistants.
• Readings about Requirements Analysis and Definition have been posted to the web site.

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

The Project Manager

• Create and maintain the schedule
• Should track progress against schedule
• Keep some slack in the schedule
• Be continually making adjustments:

Start activities before previous activity complete Sub-contract activities Renegotiate deliverables

• Keep senior management informed

Example: An Open University Course

Deliverables: 16 Written texts (bound in pairs) 8 Television programs 8 Radio programs 4 Computer programs 1 Home experimental kit (scientific calculator) 4 Assignments and sample solutions

Flexibility

Schedule: Dates for broadcasting TV and radio programs are fixed. Printing and mailings can be accelerated if overtime is used.

Functionality: The course team can decide what goes into the components of the course.

Resources: The size of the course team can be increased slightly.

Critical Path Method

Edit Unit 3

Print Unit 3

Revise Unit 3

Mail Unit 3

other activities

START END

Critical Path Method

Edit Unit 3

Typeset Unit 3

Revise Unit 3 Mail Units 3/

other activities

Edit Unit 4

Print Units 3/

Revise Unit 4

other activities

Typeset Unit 4

START

Time Estimates for Activities (Weeks)

Earliest Start Dates

Critical Path

• 0/ - 1/
  • 12/
  • 12/
    • 4/ - 15/15 17/ - 17/ - 17/ - 19/ - 22/ - 26/ - 23/24 25/

Slack

Key Personnel: Schedule for Editor

Earliest Start Date Activity

Weeks 15-16 Edit Unit 3 Weeks 17-18 Edit Unit 4 Weeks 19-20 Edit Unit 5 Weeks 21-22 Edit Unit 6

Week 15 Review draft of Unit 7 Week 17 Review draft of Unit 8 Week 19 Check proofs of Unit 3 Week 21 Check proofs of Unit 4

Weeks 18-19 Vacation Week 22 Out sick

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 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.