Download as pdf or txt
Download as pdf or txt
You are on page 1of 46

‫هتخرج بإيه من السيشن دي؟‬

Requirements Gathering
Design Proposal
Agenda:

Discovery phase

Activities Of Discovery

Outcomes
1
What is Discovery Phase?
What is the discovery phase?

• Discovery or scoping phase is a process of


collecting and analyzing information about the
project, its intended market, audience to be able
to start implementation and solution creation.

• Depending on the project’s scope, the discovery


phase time can be determined.
Main Goal Of Discovery Phase

New Project Project Revamp

Define the real problem the Define the problems the current
product should solve with making product faces with its target users
sure of the right audience. then explore possible solutions.
‫طب هل املراحل دي الزم‬
‫ننفذها في كل مشروع؟‬
Expectation VS Real world
Important factors

• Scope clarity

• Risk

• Time & Budget

• Resources

• Experience
Any
questions?
2
Discovery Phase Activities
Discovery phase skeleton

Requirements gathering Problem & Users Market


& Scoping understanding understanding

• Industry research.
• Primary research. • Secondary research.
• Stakeholder interviews

• Problem statement
• Competition analysis report
• Project proposal
• User persona
We have a
Good morning
meeting in an hour
1. Initial
research
1. Initial Research
Overview:

• It’s normal to be unaware of an industry so


this activity can help you stay prepared.

• Market research helps find the strengths and


weaknesses of the existing solutions.

• At this stage you don’t have to create a report,


it’s just a quick research to be on the same page.
1. Initial Research
Tips:

• For mobile app: use apple/play story as a


powerful tool to search competitors.

• For websites: use the best fit search words to get


the best results.

• Write the results into small bullet points to guide


you through the journey.
1. Initial Market Research
Real examples:
1. Initial Market Research
Real examples:
1. Initial Market Research
Real examples:

Get your ideas out in


a simple&quick mind
mapping.
Let’s Practice Together!
1. Search the industry.
2. Extract the main modules
Let’s have a break
2. Stakeholder
interview
2. Stakeholder Interview
Overview:

• The most important and essential activity in the


project as the stakeholders can be always a
game changer.

• The main goal is to understand the product


vision and try to frame the main problem they
face in business or the user faces.
2. Stakeholder Interview
Pre-interview Tips:

•Preparing for a meeting can help you limit the


discussion and ask the right questions.

• Do a quick research about the industry so that


you can be aligned with what they’ll say.

• Prepare the needed questions you want to ask in


a predefined agenda this can keep the meeting
productive.

• Try to start the meeting 5 mins before and check


the tool if it’s new to try.
2. Stakeholder Interview
Meeting Agenda:

• Introduction

• The general brief the project

• The project type ( from scratch - revamp)

• The main problems

• The user roles and modules

• The main competitors.

• The project success measurement

• The next steps


2. Stakeholder Interview
Interview Tips:

• Start with your agenda and the reason behind


the interview to get everyone aligned.

• Try to validate what you hear from the client.

• Summarize the client’s points before moving into


the next idea (if necessary).

• Write small notes / ask to record the meeting.

• Ask about any important documents that can


help you understand more about the industry.
2. Stakeholder Interview
After meeting:

• Prepare and send the minutes of meeting


including the next steps.
Any
questions?
3
Discovery Phase Outcomes
1. Requirements analysis:

• Gather all the insights you found valuable


from searching competitors into simple bullet
points or a mind map.

• This can be a powerful reference in your


upcoming discussions.

• This can include information about industry,


users, stakeholders, and competitors.
2. The project scope of
requirements:

• It should include all functional and non-


functional requirements, detailed and
prioritized.

• It’ll also include the user stories from


both user and business perspectives.

• It’ll also include the plan for MVP


features and future ones.

• Finally the team can estimate the time


and money for the project.
What is a user story?
User stories
Example of
real product
template
Let’s Practice Together!

Create user stories by yourself


Any
questions?
Important Articles

• The Discovery Phase in UX Projects

• Writing the perfect problem statement

• Problem Statements in UX Discovery

• UX: Creating Proto-Personas

• Three persona types

• UX workshops
Helpful Tools

•Whimsical

• Miro

• Figjam
Thank You!

You might also like