user-story, requirements and other scary words: guide for junior project manager

16
THINK OUTSIDE THE CODE THINK SOLUTIONS TRUST SOURCING “USER-STORY, REQUIREMENTS AND OTHER SCARY WORDS”

Upload: trust-sourcing

Post on 24-Jan-2017

203 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

THINK OUTSIDE THE CODETHINK SOLUTIONS

TRUST SOURCING

“USER-STORY, REQUIREMENTS AND OTHER

SCARY WORDS”

Page 2: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

www.trustsourcing.com

ABOUT US!

Page 3: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

FFP

Page 4: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

Clients Are from Mars, Developers Are from Venus

Product Life Cycle (Advanced)

Page 5: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

Clients Are from Mars, Developers Are from Venus

Enough for today

Page 6: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

What language client speaks

• “I Saw Once…”• “Just Like This, but

better”• “It Should work faster

than previous”• “Should work

everywhere” • …

Frequently Said Phrases

Page 7: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

What language client speaks

Cash oriented Thinking

Page 8: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

What language Developers speaks

Frequently Asked Questions

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?

Page 9: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

What language Developers speaks

Code Oriented Thinking

Page 10: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

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

Page 11: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

Let’s translate!

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

Page 12: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

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

Page 13: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

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

Page 14: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

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

Page 15: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

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

Page 16: USER-STORY, REQUIREMENTS and other scary words: Guide for Junior Project Manager

Lets rock!

TRUST SOURCING