- Dec 12, 2020
- 895
- 3,426
Isn't this just the same effect as any other software development
If a project has a well defined specification with a well understood end point the likelihood of being finished on schedule is significantly increased.
If a project has a loosely defined specification, allowing for adaptation, and then a customer base starts making requests, a number of which are integrated into the project, it becomes unwieldy and stages of development become less focused. New work also starts necessitating modifications to earlier code for backwards compatibility. So the whole development cycle slows.
Solution - to keep schedule on time - have a well identified and specified end point.
PS. (and ignore customer requests - that will go down well)
If a project has a well defined specification with a well understood end point the likelihood of being finished on schedule is significantly increased.
If a project has a loosely defined specification, allowing for adaptation, and then a customer base starts making requests, a number of which are integrated into the project, it becomes unwieldy and stages of development become less focused. New work also starts necessitating modifications to earlier code for backwards compatibility. So the whole development cycle slows.
Solution - to keep schedule on time - have a well identified and specified end point.
PS. (and ignore customer requests - that will go down well)
Last edited: