-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add document on sprint-kanban based workflow #67
Open
aashish24
wants to merge
1
commit into
master
Choose a base branch
from
github_workflow
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
# Team Process | ||
|
||
Our team process involves scrum-style practices with some key differences | ||
|
||
* We don't have definite sprints. Our backlog is fluid and re-evaludated every week. | ||
* We don't story-point. We should, but we aren't ready to do this yet. | ||
|
||
## States | ||
|
||
### `Triage` | ||
|
||
> Technical contributors: We aren't sure if we should do this, how hard it will be, or if we have enough information. | ||
|
||
`Triage` work may be necessary in the indefinite future, but has not been researched. This is the requirements gathering state. | ||
|
||
### `Backlog` | ||
|
||
> Technical contributors: We know we can and should do this. We aren't ready to do it yet. | ||
|
||
`Backlog` work has been reviewed (asyncrhonously) by the whole team and deemed to be necessay and adequately understood. | ||
|
||
### `Ready` | ||
|
||
> Technical contributors: We should do this as soon as we have time. | ||
|
||
`Ready` work has been reviewed synchronously by the whole team and accepted for immediate pickup. | ||
|
||
### `Done` | ||
|
||
> Technical contributors: We did this, and it's merged to main. Please verify that we met the criteria. | ||
|
||
`Done` work has been completed by the technical team and requires review from team lead and stakeholders. | ||
|
||
## Responsibilities | ||
|
||
* Team leads and stakeholders | ||
* Can propose new work, which becomes `Triage` | ||
* Are solely responsible for maintaining priority in `Triage`. | ||
* Help technical team maintain priority in `Backlog`. | ||
|
||
* Technical contributors | ||
* Can also propose new work, which can become `Backlog` or `Triage` depending on scope. | ||
* Are responsible for taking action on high-priority `Triage` work, moving it into the backlog. | ||
* Are responsible for gathering additional information or pushing back against `Triage` work. | ||
|
||
## Meetings | ||
|
||
Our team has a single weekly meeting. The goals of this meeting, in order of priority, are: | ||
|
||
1. To verify the correctness of `Ready` | ||
2. To verify the correctness of `Backlog`, and promote work to `Ready` if appropriate. | ||
3. To review `Done` and verify that requirements have been met. | ||
|
||
## Development | ||
|
||
Install https://github.com/Kitware/ldc | ||
|
||
```bash | ||
# copy .env.example and make any changes | ||
cp .env.example .env | ||
|
||
# bring the server up | ||
ldc up -d | ||
|
||
# replace a pre-built image with the development version | ||
# for example, here's how to work on the girder server code | ||
ldc dev up girder | ||
``` | ||
|
||
To work on the Vue client, see development instructions in `./client`. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this development section can be removed - it is for another project perhaps?