status-im
/
status-react
mirror of https://github.com/status-im/status-react.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-react/doc/decisions/0012-using-pivotal-tracker.md

49 lines
2.3 KiB
Markdown
Raw Permalink Normal View History

Add Using Pivotal Tracker document Signed-off-by: Pedro Pombeiro <pombeirp@users.noreply.github.com>
2019-04-02 13:44:24 +00:00
Using Pivotal Tracker
===
## Abstract
The Core Improvements swarm tracks its workflow in a Pivotal project. Although GitHub items can still be created to facilitate communication, the official way to track progress of a functionality/bug fix is in Pivotal.
[Project board link](https://www.pivotaltracker.com/n/projects/2232205)
## Creating Pivotal Stories
Fill in `Story Type`, `Requester`, `Owner` (if already assigned), and `Points` (if an estimate is available). Add a description and optionally group it using a label. As a rule of thumb, Pivotal stories should be grouped in epics for better high-level visibility. Although labels can be used to group stories, the prescribed way to do that is through epics.
You can add tasks under a Story for smaller items that don't warrant its own Story.
Do add the link to the Pull Request to the Story when one is available.
## Lifetime of a Pivotal story
The `State` field in the Pivotal story is used to track the progress of a Pivotal Story, and has the following interpretation:
| State | Meaning |
| ---------- | -------- |
| `Unstarted` | In backlog |
| `Started` | Developer has started work on story |
rename status-react to status-mobile This way the name of the repo makes at least some sense and matches the `status-desktop` repo naming. Also updated `status-jenkins-lib` since it also contained references to `status-react` repo and job names. Signed-off-by: Jakub Sokołowski <jakub@status.im>
2022-07-17 12:37:46 +00:00
| `Finished` | Developer has finished work on story (Pull Request for story is in [REVIEW](https://github.com/status-im/status-mobile/projects/7#column-1843024) column in [Pipeline for QA](https://github.com/status-im/status-mobile/projects/7) board) |
| `Delivered` | Pull Request for story is in testing in [Pipeline for QA](https://github.com/status-im/status-mobile/projects/7) board) board |
Add Using Pivotal Tracker document Signed-off-by: Pedro Pombeiro <pombeirp@users.noreply.github.com>
2019-04-02 13:44:24 +00:00
| `Accepted` | PR has been merged |
| `Rejected` | PR has been aborted |
### Rules of thumb
- **Q:** _When to create a Pivotal story?_
**A:** Stories should be created whenever estimated work exceeds half a day, or when part of a bigger epic.
- **Q:** _What do points equate to?_
**A:** We've agreed to make 3 points equate roughly to 1 day of work. From there, we can extrapolate:
| Points | Estimated Time |
| -------- | ---------------- |
| 0 points | < 1 hour |
| 1 points | 1 hour - 0.5 days|
| 2 points | 0.5 - 1 days |
| 3 points | ~1 day |
| 5 points | 2 - 3 days |
| 8 points | ~1 week |
Lint and fix missing trailing newlines (#16445) Apply the Clojure Style Guide recommendation to end files with proper lines (having a trailing newline character). See https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206
2023-07-04 19:40:13 +00:00
We should avoid 8 point stories by breaking them down into smaller stories as much as possible.