01.11.2017 Views

BABOK_Guide_v3_member_copy

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Plan Business Analysis Information Management<br />

Business Analysis Planning and Monitoring<br />

• Risks: identifies uncertain events that may impact requirements.<br />

• Source: identifies the origin of the requirement. The source is often<br />

consulted if the requirement changes or if more information regarding the<br />

requirement or the need that drove the requirement has to be obtained.<br />

• Stability: indicates the maturity of the requirement.<br />

• Status: indicates the state of the requirement, whether it is proposed,<br />

accepted, verified, postponed, cancelled, or implemented.<br />

• Urgency: indicates how soon the requirement is needed. It is usually only<br />

necessary to specify this separately from the priority when a deadline exists<br />

for implementation.<br />

Complimentary IIBA® Member Copy. Not for Distribution or Resale.<br />

3.4.5 <strong>Guide</strong>lines and Tools<br />

3.4.6 Techniques<br />

• Business Analysis Performance Assessment: provides results of previous<br />

assessments that should be reviewed and incorporated into all planning<br />

approaches.<br />

• Business Policies: define the limits within which decisions must be made. They<br />

may be described by regulations, contracts, agreements, warranties,<br />

certifications, or other legal obligations.<br />

• Information Management Tools: each organization uses some tools to store,<br />

retrieve, and share business analysis information. These may be as simple as a<br />

whiteboard, or as complex as a global wiki or robust requirements management<br />

tool.<br />

• Legal/Regulatory Information: describes legislative rules or regulations that<br />

must be followed, and helps determine how business analysis information will<br />

be managed.<br />

• Brainstorming: used to help stakeholders uncover their business analysis<br />

information management needs.<br />

• Interviews: used to help specific stakeholders uncover their business analysis<br />

information management needs.<br />

•Item Tracking: used to track issues with current information management<br />

processes.<br />

• Lessons Learned: used to create a source of information for analyzing<br />

approaches for efficiently managing business analysis information.<br />

• Mind Mapping: used to identify and categorize the kinds of information that<br />

need to be managed.<br />

• Process Modelling: used to document the process or method for managing<br />

business analysis information.<br />

46

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!