Ch31 - Chapter31 YourPrescriptionfor RequirementsManagement

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 31 Your Prescription for  Requirements Management  
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Prescription for Requirements  Management: Steps Step 1:  Get Organized Step 2:  Understand the Problem Being Solved Step 3:  Understand User and Stakeholder Needs Step 4:  Define the System Step 5:  Continuously Manage Scope and Manage Change Step 6:  Refine the System Definition Step 7:  Build the Right System Step 8:  Manage the Requirements Process
Background image of page 2
Step 1: Get Organized  A. Meet with your team and agree on the basic software  processes you will employ. B. Decide how you will manage requirements on the project  and document this process in a short one- to two-page  requirements management plan. C. Decide what types of software tooling you will apply to  the project. D. Determine a configuration management plan for your  code and requirements artifacts. E. Establish an iteration plan and determine the basic  project metrics and reporting disciplines.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Step 2: Understand the Problem Being  Solved  A. Execute the five-step problem analysis process. 1. Gain agreement on the problem being solved. Write it down. 2. Understand the root cause of the problem (if applicable to your  situation). 3. Identify the stakeholders and users, or actors, in your system. 4. Define the system boundary. Document the boundary and the  identified stakeholders and actors in a system context diagram  or preliminary use-case model. 5. Identify constraints imposed on the solution. Write them down.
Background image of page 4
Step 2: Understand the Problem Being  Solved  B. Circulate the problem statement to external  stakeholders and insist that you gain agreement on the  problem statement before moving forward.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Step 3: Understand User and  Stakeholder Needs A. Create a structured interview using a generic template
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 01/17/2012.

Page1 / 18

Ch31 - Chapter31 YourPrescriptionfor RequirementsManagement

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online