Skip to content

IssueManagement

Jump to bottom
Timothy Aldrich edited this page Aug 3, 2022 · 1 revision

project: infraspective tags:

  • dev
  • github
  • issues

Issue Management

Overview

Currently, I am a solo developer on this project. I also have a full-time job, (which is not this) and I have a few other projects that I am also working on. That said, I am trying be realistic about the times and workload, and also set up the processes and components in case the project gets additional contributors and/or I get more time to work on it.

To do that, I am going to use github tools and technologies for all of the management, and I am committing to a monthly release cycle

Issue status

In looking for successful projects and management processes, I came across this article from the nunit project. Most of this is a direct copy of their terminology, descriptions and workflow.

flowchart LR
  New-->Backlog
  New-->Discuss
  New-->Closed
  Discuss-->Backlog
  Discuss-->Closed
  Backlog-->ToDo
  ToDo-->InProgress
  InProgress-->Closed

  style New fill:#bfd4f4
  style Discuss fill:#ffb8c5
  style Backlog fill:#2564b9
  style ToDo fill:#ee3f46
  style InProgress fill:#c2e1a2
  style Closed fill:#91ca55

  classDef default color: #2d333b
Loading
  1. New : All issues start out as 'New'. These are collected but unprocessed items. During a review, new issues are categorized for further work. An issue that needs more clarity or detail would go to Discuss, while an issue that is already sufficient would go to Backlog. Issues that will not be worked on can be moved directly to Closed and given an appropriate "closed reason" label.
  2. Discuss : Although there is only one developer currently, the ability to "flesh out" the details or do some additional brainstorming is still very useful.
  3. Backlog : The standard agile backlog of work that is available to be scheduled for work.
  4. ToDo : The issues that are available as options to complete during this sprint. ToDo will be empty when the sprint is complete.
  5. InProgress : Issues that are being actively worked on. Anything that is InProgress must be assigned to someone
  6. Closed : No further work to be done on this issue. Every issue that is closed needs to have a "closed reason" label.

Project workflow

Issues and PRs are managed via the Main infraspective project

When an issue is created in the infraspective repository, it is added to the project.

The two main boards used for planning are:

  • Issue Management
  • Release Planning

Issue Management board

This view provides a traditional "Kanban style" board to manage the Status of issues. All issues starts out as New. Each issue is triaged. If it needs additional information, or thinking, it moves to Discuss. Issues in the New and Discuss column should be considered "Not ready to be scheduled yet". When they are, they are moved to Backlog.

Anything in Backlog represents a unit of work that we "want to do soon".

During release planning, issues are moved from Backlog to Todo as "items we are committing to work on in the next 90 days."

Release Planning board

Once issues are set to a status of Todo, they are available to be organized into the release cycle, which is currently set to a monthly cadence. The goal is to slot the work from No iteration into one of the next three iterations.

Clone this wiki locally