Scribd
Upload
8 views10 pages

Chapter 4 1

The chapter discusses the role of the business analyst, including their key tasks and essential skills. It outlines the skills needed such as communication, analytical thinking, and facilitation. Additionally, it explores the backgrounds that often lead to becoming an analyst and how they function on agile project teams. The role of the analyst is to define, analyze, document and communicate requirements while facilitating collaboration between stakeholders.

Uploaded by

ducvip9a2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
8 views10 pages

Chapter 4 1

The chapter discusses the role of the business analyst, including their key tasks and essential skills. It outlines the skills needed such as communication, analytical thinking, and facilitation. Additionally, it explores the backgrounds that often lead to becoming an analyst and how they function on agile project teams. The role of the analyst is to define, analyze, document and communicate requirements while facilitating collaboration between stakeholders.

Uploaded by

ducvip9a2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

CHAPTER 4

The business analyst


Objectives

• Enhancing:
–the vital functions the BA performs
–the skills and knowledge an effective analyst needs
–how to develop such people in organization
–proposes a job description for a requirements
analyst, and you can also access a sample BA job
description
Contents

1. The business analyst role


2. The business analyst’s tasks
3. Essential analyst skills
4. Essential analyst knowledge
5. The making of a business analyst
6. The analyst role on agile projects
7. Creating a collaborative team
The business analyst role
The business analyst’s tasks

• Define business requirements


• Plan the requirements approach
• Identify project stakeholders and user classes
• Elicit requirements
• Analyze requirements
• Document requirements
• Communicate requirements
• Lead requirements validation
• Facilitate requirements prioritization
• Manage requirements
Essential analyst skills

• Listening skills • Leadership skills


• Interviewing and • Observational skills
questioning skills • Communication skills
• Thinking on your feet • Organizational skills
• Analytical skills • Modeling skills
• Systems thinking skills • Interpersonal skills
• Learning skills • Creativity
• Facilitation skills
Essential analyst skills

• Thinking on your feet


1.Relax.
2.Listen.
3.Have the question prepared.
4.Use stall tactics (Repeat the question yourself, Narrow
the focus, Ask for clarification, Ask for a definition)
5.Use silence to your advantage.
6.Stick to one point.
7.Prepare some "what ifs."
8.Practice clear delivery.
9.Summarize and stop.
Essential analyst knowledge
• need a breadth of knowledge, much of which is gained through
experience.
• need to understand contemporary requirements engineering practices
and how to apply them in the context of various software development
life cycles.
• need to educate and persuade those who are not familiar with
established requirements practices.
• the effective analyst has a rich tool kit of techniques available and knows
when—and when not—to use each one.
• understanding of project management, development life cycles, risk
management, and quality engineering
• analyst can minimize miscommunications with users
• understand the organization and business domains often detect
unstated assumptions and implicit requirements
• suggest ways that users could improve their business processes or
propose valuable functionality that no other stakeholder thought of
The making of a business analyst

• The former user


• The former developer or tester
• The former (or concurrent) project manager
• The subject matter expert
• The rookie
The analyst role on agile projects
• Define a lightweight, flexible requirements process and adapt it as the
project warrants.
• Ensure that requirements documentation is at the right level: not too
little and not too much
• Help determine the best approach to document the backlog, including
whether story cards or more formal tools are most appropriate.
• Apply facilitation and leadership skills to ensure that stakeholders are
talking to one another frequently about requirements needs,
questions, and concerns.
• Help validate that customer needs are accurately represented in the
product backlog, and facilitate backlog prioritization
• Work with customers when they change their minds about
requirements and priorities, and help record those changes.
• Work with the rest of the team to determine the impact of changes on
iteration contents and release plans

You might also like