Tuesday, 26 July 2011
Task 4 Part 1- Management Myths
Do you like this story?
Software Myths :
Beliefs about software and the process used to build it – can be traced to the earliest days of computing. Myths have a number of attributes that have made them insidious.
Management myths :
Managers with software responsibility, like managers in most disciplines, are often under pressure to maintain budgets. Keep schedules from slipping, and improve quality.
- Myth : We already have a book that’s full of standards and procedures for building software. Won’t that provide with everything they need to know?
- Reality: The book of standards may very well exist, but is it used? Are software practitioners aware of its existence? Does it reflect modern software engineering practice? Is it adaptable? Is it streamlined to improve time to deliver while still maintaining a focus on quality? In many cases. The answer to all of these questions is no.
- Disscussion :Software engineering is an ever changing field that is always up to date with new technologies and resources. The book that we have is sufficient to get us started but further research is required in order to find the best and most up-to-date way of engineering a software.
- Myth : If we get behind schedule, we can add more programmers and catch up
- Reality : Brooks said “Adding people to a late software project makes it later.” As new people are added, people who were working must spend time educating the newcomers, thereby reducing the amount of time spent on productive development. People can be added but only in a planned and well-coordinated manner.
- Disscussion : More people means more minds at work in order to develop a software. The fact that these new people have not been around since the beginning of the project means that they are practically only seeing it for the first time and need to be brought to the same page as the developing team's current progress. This takes a lot of time and is not affordable at a late software project.
- Myth : If I decide to outsource the software project to a third party. I can just relax and let that firm build it.
- Reality : In an organization does not understand how to manage and control software projects internally, it will invariably struggle when it outsources software projects.
- Disscussion : When an organization outsources a project, they need to know exactly what they want from it as in the product of the software. The requirements gathered at the beginning of a project might change as software is developed and we also have to consider the fact that the developing firm makes a mistake in software development that conflicts with the desired outcome of the client.
This post was written by: UNITENIAN AUTHORS
Subscribe to:
Post Comments (Atom)
0 Responses to “Task 4 Part 1- Management Myths”
Post a Comment