Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/clinical-genomics/streamline-delivery
Project tracking for streamline-delivery
https://github.com/clinical-genomics/streamline-delivery
Last synced: 6 days ago
JSON representation
Project tracking for streamline-delivery
- Host: GitHub
- URL: https://github.com/clinical-genomics/streamline-delivery
- Owner: Clinical-Genomics
- Created: 2024-02-12T08:34:26.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2024-02-13T08:32:34.000Z (10 months ago)
- Last Synced: 2024-02-13T10:31:24.573Z (10 months ago)
- Size: 5.86 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 12
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Streamline-delivery
This is a repository for project management in the streamline-delivery project.
## How we work
- Build backlog with user stories
- Separate technical refinement
- Separate sprint planning
- Sprint where we execute the plan
- Sprint retrospective
The user stories are created as milestones [here in this repo](https://github.com/Clinical-Genomics/streamline-delivery/milestones).
The implementation plan is broken down into [work item issues](https://github.com/Clinical-Genomics/streamline-delivery/issues?q=is%3Aopen+is%3Aissue+label%3A%22Work+item%22) which are associated with the milestone.
The sprint starts once the sprint planning is done and lasts for a preset time period (usually two weeks).
## Why we work like this
- Creating user stories with production increases the likelihood that we build the right thing.
- Creating an implementation plan increases the likelihood we build the thing right.
- Planning the sprints increases the likelihood that we build the things in the right order.
- Having retros increases the likelihood we do not repeat mistakes.
Doing the steps above separately decreases uncertainty about what needs to be done which means we get more things done.
## Creating user stories
### Template for user story
```
Title: A short, descriptive title.
As a [type of user],
I want [an action or feature],
So that [benefit or reason].
Acceptance Criteria
- Criteria 1
- Criteria 2
- Criteria 3
...
Notes
- Additional information.
- Dependencies.
- Related user stories.
```
Each story is assigned a priority based on how important it is to production.
## Technical refinement
The developers prepare for a refinement meeting for a specific user story and discuss the way to implement it.
The decided upon implementation plan is documented and an estimate of the amount work is done.
Separate work item issues are created based on the implementation plan and associated with the story milestone.
## Sprint planning
Based on the dependencies, priority and work estimate, the developers decide on which stories to work on during the sprint.
Individual work items are scheduled for the sprint - put into the ready column on the project board.
Developers are assigned to the user stories and know which work items they should work on.
## Sprint
The developers implement the work items.
If anything is unclear regarding the implementation, a technical refinement is scheduled if necessary.
If anything is unclear regarding the acceptance criteria, a user story meeting is scheduled if necessary.
## Retrospective
Once the sprint is over, the devs meet and
- Go through the project board
- Discuss what went well
- Discuss what could have gone better
- Write down actions to take to improve the next sprint
## Resources
- [Design](https://www.figma.com/file/jfcyr8KAdFYhXDVyZLfYf2/Trailblazer-mock?type=design&node-id=0-1&mode=design&t=bM8tgbpJXEaK9RGt-0)
- [Requirements draft](https://docs.google.com/document/d/13FdNjrMG0bIwpHuuo_ZGFDdGhhLRDWD4Er8ErgR27rQ/edit#heading=h.r3cf4lonoo68)
- [Project board]()
- [Retro notes](https://docs.google.com/document/d/1eQK6LefuQx0Xua1z5Lri-LDPNr0cpFhXsLBrRIQNSTw/edit?usp=sharing)