CS 501: Software Engineering Fall 2000 Lecture 4 Management I: Project Management.

Slides:



Advertisements
Similar presentations
Project management.
Advertisements

Project Management Concepts
Richard Fisher 1 The University of Texas at Dallas Project Management BA 4320 Richard Fisher The University of Texas at Dallas.
CS3500 Software Engineering Project Management (1) In 1986 one well-known software engineer (Tom DeMarco) made the simple but important observation: “You.
© The McGraw-Hill Companies, Software Project Management 4th Edition Monitoring and control Chapter 9.
CS CS 5150 Software Engineering Lecture 4 Project Management.
CS3773 Software Engineering Lecture 8 Software Planning and Estimation.
SWE Introduction to Software Engineering
Feasibility and Cost/Benefit Analysis. Cost considerations u Cost classifications –Tangible / Intangible –Direct / Indirect –Fixed / Variable –Developmental.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 Project management.
1 CS 501 Spring 2008 CS 501: Software Engineering Lecture 4 Project Management.
1 CS 501 Spring 2005 CS 501: Software Engineering Lecture 4 Project Management.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Chapter 4 Project Management “…a huge topic.” See Part 6, “Management”, Chaps.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
1 SWE Introduction to Software Engineering Lecture 6 - Software Project Management.
Creator: ACSession No: 10 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringDecember 2005 Project Management CSE300 Advanced Software Engineering.
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
Section 4.0 Project Implementation. Factors that Ensure Success  Update the project plan  Stay within scope  Authorized change implementation  Providing.
1 CS 501 Spring 2007 CS 501: Software Engineering Lecture 4 Project Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Project Management and Scheduling
Software Engineering Principles Chapter 3 From Software Engineering by I. Sommerville, Slide 1 project managementorganizing planning scheduling Learning.
贾银山 Software Engineering, Chapter 5 Slide 1 Project management.
©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 5 Slide 1 Chapter 5 Project Management Modified by Randy K. Smith.
Feasibility and Cost/Benefit Analysis. Cost considerations u Cost classifications –Tangible / Intangible –Direct / Indirect –Fixed / Variable –Developmental.
Project management DeSiaMore 1.
Project management.
Software Project Management Task Estimating and Scheduling
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter 6: Project Time Management
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Chapter 3: Project Management Omar Meqdadi SE 2730 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
CS 5150 Software Engineering Lecture 6 Project Management.
CS 360 Lecture 4.  The operating system for the IBM 360 was two years late!  Question:  How does a project get two years behind schedule?  Answer:
1 Chapter 5 Project management. 2 Project management : Is Organizing, planning and scheduling software projects.
Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project management Lecture 10. Topics covered Management activities Project planning Project scheduling Risk management.
Project Planning Techniques U08784Software Project Management Rosemary Phillimore.
CSEM01 - wk8 - Software Planning1 Software Planning CSEM01 SE Evolution & Management Anne Comer Helen Edwards.
Managing Resources Program Evaluation and Review Technique (PERT) Production Process.
CS 501: Software Engineering Fall 1999 Lecture 6 Management I: Project Management.
CS CS 5150 Software Engineering Lecture 4 Project Management.
Project management.  To explain the main tasks undertaken by project managers  To introduce software project management and to describe its distinctive.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Engineering, 8th edition. Chapter 5 1 Courtesy: ©Ian Sommerville 2006 Oct 13 th, 2008 Lecture # 6 Project management.
1 Project management. 2 Topics covered Management activities Project planning Project scheduling Risk management.
Dr Izzat M Alsmadi Edited from ©Ian Sommerville & others Software Engineering, Chapter 3 Slide 1 Project management (Chapter 5 from the textbook)
Lecture 61 Project planning tool Lecture 62 Objectives Understand the reasons why projects sometimes fail Describe the different scheduling tools, including.
Project Management Inspections and Reviews 1 February.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
Project Time Management
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 4 Project Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project management 1/30/2016ICS 413 – Software Engineering1.
CS CS 5150 Software Engineering Lecture 7 Project Management.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
CS CS 5150 Software Engineering Lecture 7 Project Management.
1 Project management Organising, planning and scheduling software projects.
HNDIT23082 Lecture 10:Software Project Management
CS 501: Software Engineering
Exam 0 review CS 360 Lecture 8.
Assistant Professor of Computer Science Washington State University
Project Management and Information Security
CS 501: Software Engineering
Project Time Management
Software Project management
Presentation transcript:

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 to the senior Teaching Assistant. Remember to copy about the course to the Teaching Assistants. Readings about Requirements Analysis and Definition have been posted to the web site.

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

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

Project Planning Methods The Critical Path Method, Gantt charts, Activity bar charts, etc. are roughly equivalent. These methods are best when: Model is updated regularly (e.g., monthly) The structure of the project is well understood The time estimates are reliable Activities do not share resources [Critical Path Method is excellent for large construction projects.]

Example: An Open University Course Deliverables: 16Written texts (bound in pairs) 8Television programs 8 Radio programs 4Computer programs 1Home experimental kit (scientific calculator) 4Assignments 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.

Scheduling: Critical Path Method An activity A dummy activity An event A milestone

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/4 other activities Edit Unit 4 Print Units 3/4 Revise Unit 4 other activities Typeset Unit 4 START

Critical Path Method START Edit Unit 3 Script TV 2 Make TV 2 Edit Unit 4 Prototype Computer 1 Program Computer 1 Document Computer 1 Mail Delivery

Time Estimates for Activities (Weeks)

Earliest Start Dates

Latest Start Dates

Critical Path 0/00/0 1/11 12/12 12/14 4/13 15/1517/17 19/20 22/23 26/26 23/24 25/25

Slack 0/00/0 1/11 17/17 23/ /12 12/14 4/13 15/1517/17 19/20 22/23 26/26 25/

Key Personnel 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?

Key Personnel: Schedule for Editor Earliest Start DateActivity Weeks 15-16Edit Unit 3 Weeks 17-18Edit Unit 4 Weeks 19-20Edit Unit 5 Weeks 21-22Edit Unit 6 Week 15Review draft of Unit 7 Week 17Review draft of Unit 8 Week 19Check proofs of Unit 3 Week 21Check proofs of Unit 4 Weeks 18-19Vacation Week 22Out 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.

Experience with Critical Path Method Administrative computing department at Dartmouth used the Critical Path Method for implementation phase of major projects. Experience: Elapsed time to complete projects was consistently 25% 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 on many activities (schedule conflicts) System ZZZ (non-billable hours)

Reading Before next class, read the readings on Requirements that have been posted on the web site.