1 / 4

Debunking Common Software Development Myths for Successful Project Management

In the realm of software development, many myths can hinder project success. This article explores pervasive misconceptions, such as the belief that existing standards are sufficient or that adding more programmers can rectify schedule delays. It emphasizes the importance of understanding management challenges and requirement specifications, highlighting that software is not as flexible as often perceived. The article also discusses the critical need for continuous effort post-delivery and dispels the notion that documentation is merely busy work. Embracing reality over myth is essential for project success.

tess
Télécharger la présentation

Debunking Common Software Development Myths for Successful Project Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Myth

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

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

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

More Related