Skip to content
This repository was archived by the owner on Feb 8, 2024. It is now read-only.

200326: Task management

Jump to bottom
Valery V. Vorotyntsev edited this page Mar 26, 2020 · 1 revision

[[TOC]]

Task management

Hare developers are faced with three sources of tasks:

  1. Issues at GitLab 🐰
  2. HA kanban board
  3. Hare/HA bugs

Why so many? Which one to choose?

GitLab issues

GitLab issues is where software engineering happens. :construction_site:

Hare team's modus operandi is defined in the PC3 (Pedantic Code Construction Contract), which is clearly pro GitLab/GitHub issues; see

2.1. Preliminaries

[...]

  1. The project SHALL be hosted on github.com or equivalent, herein called the "Platform".

  2. The project SHALL use the Platform issue tracker.

and

2.3. Development Process

  1. Change on the project SHALL be governed by the pattern of accurately identifying problems and applying minimal, accurate solutions to these problems.

  2. To request changes, a user SHOULD log an issue on the project Platform issue tracker.

  3. The user or Contributor SHOULD write the issue by describing the problem they face or observe.

  4. The user or Contributor SHOULD seek consensus on the accuracy of their observation, and the value of solving the problem.

  5. Thus, the release history of the project SHALL be a list of meaningful issues logged and solved.

The recommended way to report a problem to Hare developers is to create a GitLab issue. Jira bug reports are accepted grudgingly. 🪲

Why Jira

Corporate inertia is real. While we may show our colleagues alternative methods of collaboration, we cannot make them change their habbits and accept the "Platform" as their saviour.

🙊

And some organisations, as we know too well, have a particularly nasty habbit of picking the worst tool for the job and mandating its use (shout-out 💩 to Google Chat IM!). Sigh. 😞


Kanban board

The HA kanban board consists of the tasks that will be the focus of Hare team's efforts for the next 4 weeks. The goal is to complete all tasks from M2–M5 sections by April 23rd. :calendar_spiral:

This kanban board is what we use to report HA progress to management. Team members are expected to add their daily status reports to the kanban tickets(s) they are working on. Current state of the kanban board is discussed at the "scrum" meetings.

This approach may provide the desired level of external visibility, while keeping the bookkeeping load on engineers to the minimum. (In other words, @john.forgan will have a good view on the status of HA work and won't need to interrogate engineers to obtain that information.)

The HA kanban board is an experiment. Let us try this new method of reporting for 4 weeks (till April 23rd) and then decide if we want to keep it.

How to use the kanban board

  1. Pick a task from the "Take Me" column.
  2. Get it done, using as many GitLab issues and merge requests as necessary.
  3. Goto 1.

Debugging duty

Two Hare engineers will be paying for the sins of others dedicated exclusively to troubleshooting on clusters and investigating HA issues, reported by QA.

In the beginning, the Almighty Tallest will be @andriy.tkachuk and @mandar.sawant. We want to establish a rotation to train the debugging skills of Hare developers and give them first-hand experience with the real EES. The A.T. duty gives one a clear picture of UX/DX shortcomings and vaccinates against architectural astronautitis.

So, in a fortnight or so (April 6?) one of the "kanbaners" will switch roles with one of the Almighty Tallest. ⚔️

Who may not even want to leave. But will have to, for greater good.

Dost thou wish to leave with such hasty abandon?

  • For bugs and glory, press N.
  • For work and worry, press Y.

-- @vvv

Clone this wiki locally