Chapter 4 - The business analyst ( Essential analyst skills (Facilitation…
Chapter 4 - The business analyst
The business analyst's tasks
Lead requirements validation
facilitate requirements priortization
Identify project stakeholders and user classes
Plan the requirements approach
Define business requirements
The making of a business analyst
The fomer developer
The fomer (or concurrent) project manager
The fomer user
The subject master expert
The business analyst role
Essential analyst skills
The ability to facilitate requirements discussions and elicitation workshops is a vital analyst capability.
Facilitation is the act of leading a group towards success.
Facilitation is essential when collaboratively defining requirements, prioritizing needs, and resolving conflicts.
A strong analyst can influence a group of stakeholders to move in a certain direction to accomplish a common goal.
Leadership requires understanding a variety of techniques to negotiate agreements among project stakeholders, resolve conflicts, and make decisions
System thinking skills
Why does BA need to Organizational?
BAs must contend with a vast array of jumbled information gathered during elicitation and analysis.
Coping with rapidly changing information and structuring all the bits into a coherent whole demands exceptional organizational skills and the patience and tenacity to make sense from ambiguity and disarray.
As an analyst, you need to be able to set up an information architecturevto support the project information as it grows throughout the project
Thinking on your feet
Business analysts always need to be aware of the existing information and to process new information against it.
They need to spot contradictions, uncertainty, vagueness, and assumptions so they can discuss them in the moment if appropriate.
and similar diagrams
Data flow diagram
When are these model useful?
communicating with developers
help the BA improve the requirements
communicating with users
Interviewing and questioning skills
An analyst should feel comfortable talking with individuals in diverse job functions and at all levels of the organization.
A BA should speak the language of the audience she is talking to, not using technical jargon with business stakeholders.
Analysts must be able to get people with competing interests to work together as a team
The BA is not merely a scribe who records whatever customers say.
The best analysts invent potential requirements for customers to consider
They conceive innovative product capabilities, imagine new markets and business opportunities, and think of ways to surprise and delight their customers.
Essential analyst knowleadge
The analyst roles on Agile project
to document the
, including whether story cards or more formal tools are most appropriate.
that stakeholders are talking to one another frequently about requirements needs, questions, and concerns.
is at the right level: not too little and not too much. (Many BAs tend to
in specifications to the nth degree. Some purists suggest agile projects should have little or no requirements documentation. Neither extreme is ideal.)
that customer needs are accurately represented in the
, and facilitate backlog prioritization.
process and adapt it as the project warrants.
change their minds
requirements and priorities
help record those changes
the rest of the team
to determine the
impact of changes
on iteration contents and release plans.
Creating a collaborative team