#1 Feature Document

[Narasimha A]

The goal of the tool is to enable organizations to manage different projects following an iterative,agile process. The tool will model an agile process similar to extreme programming.

A project will start by creating a feature document. This provides a high level picture of the project. The feature document contains a simple list of high level features. The stakeholders in the project will prioritize the features and create releases . A release is a set of features.Each release consists of iterations. Each iteration implements a set of features in that release through "stories". A story is a requirement which is small enough to be implemented in 3-4 days, but can be seen by the end-users of the system. A story is connected to a feature from the feature document.
A story flows through the following states is as follows:
New -> In analysis -> Ready for Development -> Development in progress-> Ready for QA -> QA in progress-> QA complete->Finished.

A story can depend on other stories. A project manager should be able to generate reports at an iteration level or a release level. A report consists of total # of stories in play ['In analysis' to 'QA complete' states], # of stories in each status