This is an old revision of this page, as edited by RexNL (talk | contribs) at 22:16, 13 February 2006 (Reverted edits by 136.186.1.118 (talk) to last version by RexNL). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 22:16, 13 February 2006 by RexNL (talk | contribs) (Reverted edits by 136.186.1.118 (talk) to last version by RexNL)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)Scope (products) of a project is the sum total of all projects products and their requirements or features.
Sometimes scope is used to mean the totality of work needed to complete a project.
In traditional project management, the tools to describe a project's scope (product) are the product breakdown structure and product descriptions. The primary tool to describe a project's scope (work) is the work breakdown structure.
Extreme project management advocates the use of user stories, feature lists and feature cards to describe a project's scope (product).
If requirements are not completely defined and described and if there is no effective change control in a project, scope or requirement creep may ensue.
 | This organization-related article is a stub. You can help Misplaced Pages by expanding it. |