TABLE OF CONTENTS I've suggested previously the tremendous value of spending some time (in any endeavor) to plan the approach. Write (document) the planned approach to address the requirements-related work in a project requirements plan. As is the case with other plans, the requirements plan can be (and should be) revisited and updated frequently during the project. Some of the critical aspects of this plan are summarized in the checklist provided in Table 5.1 and discussed below. Note that all aspects are not necessarily always perfomed sequentially; some may be performed concurrently. Note that some aspects are iterative (done repeatedly based on the availability of new or different information). Retain flexibility in your approach (always) to allow new information to shape refinements in the approach.
| Done? | Step | Action or Activity |
|---|---|---|
| 1 | Review related historical information | |
| 2 | Review related organizational policies | |
| 3 | Identify the stakeholders of the project | |
| 4 | Develop a strategy to involve customers and users throughout the development effort | |
| 5 | Write (and iterate) a project vision and scope document | |
| 6 | Develop a requirements plan | |
| 7 | Provide for peer reviews and inspections of all requirements-related work products | |
| 8 | Initiate a project glossary and a project acronyms list | |
| 9 | Decide on the life-cycle approach to be used on the project | |
| 10 | Begin tailoring of the corporate (or other) requirements process | |
| 11 | Establish a mechanism to evolve the real requirements from the stated... |
