Download
1 / 4
40 likes | 150 Views
Software Myth. Management Myths [Pressman]. We already have standards and procedures for building software; isn’t that enough? How widely used is it? How relevant to the team? How useful to the project? If we’re behind schedule, we’ll just add more programmers to catch up
E N D
Management Myths [Pressman] • We already have standards and procedures for building software; isn’t that enough? • How widely used is it? • How relevant to the team? • How useful to the project? • If we’re behind schedule, we’ll just add more programmers to catch up • “Adding people to a late project makes it later” [Brooks] • Ramp-up time • Interference • If I outsource a project, I can just relax • Management issues are much more difficult, and if not understood, will sink the project
Customer Myths [Pressman] • A General statement of objective is sufficient to begin write programs. • Requirements can change, and that’s OK because software is so flexible • Most software project failures can be traced to inadequacy of requirement specifications
Software Engineers’ Myths [Pressman] • Once the program is written, I’m done • Between 60-80% of effort expended after delivery • Until the program is written, quality is uncertain • The only deliverable is the program itself • Documentation is Software-Engineering busy work
