-
Notifications
You must be signed in to change notification settings - Fork 7
PIVOTAL TRACKER STORY
Pivotal Tracker Story
A feature story should contain the following information
Title: one line describing the story
Description: a detailed description of the story.
Acceptance Criteria(presented as Scenarios): These should include conditions that must be met for the feature to be accepted.
Scenario:
Given context
And some more context...
When event
Then outcome
And another outcome...
Example
Title: As a Taskee I should be able to grant the Tasker access for offline communication
Description:
As a Taskee, I should be able to make my contact information visible to the Tasker after successful completion of tasks
So that they can be able to contact me offline
Acceptance Criteria:
Scenario 1:
Given that I am a taskee
And I have finished a task assigned to me
And all payments have been completed,
When I log into dashboard,
Then I should see a link where I can decide to share or decide not to share my contact info with the tasker
Scenario 2:
Where necessary, the story should provide more scenarios that cover other edge cases.
Note: Every story title should include the word ‘should’ as opposed to ‘can’. e.g. It’s unclear whether the story “User can delete comment” is a feature or a bug. “User should be able to delete comment” or “User should not be able to delete comment” are much clearer: the former is a feature, the latter a bug.
A bug story should contain the following information:
Title: A short description of the bug.
Description: What is currently happening? What should be happening?
Steps To Reproduce: Outline the steps to reproduce/show the bug.
Resources: Include screenshots and other assets to help explain/show the bug.
Example
Title:
Unwanted spaces should not appear between widgets.
Description:
The number of widgets showing per row is inconsistent.
When users view their dashboard, each row should contain 2 widgets per row.
Steps To Reproduce:
- Login to Skilltree dashboard.
- Some rows display unwanted spaces in between the widgets.
Resources:
Attach a screenshot of the error caused by the bug if applicable.
A chore story should include the following information:
Title: A short description of what needs to be done.
Description(if applicable): a detailed description of the what the chore does.
Why is this important: Why is it needed? Does it help the team go faster or is it a dependency that could cause problems in the code base if it’s not done?
Example
Title:
Setup CI for user management service.
Description(if applicable): Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day.
Why this is important:
Stable CI setup will make it easy to integrate our code while ensuring that all defined tests are passing per integration.