THINK OUTSIDE THE CODETHINK SOLUTIONS
TRUST SOURCING
“USER-STORY, REQUIREMENTS AND OTHER
SCARY WORDS”
What language client speaks
• “I Saw Once…”• “Just Like This, but
better”• “It Should work faster
than previous”• “Should work
everywhere” • …
Frequently Said Phrases
Cash oriented Thinking
What language Developers speaks
Frequently Asked Questions
Ok, I got it.
How is …? What I should do …?
How?
Who Will?
When?
What For?
Who?
Who can?
What For?
What Then?
How?
Who?
Which?
How?
How Many? Wha
t For
?
WHERE?What?Who?
Code Oriented Thinking
Let’s translate!
WTF Is going on? or how we should talk with customer
• Goals• Documentation• Questions• Mockup• Examples• Mind Maps• More questions• Read documentation again
and then ask new questions
Handle 3 years childor how we should talk with developers
• Prototypes (Axure RP,
Balsamiqs)• Use Cases• User Stories• Diagrams (Visio, draw.io,…)• Detailed requirements• Examples• Mockups• Mind Maps• whiteboard
Instruments
Prototype
• Display how it will work• Visualization of requirements• increased user involvement
Advantages:
Disadvantages
: • Insufficient analysis• Customer may think that this is real
product• It takes time
Instruments
User stories
• They are short and easy• Allows to determinate project• Good for “variable” project
Advantages:
Disadvantages
: • hidden expectations • Not so good for big projects• Not self-sufficient
Instruments
Use cases
• Allow to prioritize project• Allow to answer tricky questions• Allow to discover all users needs
Advantages:
Disadvantages
: • Bad for non-iteration based
requirements• Sometimes hard to show relationships
between use cases• You need experience to draw them
Instruments
Diagrams
• Excellent to discover hidden
expectations• Easy to calculate ETA• Bugs minimization
Advantages:
Disadvantages
: • It takes time• You have to understand what client
really want• You need experience to draw them