Effective requirement gathering using Design Thinking technique

EFFECTIVE
REQUIREMENT
GATHERING
USING DESIGN
THINKING TECHNIQUES
ARJUN GHOSH

WHATIS“EFFECTIVE”
REQUIREMENTGATHERING?

EFFECTIVE REQUIREMENTS GATHERING
Copyright © 2018 Accenture. All rights reserved. 3
Getting the
information right is
very important for
successful
development of a
software product per
client’s end vision.
With the advent of Agile
and its short iterative
process, many started to
neglect this important
stage.
Hasty or poor gathering
of requirements leads to
poor quality and an
ineffective backlog of
epics/user stories,
preventing good
product road-map.

HOWDOYOUACCOMPLISH
“EFFECTIVE”REQUIREMENT
GATHERING?

DIFFERENT WAYS OF ANALYZING
REQUIREMENTS
WHAT ARE THE
DIFFERENT WAYS OF
ANALYZING AN
REQUIREMENT
EFFECTIVELY?
USING DESIGN THINKING
TECHNIQUES, ONE CAN
ANALYZE THE CURRENT
“AS-IS” STATE FOR A
PROJECT, TO HELP
IDENTIFY THE GAPS AND
GATHER FINDINGS & NEW
REQUIREMENTS, FOR
ROBUST SOFTWARE
DEVELOPMENT.

WHAT IS DESIGN THINKING?
Design
Thinking
Creative
Strategies
Designing
Product
Challenge
Assumptions
Iterative
Process
Solution
based
Approach
Human
Centered
1. Creative strategies used during
product design
2. A focus on human-centered
products, services and processes
3. An iterative process to understand the
audience, challenges and problems
4. Solution-based approach to problem
solving

OUR APPROACH TO DESIGN THINKING
Learn about
people and the
context of the
problem.
Synthesize
learnings from
discovery and
point of view.
Ideate
iteratively—
prototyping
cycles.
Test ideas
and
prototypes
with actual
users.
Deploy the
chosen
solution and
refine it.

DESIGN THINKING + AGILE
Agile SPRINTDescribeDiscover ImplementTest
IDEATE
PROTOTYPE
SPRINT 0 BUILD / DEPLOY

DESIGN THINKING TECHNIQUES
Requirements gathering and product refinement phases
techniques
1. Territory maps
2. Customer interviews
3. Customer journey
4. Affiliation clustering

Essentially, a Territory Map is used to
identify, who/what are the main users
of a system and interaction between
those users and their environment.
Grouping the related items along with
the environment context for insights
into the system
TECHNIQUE 1: TERRITORY MAPS

“Interview Sessions” are the most
common technique for requirement
elicitation, where a series of interviews
are held with various stakeholders in a
process to change or affect.
Questions can be “Open Ended” and
“Close Ended”.
Ask “Why,” and be an Active Listener.
TECHNIQUE 2: CUSTOMER INTERVIEWS

“Customer Journey” map is a
visualization of the process that a
person goes through in a process,
to complete an objective or get a
desired result.
This techniques allows customer to
quickly evaluate, where in the
process, are the different
challenges.
TECHNIQUE 3: CUSTOMER JOURNEY

“Affinity Clustering” organizes a large
quantity of information by natural
relationships.
This allows customers to visually
group all the logically related
components in system.
Generally colored post-its are used in
these sessions.
TECHNIQUE 4: AFFINITY CLUSTERING

CASESTUDY
ALARGEUKFINANCIAL
INSTITUTION

FINANCIAL SERVICES COMPANY
CASE STUDY
BUSINESS BENEFITS
• Increased efficiency in the company’s
entire requirements gathering
process.
• 1-2 months process duration reduced
to nearly 15-20 days.
• 40%-60% efficiency increase over
their current process, with time-saving
and cost-saving.
• Detailed, precise and effective
requirements backlog creation.
• Developed a better product vision
road-map and increased ROI from the
end product.
OUR SOLUTION
Successfully introduced Accenture
prescribed Agile Design Thinking
methodology in the company’s
requirements gathering process.
This innovation into the current process
increased the efficiency and
effectiveness.
During the Discovery and Describe
phases of the requirements gathering
process, Design Thinking tools and
techniques were used, including
customer journeys and territory maps.
THE PROBLEM
A Financial Services company required a
fast but effective requirement elicitation,
to move forward with future forecasting
and product road-map.
Current process had following
deficiencies:
• Was not time-efficient.
• Process output was not effective or
usable.
• Long and laborious process, taking 1-
2 months of duration, at every change
request.

THANK YOU!
For more questions, you can contact,
Arjun Ghosh
Enterprise Agile Coach
& Transformation Coach
Disclaimer*: This Presentation has been published for information and illustrative purposes only and is
not intended to serve as advice of any nature whatsoever. The information contained and the
references made in this Presentation is in good faith and neither Accenture nor any its directors, agents
or employees give any warranty of accuracy (whether expressed or implied), nor accepts any liability as
a result of reliance upon the content including (but not limited) information, advice, statement
or opinion contained in this Presentation. This Presentation also contains certain information available
in public domain, created and maintained by private and public organizations. Accenture does not
control or guarantee the accuracy, relevance, timelines or completeness of such information. Accenture
does not warrant or solicit any kind of act or omission based on this Presentation . The Presentation is
the property of Accenture and its affiliates and Accenture be the holder of the copyright or any
intellectual property over the Presentation. No part of this document may be reproduced in any manner
without the written permission of Accenture. Opinions expressed herein are subject to change
arjun.b.ghosh@acccenture.com

➢ https://www.interaction-design.org/literature/article/what-is-design-
thinking-and-why-is-it-so-popular
➢ https://www.ideou.com/blogs/inspiration/what-is-design-thinking
➢ http://www.businessballs.com/business-process-modelling.htm
➢ https://www.fastcompany.com/919258/design-thinking-what
➢ https://confluence.cornell.edu/display/BAF/Elicitation+Techniques#Elicitatio
nTechniques-Interview
➢ https://businessanalystlearnings.com/ba-techniques/2013/7/18/interviews-
requirements-elicitation-technique
REFERENCES

Effective requirement gathering using Design Thinking technique

More Related Content

What's hot

Similar to Effective requirement gathering using Design Thinking technique

Recently uploaded

Effective requirement gathering using Design Thinking technique