CMPE/SE 131 Software Engineering April 20 Class
Author : faustina-dinatale | Published Date : 2025-08-13
Description: CMPESE 131 Software Engineering April 20 Class Meeting Department of Computer Engineering San José State University Spring 2017 Instructor Ron Mak wwwcssjsuedumak 2 Project Scheduling Triangle Time resources and features are
Presentation Embed Code
Download Presentation
Download
Presentation The PPT/PDF document
"CMPE/SE 131 Software Engineering April 20 Class" is the property of its rightful owner.
Permission is granted to download and print the materials on this website for personal, non-commercial use only,
and to display it on your personal computer provided you do not modify the materials and that you retain all
copyright notices contained in the materials. By downloading content from our website, you accept the terms of
this agreement.
Transcript:CMPE/SE 131 Software Engineering April 20 Class:
CMPE/SE 131 Software Engineering April 20 Class Meeting Department of Computer Engineering San José State University Spring 2017 Instructor: Ron Mak www.cs.sjsu.edu/~mak 2 Project Scheduling Triangle Time, resources, and features are interdependent. At the beginning when you schedule a project, you can have firm time and resources, or a firm feature set, but not both. FEATURES RESOURCES TIME 3 Project SchedulingTriangle, cont’d Because developers want to be productive (i.e., make accomplishments), unrealistic schedules are demoralizing. Crunch mode and death march. FEATURES RESOURCES TIME Scheduling Disasters Recall the dangers of allowing the marketing and sales departments to set engineering schedules. Their goal is to beat the competition to market Engineering’s goal is to build a reliable product. A recent example: This company wanted to beat Apple’s announcement of the new iPhone 7. The exploding Samsung Galaxy Note 7 phone. 4 5 Project Failures Why study failed projects? Failure is a far stronger learning experience than success. Robert Glass When you’re failing, you’re forced to be creative, to dig deep and think hard, night and day. Every company needs people who have been through that. Bill Gates 6 Causes of Project Failures Technology New technology that isn’t ready or is improperly used. Performance Performance requirements were not seriously considered during design. “ We can just add faster hardware.” Project management Inexperienced and/or clueless managers. Unrealistic schedules. 7 10 Signs of Project Failure Project managers don’t understand users’ needs. Scope is ill-defined. Project changes are managed poorly. The chosen technology changes. Business needs change. Deadlines are unrealistic. The project lacks people with appropriate skills. Best practices and lessons are ignored. Users are resistant. Sponsorship is lost. 8 Phases of a Failing Project Crunch mode Extremely tight project schedule. Project members under pressure. Death march Project schedule nearly impossible. Project members smell potential failure. Failure Over budget and/or missed deadlines. Doesn’t meet functional and/or nonfunctional requirements. 9 Example of a Failed Project Denver International Airport’s Automated Baggage-Handling System 10 Background: Denver International Airport New Denver International Airport (DIA) Replacement for Denver’s aging Stapleton Airport. Construction began in November 1989. Originally scheduled to open in October 1993. Political battle between expanding Stapleton vs. building the new DIA. New airport meant jobs during an economic downturn. Start of construction was delayed. 11 Background: Denver International Airport, cont’d United Airlines was a major carrier for the new DIA. Housed in Concourse B. United Airlines wanted its own