To Do:

1. Create a new project ticket to store requirements.
2. Create 1 tasks or artifact for each specific feature or deliverable to the client. For example, one artifact for the framework, and one for each form, report, and supporting application such as an installation program, or help file. If a printed user manuel is desired, we usually complete that with a separate Documentation project, but you could add that as a task to the requirements document as well.

2-Step or Rolling Estimates

With our 2-Step approach, we stop after an initial step-1 effort and seek authorization to build the application. With our rolling estimates approach, we just roll right into building the application frequently starting the initial coding phase toward the end of a Req+Design phase.

Informal, Formal, and Robust

For our PSDP informal path, the requirements project is approved and we usually just roll with the requirements project as Step-2 of our 2-Step approach. With our Formal and Robust paths, our preferred technique is to copy the initial requirements into a new project and close the Initial Requirements project as complete prior to building the application. This allows us to establish a baseline of requirements and estimates we can measure ourselves against as the project proceeds. Plus, it clearly documents and changes in scope.