Archiving Information

SUCCESS of a project largely depends on how well the requirements are:

-understood

-captured

-effectively managed

Detailed and careful archiving of Information:

-Gives clarity related to all spheres of the project

-Brings uniform understanding and consensus between all stakeholders

-Provides a ready record, based on which the project can be monitored once work begins.

Detailed and careful archiving of Information becomes the base for various planning tools like:

Work Breakdown Structure (WBS), Cost Planning and Quality Planning

.

The Components

The basic components of the Information archived for a Project as derived from the Requirements include:

-The Business need / opportunity

-Project Objectives

-Functional requirements

-Non- functional requirements (like safety, security, etc.)

-Quality Requirements

-Acceptance Criteria

-Guiding principles of the Organization

-Assumptions

-Constraints, etc

Traceability is being able to link the requirement back to its origin and continue to monitor it through the project lifecycle

VIDEO:

Copyright is protected for GROOK Network - Microsoft Project Tutorial

Forums:

Main menu