Requirements collection

Requirements Collection 

Once the project title is decided, now its time to decide what actually to be done. It must include the two end points: 

-where to begin and 

-where to finish. 

This means, we need to decide what is the situation when we begin and what the final product should look like. 

The path to take from this beginning point to the ending point should not bother the team at this stage. The path is what we need to design and implement. Hence it is the time to create the questions and surely not trying to find answers. 

Divide your batch into two groups: 

One plays the role of the clients and the other group plays the role of requirements gathering team. 

Collection 

The process must include interviews, discussions. The two teams must interact in all possible ways to exchange the needs and ideas. The whole process must concentrate only on finding the problems of the clients and never try to look for the ways to reach the solutions here. At every act, make sure to document. 

Understand

The next step is to understand these questions/ problems listed in the Collection phase. 

-Let each member of the team list the requirements they have understood.

- Now all members sit together and look at each one list and discuss.  Arguments provide good opportunities for getting best.

A final list of requirements is now prepared with each member's participation. 

Document 

Now document all the requirements listed.  This list must be complete and unambiguous. It must be well documented. 

This document will proceed further to design phase.