Scoping => SOW (Statement/Scope of Work)
Discovery
Inception
Development
Production
Maintenance
This is not waterfall! These phases often overlap and recur.
A story:
(*) chores and spikes do not directly provide business value, but improve knowledge or reduce debt or increase simplicty
Usually a given feature has one or more stories.
There are other types of stories and tasks...
(this diagram is from Pivotal Tracker but the workflow applies to most Agile processes and tools)
Story titles should be brief; story bodies should follow this pattern:
AS A ____ [role]
I WANT TO ____ [action]
SO THAT ____ [motivation]
Notes: * If you write "As a user" you're probably doing it wrong -- use a more specific role name instead * "I want to" should be an action, not just a desire
GIVEN ____ [precondition]
WHEN ____ [action]
THEN ____ [postcondition/assertion]
Title: Sign Out
Body: As a logged-in user at home, I want to sign out of the application, so that my other family members can't use my account
Acceptance Criteria:
Given I am signed in as a normal (non-admin) user
When I look at the nav bar
Then I see the "Sign Out" button
Given I am signed in as a normal user
When I click on the "Sign Out" button
Then I am returned to the home page
Given I am signed in as a normal user
When I click on the "Sign Out" button
Then I cannot view the "Edit Profile" page
Given I am not signed in
When I look at the nav bar
Then I do not see the "Sign Out" button
A backlog is a list of stories
that have been
☑ written,
☑ estimated,
☑ and prioritized
☑ in linear order
When writing stories, it is very tempting to skip one of these steps
e.g. :
so please try to treat the previous slide as a checklist, and push back if someone wants to skip a step, or do it out of order, or impatiently do several steps at once
The customer gets to say how soon; the coders get to say how hard
In general...
A point is not a promise of time, but is an estimate of effort
Points can also be awarded for complexity or risk or mystery
It’s up to the customer, BUT here are some guidelines:
Flowchart:
____________fix________
v \ /-> new feature
in-progress -> done -> accept/reject?
| \-> new bug
v
Done
The goal is for any coder to be able to work on any story (with help, if needed, from the right pair partner).
the more frequent they are, the shorter they can be
Standard Burlington Code Academy Retro format:
1/30