-
Notifications
You must be signed in to change notification settings - Fork 31
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
We've decided to stop working in sprints and simply schedule our work weekly on monday meetings using a kanban board with no retrospective meetings. Ref: teamniteo/operations#2091 (comment)
- Loading branch information
Showing
11 changed files
with
79 additions
and
149 deletions.
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
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
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,37 @@ | ||
# Kanban | ||
|
||
Our work process is based on [Kanban](https://en.wikipedia.org/wiki/Kanban) with some elements from [Scrum](https://en.wikipedia.org/wiki/Scrum_(software_development)): | ||
|
||
* We are our own *product owners*, as we have no customer projects. | ||
* We work asynchronously, so keep scheduled meetings to a bare minimum. | ||
* We organize our work using a Kanban board. | ||
|
||
Read about [writing User Stories and issues](user-stories.md). | ||
|
||
User Stories that are dependent on each other should be merged into one bigger user story. This kind of User Stories can have 2 assignees. | ||
|
||
## Monday Meetings | ||
|
||
Each Monday we have a meeting to review the Kanban board and check in with our [OKR's](https://en.wikipedia.org/wiki/Objectives_and_key_results). We typically have one meeting per project starting with Operations. | ||
|
||
Turn on your camera during the meeting. Try to refrain from doing other things (browsing, doing support, etc.) during the meeting -- we only have this meeting and it doesn't take a lot of time so we should all pay attention to everyone else for this period. | ||
|
||
## Urgent Production Fixes | ||
|
||
If we need to fix an urgent bug, we use the Scrum *priority lane* approach: the user story gets written and then if the product owner decides it really is urgent, the user story is added to the 'In Progress' pipeline and labeled with Priority Lane so that everyone knows it is an exceptional and urgent issue and the whole team needs to focus on getting it completed as soon as possible. | ||
|
||
## Recurring Tasks | ||
|
||
There are a bunch of tasks we have to do every month/quarter/year. To make sure they get assigned enough time for proper execution, we include them in the Kanban board as user stories. The only difference is, they don't need user story demo recordings since they happen so often and are repetitive. | ||
|
||
For every month/quarter that a recurring task is required we (re)open the issue and create a comment for the new month/quarter. | ||
|
||
## On-Calls | ||
|
||
Sometimes, things break in the middle of the night or on weekends. The great thing about being a remote-first team is that we cover different time zones so there is almost always someone available. The solution for the weekend is to have Niteans on-call. | ||
|
||
Being on-call means being available for any critical, urgent issues that may arise. Some examples of this are servers offline or the product app is down. Each on-call day (Saturday and Sunday) counts as a 2-hour workday, even if there were no emergencies. Any work more than two hours counts as regular work. | ||
|
||
Niteans can be on-call only if they already pass basic support training or has already reported for [Everyone on Support](https://github.com/teamniteo/handbook/blob/master/4_Marketing-Support/everyone-on-support.md). | ||
|
||
Every [Monday Meeting](https://github.com/teamniteo/handbook/blob/master/2_Operations/kanban.md#monday-meetings), we assign who will be on-call for the next weekend and note it in the [Monday Meeting issue](https://github.com/teamniteo/operations/blob/master/.github/ISSUE_TEMPLATE/monday_meeting.md). |
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
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.