A. understand sign-off authority.
B. gain project support.
C. process the feedback accurately.
D. identify risk tolerance levels.
A. Mind map
B. Use case
C. Item tracking
D. Expert judgement
A. Priority
B. Stability
C. Urgency
D. Complexity
A. Define design options
B. Define requirements architecture
C. Analyze potential value and recommend solution
D. Specify and model requirements
A. Conduct elicitation
B. Confirm elicitation results
C. Manage stakeholder collaboration
D. Communicate business analysis information
A. Requirements at low levels of abstraction
B. Requirements without direct ties to a particular tool
C. Requirements expressed in more detail
D. Requirements with specific references to departments
A. Visual thinking
B. Conceptual thinking
C. Creative thinking
D. Systems thinking
A. Scope creep
B. Resource shortfalls
C. Inaccurate cost estimated
D. Delayed approvals
A. penalty.
B. benefit.
C. stability.
D. dependency.
A. Operational Support
B. Domain subject matter experts
C. Sponsor
D. Project Manager
