What if we can NEVER specify a requirement precisely enough that there won’t be this kind of ambiguity?

Maybe the problem is that we’re just afraid to talk to each other…

Traditional Requirements Analysis

User Story Aspects

Card Conversation Confirmation

Life Cycle of an Agile User Story

As a nurse, I want to have to enter my password before seeing patient data, so that we don’t disclose patient information to unauthorized users.

As a <role>I want <feature>So that <business value>

Independent Negotiable Valuable Estimable Small Testable

INVEST in User Stories

Story Points◦ Size matters, not duration◦ Story points are relative◦ Size can be based on several factors

Ideal Days

Estimating Stories in Agile

T-Shirt Sizing (S, M, L)

Exponential (1, 2, 4, 8)

Fibonacci series (1, 2, 3, 5, 8)

Business understands that 8 is much bigger than 1 as opposed to a linear scale.

Assigning Story Points

1 – Rhode Island8 – Texas2 – Ohio3 – Nebraska5 – Nevada3 / 5 - Oregon

Relative Sizing

Moderator: Reads Story Description

Ask moderator questions

Pick estimate card

Show cards simultaneously

Discuss Low / High estimates

Consensus (OR Pessimist wins!)

No bluffing

Planning Poker in Agile

As a Customer,

I want to log out

1

As a Marketing Manager,

I want to display the top 5 Books that are on special every week,

So that I can promote company sales offers8

As a Customer,

I want to add a book to my Shopping Cart

As a Sales Manager,

I want to see the number of orders completed per month,

So that I can track online sales numbers

As a Customer,

I want to search for a book by title,

So that I can find a book quickly online

As a Customer,

I want to store my credit card online,

So that I can make multiple purchases quickly

As a Customer,

I want to fill in a Suggestion Form

So that I can leave feedback for the vendors

As a Customer,

I want to delete a book from my Shopping Cart

So that I can remove unwanted items from my cart

Daily Iteration Release

Planning

Yesterday’s weather

Commitment-driven- Add story one-by-one till team cannot commit to

more

Iteration Planning

Acceptance CriteriaGiven I am logged in as a user in the administrator role And There are 3 vendors When I go to the manage vendors page Then I should see the first 3 vendor names

Given /there are (\d+) vendors/i do |n|

Vendor.transaction do

Vendor.destroy_all

n.to_i.times do |n|

Factory.create(:vendor, :business_name => "Vendor #{n}")

end

end

end