Tasks & Backlogs

Principles

1. GitHub is the only one task tracker for developers (do not assign devs to Asana tasks: you own them, devs just (smart) executors. Dev copy-paste your tasks to GH after approving them on betting table)
2. Developers should not maintain product backlog(s)
3. The Technical backlog is the only backlog developers should maintain and be in charge of.
4. There should be a minimal number of sources of tasks:
   1. Pitches and betting tables.
   2. Slack messages for bug-reports and small improvements requests (for @dev-hotline only!).
   3. Devs can create technical GitHub issues for devs.

Task sources

There are essentially a few types of requests/reports:

• ⭐️ Feature Request (new feature or improvement)
• 🔥 Burning Issue Report (an issue that needs to be looked right now)
• 🐞 Bug Report (an issue that needs to be fixed at some day)
• ⚙️ Technical task (only devs create and use them)

They have different sources (ways to ask a dev team to work on them):

1. Feature Request:
   1. Create a ShapeUp Pitch together with a dev
   2. Get approval on the betting table
   3. Dev will create a GitHub issue (with a linked with Asana task, if any)
   4. Dev(s) works on it
2. Bug/issue reports:
   1. public message on Slack to @dev-hotline
   2. GitHub issue (@dev-hotline creates it)
   3. work now or later (depends on severity, size, etc.)
3. Improvement request:
   1. public message on Slack to @dev-hotline
   2. @dev-hotline estimates it or redirect it to another dev (often to a system owner)
   3. dev(s) chose a track (quickfix or feature request)
   4. dev creates a GitHub issue and shares a link to it to allow the requester to track the progress
4. Technical task:
   1. developers create them and work when needed. Mostly during cool-down or during support-engineer duty.