BABOK_Guide_v3_member_copy

Techniques
Stakeholder List, Map, or Personas
Figure 10.43.3: RACI Matrix
Change Request Process
RACI
Executive Sponsor
Business Analyst
Project Manager
Developer
Tester
Trainer
Application Architect
Data Modeller
Database Analyst (DBA)
Infrastructure Analyst
Business Architect
Information Architect
Solution Owner
Subject Matter Expert (SME)
Other Stakeholders
.4 Personas
A
R
C
C
I
I
C
C
C
C
R
C
C
C
R C I
(varies)
A persona is defined as a fictional character or archetype that exemplifies the way
a typical user interacts with a product. Personas are helpful when there is a desire
to understand the needs held by a group or class of users. Although the user
groups are fictional, they are built to represent actual users. Research is
conducted to understand the user group, and the personas are then created
based upon knowledge rather than opinion. A number of elicitation techniques
can be utilized to conduct this research. Interviews and surveys/questionnaires are
two techniques commonly used to elicit this information. The persona is written
in narrative form and focuses on providing insight into the goals of the group.
This allows the reader to see the story from the point of view of the stakeholder
group. Personas help bring the user to life, which in turn makes the needs feel
real to those who design and build solutions.
Complimentary IIBA® Member Copy. Not for Distribution or Resale.
10.43.4 Usage Considerations
.1 Strengths
• Identifies the specific people who must be engaged in requirements elicitation
activities.
• Helps the business analyst plan collaboration, communication, and facilitation
activities to engage all stakeholder groups.
• Useful to understand changes in impacted groups over time.
347