Quote:
- During analysis and design, requirements change
- During development, requirements change
- Requirements change all the time
- Mistakes are made during analysis and subsequently design, quite serious ones, which are subsequently overlooked until someone actually tries to use the first prototype
- Design and analysis takes time away from other tasks, as a result the business becomes less efficient beacuse the solution is delivered later
- People with absolutely ****all skill, get moved to being systems analysists, because it's perceived as "easier" than programming, they make a balls-up of it, then throw their shoddy half-done inaccurate "solutions" at the developers
IMHo change is a fact of life they will always change that should put a extra emphasys on the importance of Analysys and Design.............to estimate the level of change that can occur and choose appropriate Process model............You choose an worng model and it would make you like as hell later.
Quote:
There is a "Change Management" process for projects, as well as for software. I tend to call the software one "version control", and manage the project side with "variation orders" (I stole that concept from civil engineering/construction)
Why do you have to steal it when we have something called the Software Configuration Management...which accumodates all these :p