Embed Size (px)
Citation preview
Stop Gathering Requirements
Presenter:Steve Blais, PMP, PMI‐PBAAuthor, Consultant, Teacher and Coach
2
Presenter: Steve Blais, PMP, PMI-PBA
50 years of experience and IT and IT management Provides B/A consulting services around the
world Author of the book: Business Analysis: Best
Practices for Success, John Wiley, 2011 Co‐author of the Book Business Analysis for
Practitioners: a Practice Guide, PMI, 2014 Member of the steering committee for the
Business Analysis Body of Knowledge, version 3, IIBA, 2015
Frequent contributor of articles for Modern Analyst, including the series of Doctor BA articles
3
Sound Familiar?
The people you want in the elicitation meeting don’t show up
Stakeholders in conflict about requirements and what they mean
Can’t get requirements prioritized Stakeholders keep putting off the final sign‐off Missing pieces of the solution Hours in requirements review debating the wording
or order Stakeholders refuse to prioritize the requirements or
give them all equal weight
4
“Gathering” Requirements
4
Find out what they want
5
“Gathering” Requirements
5
Find out what they want
Just gather the requirements.How hard can
that be?
6
“Gathering” Requirements
6
Find out what they want
We have to finish the code: Go get the requirements
Just gather the requirements.How hard can
that be?
7
Four Steps to “Gather Requirements“
1. Business community gives you requirementsWhich you copy exactly as they are given to you
2. Format requirements into requirements document With some editing and organization
3. Confirm what you wroteWith those you gave them to you
4. Give it to the solution team
7
8
What’s Wrong with That?
Who is responsible for the requirements?No need for in‐depth discussions or explanationsNeed to go back to get answersReplaced by Agile or a machineI don't get no respect
8
9
What’s Wrong with That?
Who is responsible for the requirements?No need for in‐depth discussions or explanationsNeed to go back to get answersReplaced by Agile or a machineI don't get no respect
9
10
They don’t Want requirements
Don’t have the time Don’t really know what to say Forced into the situation Not really the SME
10
11
They don’t Want requirements
Don’t have the time Don’t really know what to say Forced into the situation Not really the SME
11
12
What do they want?
The business analyst’s job Define solutions Define what is needed by the business to implement the selected solution
12
13
Don’t have a clue?
They don’t know what they want Your job is to help them understand the problem and realize what they want • Offering options and choices• Developing solutions and alternatives• Suggesting improvements and enhancements• Increasing the value of the business
13
14
What to do Instead…
14
Gather information Confirm the information Analyze the information Confirm the analysis
15
What to do Instead…
15
Requirements don’t exist until the business analyst analyzes them
into existence
Gather information Confirm the information Analyze the information Confirm the analysis
16
In Other Words…
Gather information about the business problem domain Analyze the information to define the real business
problem Gather information about the business problem:
circumstances, conditions, consequences Analyze the information to define solutions to the
problem Present solutions to the business Gather information about the selected solution Pass the details of the solution to the solution team:
These are the requirements
16
18
Questions Slide
Questions?
![COIN LAUNDRY WORLD & CAFE GATHER WHILE YOU … · COIN LAUNDRY WORLD & CAFE GATHER WHILE YOU NEIGHBORS CAFE], 139 H SOUR oÉFEE SWEETS CAFE Share with Sooo Liquid / r have a n-ce](https://img.pdfslide.net/doc/110x75/5ad76b3f7f8b9a9d5c8c0e4f/coin-laundry-world-cafe-gather-while-you-laundry-world-cafe-gather-while-you.jpg)
