Two stages of project requirements management


	CentriQS -15% OFF Business management software for small & midsize enterprises Play Demo		VIP Task Manager Task management software for teams & small offices Play Demo / Download

Successful experience of project implementation shows that efficient *requirements management* is the key factor of the process of product development. Requirements define what the product should do. Therefore during all lifecycle of the project, it is necessary to organize effective work with them. The main objectives of the process are as follows: Understanding structure and dynamics of project Understanding current problems of project and defining potential possibilities of its improvement Revealing the system requirements needed for automation support of project performance Establishing and maintaining the agreement with clients and other interested persons about what the product should do Providing product developers with the best understanding of requirements before the project launching Defining functional borders of the product Providing basis to planning technical maintenance of product development stages Providing basis for costs and time estimation needed for the product development Defining graphic interfaces of users taking into account their requirements and goals. Requirements management is understood as the methodical approach to managing and planning of requirements implementation. This approach regulates the following procedures of work with requirements: revealing, documenting, verification and the statement of requirements, planning of implementation and tracing of changes of requirements. The approach provides two stages: preparation for requirements management and actually management of them. Preparation is very important stage that allows to regulate organizational procedures, to define templates of the basic documents, to plan management requirements process, and also to define roles of the process participants. The typical composition of project group participants within the limits of the process is the following: system analyst requirements expert requirements reviewer architect In most of projects the role of the expert is played, as a rule, by the customer but in some cases the expert is a part of project team from outside the project developer.
Play Demo	Management of requirement. Revealing of requirements and their structuring is led by system analyst on the basis of "Procedure of requirements revealing developed on a preparation stage of management of requirements. Based on the list of the revealed requirements, the system analyst models requirements. After the model creation he in cooperation with the requirements expert makes necessary documentation. On this step the templates of documents are applied. On the next step verification and the statement of requirements is made.
The useful software tool for the organization of efficient management of product requirements in the project is VIP Task Manager. It allows the project team to work with requirements, to trace possible changes in them and to organize discussions. VIP Task Manager gives a chance to organize controllable access to the requirements and allows all participants of the project team to be well informed of current requirements, their context and jointly to work on creation of qualitative product. Via local office network or Internet VIP Task Manager grants access to the requirements for all project participants which work remotely. The software allows to create tasks for each product requirement and assign it to responsible team member.
In VIP Task Manager you can use such task attributes like "Notes", "Attachment", "Comments" and "Custom field" to specify the product requirements. Each requirement can be represented as a task in VIP Task Manager and you can establish for them the additional information, define priorities, due dates of implementation and any other attributes (use custom fields). Usually customer creates product requirements in the form of separate document (MS Word, PDF file, or other). When you create task for a particular requirement, you can attach any type of file or link to the product requirement documents. At the same time all documentation is stored in single database and all project participants may have access to the product requirement.		Play Demo