Process

Description

The APEMAN project will be executed as a light-weight Kanban workflow with the following states (or columns) in order:

• Bucket - For any incoming issues to be evaluated. Issues are in no particular order here.
• Backlog - The ordered backlog of work to be performed.
• On Deck - Issues taken from the backlog that have sufficient definition to be started (see Definition of Ready).
• In Progress - Issues that currently being actively worked on.
• Done - Issues that have been completed.

The project Kanban board is managed within GitHub as the APEMAN Project.

Definition of Ready

Before an issue may be promoted to the On Deck state:

• The issue must be assigned a discipline tag (e.g. "Implementation", "Project Management", etc.)
• The issue must have sufficient description to be implementable.
• The issue must have explicit Acceptance Criteria defined.

Definition of Done

Before an issue may be assigned to the Done state:

• All Acceptance Criteria must be met
• For implementation tasks:
  • Sufficient unit and integration tests must be defined
  • The code must pass the continuous integration build (implying all test and quality measures have passed)
  • Any necessary BDD tests must be implemented and passing
  • The issue's code branch must be merged to master and the issue closed

Workflow

WIP: There may only be a maximum of one issue In Progress per active participant at any one given time. Though it should be an exceptional case, it is permitted to move an issue back into On Deck if it's expedient to put an issue on hold.

Cadence: The workflow is continuous as opposed to following defined iterations. To support continuous improvement, each week will conclude with an informal Retrospective with observations recorded in the APEMAN wiki.