To manage new development efforts, companies applied the established project management methods, but project schedules slipped during test runs, especially when confusion occurred in the gray zone between the user specifications and the delivered software.
As the industry has matured, analysis of software project management failures has shown that the following are the most common causes:[2][3][4] The first five items in the list above show the difficulties articulating the needs of the client in such a way that proper resources can deliver the proper project goals.
Today software project management methods are still evolving, but the current trend leads away from the waterfall model to a more cyclic project delivery model that imitates a software development process.
These processes exist primarily for supporting the management of software development, and are generally skewed toward addressing business concerns.
In computing, the term "issue" is a unit of work to accomplish an improvement in a system.
Different companies have different definitions of severities, but some of the most common ones are: In some implementations of software development processes, issues are investigated by quality assurance analysts a system is verified for correctness, and then assigned back to a member of the development team to resolve the identified issue.