What should you consider when managing a project?

  1. What is the business problem you are trying to solve, and who has a stake in its resolution?

  2. What features are essential to a solution?

  3. How can the proposed solution be described in language that can be understood by technical and nontechnical people?

  4. What are the available resources (time, people, money)?

  5. How should requirements be prioritized?

  6. How can you verify that the system will function as described and perform with acceptable speed and efficiency?

  7. How can you trace dependency relationships between requirements?

  8. How can changes to the system be limited and negotiated so that the product can be completed and stakeholders remain engaged?

  9. What is the procedure for reviewing and resolving changes to requirements?

Review

Requirements management is the systematic approach to organizing and documenting project requirements so that you can manage change. Poor change management is a key cause of project failure. To manage requirements projects successfully, you should identify the business problem you are trying to solve; use a process that involves all those with a stake in the success of the project; and use a tool that enables you to organize, prioritize, and track changes to your project requirements.

What's next?

Module 3 introduces you to some of the key features of RequisitePro. To go to Module 3, click the right arrow.

Page 3 of 3    Main Menu Previous Page Next Page