Term
| The main purpose of managing requirements and communication is to: |
|
Definition
| help minimize the "Negative Impact" in a project and ensure a gradual consensus of the reqs and scope. |
|
|
Term
| The 5 Tasks in the Req Mgmt and Comm knowledge area are: |
|
Definition
STaR PC
S - Solution Scope and Req (Manage)
T - Tracability (Manage)
R - Re-Use (Maintain)
P - Package (Prepare)
C - Communicate |
|
|
Term
| Managing the Scope and the Requirements will help you to: (2) |
|
Definition
1 - Secure approval from Stakeholders
2 - Use the scope as a guage to define req and manage issues as they surface |
|
|
Term
| What Inputs do you need to manage the scope and the reqs? |
|
Definition
uSSR2
S - Soln Scope
S - SH List (those who will review and approve)
R - Req
R - Req Mgmt Plan |
|
|
Term
| What output results from managing the soln scope and the reqs? |
|
Definition
R(A)
Reqs (Approved) -- that can be used for implementation |
|
|
Term
| What should you consider when managing soln scope and reqs? (4) |
|
Definition
1 - Mng Soln scope - Are all of the reqs w/in the scope?
2 - Mng Confliscts/issues - Are there any inconsistent reqs or differences in the way SHs view the reqs?
3 - Present for review - How to present reqs to SHs to acheive the right level of understanding
4 - Get appoval - What should the approval strategy be? |
|
|
Term
|
Definition
| The freezing of the current version and tracking subsequent changes going forward |
|
|
Term
| What technique could be used to manage soln scope and reqs? |
|
Definition
| "Problem tracking" (9.20) |
|
|
Term
| What does managing the req tracability help you do? (2) |
|
Definition
1 - Establish and maintain relationaships btwn bus objectives and reqs, other team deliverables, and soln components.
2 - Ensure nothing gets left out |
|
|
Term
| What inputs do you need to manage Req Traceability? |
|
Definition
RR
R - Req
R - Req Mgmt Plan (traceability level and tools) |
|
|
Term
| What output results from req traceability? |
|
Definition
R(T)
Reqs (Traced) - clearly defined relationships. easy to define effect on each other |
|
|
Term
| What should you consider when tracing reqs? (3) |
|
Definition
| 1 - Understand relationships -- what are the dependencies btwn reqs? 2 - Analyze impact - what is the impact of change? 3 - Specialized Configuration Mgmt Tool -- How to trace a large number of reqs |
|
|
Term
| What are the 5 relationships in req traceability? |
|
Definition
NESt CoVer
N - Necessity
E - Effort
S - Subset
C - Cover
V - Value |
|
|
Term
| What technique could you use to manage req traceability? |
|
Definition
| "coverage matrix" (only when reqs are few) |
|
|
Term
| The task of maintaining reqs for re-use will help you to: (3) |
|
Definition
1 - ID reqs that could be used again
2 - Recognize all the use cases for the re-use of reqs
3 - save time for efforts that have similar needs |
|
|
Term
| What inputs do you need in order to maintain reqs for re-use? |
|
Definition
ROpe
R - Reqs
O - OPAs Org Process Assets |
|
|
Term
| What output is produced by maintaining reqs for re-use? |
|
Definition
R (MR)
Reqs (Maintained and Re-useable) (documentation) |
|
|
Term
| What should you consider when maintaining reqs for re-use? (2) |
|
Definition
1 - ongoing reqs - determine what reqs are needed on a continual basis
2 - satisfied reqs - will SHs need certain reqs in future releases as well? |
|
|
Term
| What techniques could you use to maintain reqs for re-use? |
|
Definition
The BABOK does NOT recommend any...
*None* |
|
|
Term
| What does the task of preparing the reqs package help you do? (2) |
|
Definition
1 - ask the right questions and assess the best way to package the reqs
2 - prepare a pkg that aligns well with the SHs |
|
|
Term
| What inputs do you need to prepare the reqs package? |
|
Definition
ROCkS
R - Reqs
O - OPAs Org Process Assets
C - Comm Plan (What format did they want the package in?)
S - Structure Reqd (per the BRD) |
|
|
Term
| What output results from preparing the reqs package? |
|
Definition
RP
a Reqs Package that contains documented reqs and/or presentations for SH review |
|
|
Term
| What should you consider when preparing the reqs package? (2) |
|
Definition
1 - work products and deliverables - which outputs should be produced during BA work?
2 - format and structure |
|
|
Term
| What technique could you use to prepare the reqs package? |
|
Definition
|
|
Term
| The task of communicating the reqs will help you to: (3) |
|
Definition
1 - Create an ongoing dialog about the reqs which leads to understanding and approval
2 - Recognize the formal and informal ways to communicate reqs.
3 - Prevent last minute surprises |
|
|
Term
| What inputs do you need to communicate the reqs? |
|
Definition
Review on PC
R - Reqs
P - Package/Presentation
C - Comm Plan (BA) |
|
|
Term
| What output results from communicating reqs? |
|
Definition
CR
Communicated Reqs - common understanding among SHs at a given point in time. |
|
|
Term
| What should you consider when communicating reqs? (2) |
|
Definition
1 - general communication - are we informing SHs of progress with regular updates
2 - presentations - what is the best way? |
|
|
Term
| What techniques could you use to communicate reqs? (2) |
|
Definition
1 - Req Workshops (9.23)
2 - Structured Walkthroughs (9.30) |
|
|
Term
| The technique that is used to help familiarize the project team with the existing soln scope is: |
|
Definition
|
|
Term
| What would NOT be a good formal document for requirements? |
|
Definition
|
|
