Stakeholders

Plan Business Analysis Activities i.e.

determine activities required to define
Approved Requirements Manage Solution and Requirements Scope the solution to the business problem,
how those activities will be carried out,
Decision Record
the work effort involved, and an estimate
of how long the activities will take. Plan
Forward Tracing Requirements for Analysis, Elicitation, Requirements
Analysis. Solution Assessment and
Backward Tracing Requirements Validation, Requirements Management
Manage Requirements Traceability
and Communication
Impact Analysis due to change in
Requirements Business Analysis Planning and Monitoring
Communication format: Information
to be sent to the various Stakeholders,
Custodian/Librarian responsible for
Requirements to be maintained for reuse and the form of communication i.e.
maintaining requirements
Requirements Management and Verbal or Written
Business Requirements Document Communication
Requirements Management Process:
Determine "As Is" and who needs to be
Requirements Traceability
Interaction with all stakeholders before, informed of changes to requirements
during and after projects. Necessary NOT actual approval of requirements
documentation attached
Project Status Update: T rack, access
and report on work done, and take steps
Requirements Communication to identify/determine corrective action to
Interaction with solution team to assure outstanding issues
that requirements are correctly
understood and implemented. Necessary
documentation attached
Internal: Define/refine current/future business
architecture.
Identify Business Need Assess the current state of technology
Solution Design Assessment to Determine to fully define the (infrastructure and applications)
if solution best fits the business need, identify business Problem/
gaps and shortcomings in solutions (If any), Opportunity
and determine necessary workarounds or External:
changes to the solution Benchmark analysis
Competitive studies
Requirements Allocation:
Requirements allocated among releases
and/or solutions components. Solution Approach:
PROJECT Identify potential solutions, analyze
feasibility of options, recommend viable
SOLUTION ASSESSMENT AND business solution, and validate with
Organizational Readiness Assessment VALIDATION decision makers
ENTERPRISE ANALYSIS

Organizational Change Define Solution Scope

Recommendations

Validated Corrective Actions Project objectives and expected business

Solution Validation benefits i.e. Business Goal
Defect Impact Analysis

Solution Evaluation to determine if

original goals have been met
Develop the Business Case Project scope

Structured Requirements i.e. similar

requirements grouped together Evaluate risk

Prioritized requirements
Scheduled resources
Use Cases, Models or Diagrams to
Elicitation plan
Supporting Materials
Indicate Process Flow

Assumptions and Constraints to

REQUIREMENTS ANALYSIS
separate Stakeholder desires from Elicitation activity results
Actual needs

Stakeholder confirmation to verify Conduct Elicitation

requirements are correctly and Assumptions, constraints, risks, issues
ELICITATION
completely defined, and of acceptable observed during Elicitation
quality (Email/other documentation
confirming same attached)
Elicitation documentation e.g. Minutes of meeting
Requirements Validation: Determine Elicitation Activity Results i.e.
requirements satisfy Business Need Information provided by
Stakeholders

Validated Stated Requirements i.e.

Confirmed Elicitation results

H0NL60M4_Business-Analyst-Plan.mmap - 17/10/2011 - Mindjet