Release cycles
It is said that the initial development of a typical software system only accounts for 20% of the total system, meaning that additional enhancements introduced after the first release can account for as much as an additional four times the amount of software development. For projects that are anything other than a simple straightforward system such as a brochure style website, this can become a serious issue because clients without an understanding of software release cycles will want everything in the first release. This can lead to over ambitious expectations, ongoing changes and constant additions to the specification that keep delaying the first release. Ultimately, this risks the system being released too late; whether in terms ...
Get Going IT Alone: The Handbook for Freelance and Contract Software Developers now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
