Software project management: Difference between revisions

Revision as of 11:03, 7 May 2010

Revision as of 11:28, 7 May 2010

Line 10:

* [[Change management]] is the process of identifying, documenting, analyzing, prioritizing and agreeing on changes to [[scope (project management)]] and then controlling changes and communicating to relevant stakeholders. [[Change impact analysis]] of new or altered scope, which includes [[Requirements analysis]] at the change level, is an important part of the [[software engineering]] process; whereby business analysts or [[software developers]] identify the altered needs or requirements of a client; having identified these requirements they are then in a position to re-design or modify a solution. Theoretically, each change can impact the timeline and budget of a software project, and therefore by definition must include [[risk-benefit analysis]] before approval.

* [[Software configuration management]] is the process of identifying, and documenting the scope itself, which is the softaresoftware product underway, including all sub-products and changes and enabling communication of these to relevant stakeholders. In general, the processes employed include [[version control]], [[naming convention (programming)]], and software archival agreements.

* [[Release management]] is the process of identifying, documenting, prioritizing and agreeing on releases of software and then controlling the release schedule and communicating to relevant stakeholders. Most software projects have access to three software environments to which software can be released; Development, Test, and Production. In very large projects, where distributed teams need to integrate their work before release to users, there will often be more environments for testing, called [[unit testing]], [[system testing]], or [[integration testing]], before release to [[User acceptance testing]] (UAT).