design thinking for requirements analysis - ba … · - design thinking (req)t-requirements...

© 2016 BA Convention

Mastek approach to applying Design Thinking for Requirement Analysis in the Digital Era - By Kavita Desai (Lead BA CoE ) - Parag Nemade (Associate Business Consultant)

Design Thinking for Requirements Analysis

© 2016 BA Convention 2

Click to edit Master text styles

Click to edit header

Agenda

• Why Design Thinking ?

• Mastek’s approach for applying Design Thinking to

Requirements Analysis

• Case Study




Key Takeaways

• A step by step approach for applying Design Thinking

principles to Requirements Analysis

• Techniques and tips for applying this approach to your

projects

• How to use this approach in Agile projects too




The Digital Disruption

• 10X the

innovators

• 1/10 the cost

• 100X the power

Source :” The Digital Disruptor's Handbook” Forrester




How do we Bridge the Gap?

• Simple

• Convenient

• Frictionless

Customer Expectations

• Process Centric

• Real end user

needs missed

• Limited Scope

for Innovation

Existing Approaches




The Realisation : An Unified Approach

• Technology

• Automation

• Emotion

• Empathy

• Creativity




D(Req)T way out !!

D(Req)T

/dɪˈɹɛkt/, /daɪˈɹɛkt/, /dəˈɹɛkt/

D - Design Thinking

(Req)T- Requirements Analysis in a time

bound manner.

A Requirements Analysis approach for the

digital era that applies principles of

design thinking to best practices of

requirements analysis to create user

centric & innovative solutions and

systems.(leveraging Stanford's design thinking templates)




Business Foundation

1.Clarify Context

2.Understand and

Empathize

3.Ideate Innovate and

Prototype 4.Build & Test

Design Thinking and the D(Req)T Approach

The D(Req)T Approach

Empathize Define Ideate Prototype Test

* Courtesy: Stanford Design School




Evolution of D(Req)T

4 Billion GBP pa

1000+ Colleges

2 million apprentic

eships

50% increase by 2020

Right Skills

High Quality

Apprenticeship funding

“Digital First” for

Employer Ownership

• Understand diverse Employer

needs and attitudes

• Encourage participation and

Ownership amongst the

employers

The Challenge




D(Req)T Step 1. Clarify the context

• What is the Vision of the project?

• Who are my target users?

• What are the needs?

• What are the top features of the

application?

• How will it meet business value?

• How will I measure the success?

Visioning Workshop : Create Vision Board

Vision Board Snap Shot




D(Req)T Step 1. The Output :Vision Board

• Articulate features

• Clarity on target users

• Articulated Value

– Better quality, responsive apprentices

– Improved employer satisfaction and engagement

– More employers take on apprenticeships

Tips

• Keep it Simple

• Use the Whiteboard/ Wall

• Simple Diagrams and mock ups

• Display the Vision Board in a prominent place in

the Design thinking room




D(Req)T Step 2.Understand and Empathize

2.1.Collect Data

2.2 Group Data

2.3.Define Persona

2.4.Refine Personas




2.1 Collecting Data

* Courtesy : Stanford design School

• Capture Behaviors , Assumptions &

• Expectations

• Capture Pictures of work place

• Interview with Empathy (Empathy Maps)

Insights and Observations Say

Do

Think

Feel

Empathy Map Template




2.2 Group the Data

• Groups based on Goals, Needs,

Problems, Thinking

• Demography, type of user, technology

they use, how comfortable they are etc.

• Separate the fluff from relevant

information.

Tips

• Identifying Focus vs Accuracy

• Perspective of Differences

• If in doubt : Refer Target users

on Vision board




2.3 Create Personas

• Classify, Name, Relate

• Identify characteristics

• Relate to target users

• Keep it real




2.4 Refine the Personas

• Brainstorm to refine understanding

• Create & display posters

• Share with as many colleagues

• Bring them to life




D(Req)T Step 2 : The Output

• Refined Personas

• User needs based on personas

• Persona based prioritization

• Key User Needs emerged

– Easy Access

– Understanding the funding

– Clarity about the actual costs

• High Volume group

Deprioritized

Activities owned by employer Yes/No




D(Req)T Step 3.Ideate,Innovate and Prototype

• Brainstorm to ideate on each persona and needs

• Create User Journeys

• Encourage innovative ideas

• Prototypes with just enough details for feedback

• Seek Feedback “I like, I wish, What if..?” ( Stanford approach)

What If ” I could compare provider costs

I Wish “I could get easy help to resolve funding

queries”

I Like that “I am able to

see the fund split”




D(Req)T Step 3 :The Outputs

User Journey Prototype




D(Req)T Step 4.Build and Test

• Enhance proto type

• Continuous interaction with user groups for feedback

• Testing from User perspective and not “Tester” perspective

• “Real Feedback” and buy in




D(Req)T helps bridge the gap!

D(Req)T

• Understand Real End User Needs

• Capture User Centric requirements

• Create Opportunities for Innovation

• Requirement Approach for the Digital Era




Any Questions ?

Thank You

design thinking for requirements analysis - ba … · - design thinking (req)t-requirements...

Documents