7
3 C’s & INVEST A Good User Story

A good user story

Embed Size (px)

Citation preview

Page 1: A good user story

3 C’s & INVEST

A Good User Story

Page 2: A good user story

User story in software development addresses the miscommunication between those who uses (user) the software and those who build (developers) it about what (value) the user wants.

Why user story?

As a <some role> – who?

I want do <some action> – what?

So that <some benefit> – why?

Page 3: A good user story

3 C’s of User Story

Card - A physical representation of what user wants in few simple plane statements.

Conversation – Details of story emerges when the developers talks with product owner and customer about who, what & why.

Confirmation – Objective of story identified after conversation in terms of acceptance criteria.

Page 4: A good user story

INVEST in User Story

I - IndependentN - Negotiable V - ValuableE- EstimableS - SmallT - Testable

Page 5: A good user story

INVEST in User Story

Independent - Helps in prioritizing the backlog.Negotiable - Evolves the customer’s need.Valuable - Places user story in the backlog. Estimable - Helps in to commit a user story. Small - Helps it in getting delivered in a sprint.Testable – Helps in getting it done.

Page 6: A good user story

A good User Story

3 C’s, INVEST -> User Story

A Good User Story