Introduction

Issues workflow status is tracked through GitHub 'project' board (as a alternative to Trello). To simplify tracking and administration, generic names are used for workflow states (regardless of issue type). If needed, filtering board by issue type can be achieved by 'Filter Cards' field in board view.

Workflow states

Following workflow states are defined and configured within project board:

• Backlog
  • Buffer for all incoming (newly-created) issues.
• Grooming
  • Discussions
  • Decissions
  • Triage:
    • define Issues type (e.g. epic, user-story..)
    • define references (e.g. create new epic or update existing one...)
• Ongoing
  • Assigned and categorized issues that we are working on
• Ready
  • Issues that are finalized and ready for next step (depending on type)
• Done
  • Closed issues (automatically moved in Project view)

Workflow per Issue type

While workflow state names are same for all issue types, expectations and needed actions can differ from types to type

Bug

• Backlog
  • Each new issueis automatically added to backlog
  • Issuer mark issue with 'Bug' label
• Grooming
  • Assign theme label
  • Reference affected user-story (one or more)
  • Further discussion if needed
  • Assign issue to team member and move to 'Ongoing' state
• Ongoing
  • Team member is assigned
  • Fix development is ongoing
• Ready
  • Development is finished
  • Ready to be tested and included into release
• Done
  • Fix is delivered into release
  • Issue is marked as Closed

Enchantment

• Backlog
  • Each new issue is automatically added to backlog
  • Issuer mark issue with 'Enchantment' label
• Grooming
  • Assign theme label
  • Further discussion if needed
  • If issue is related to existing User Story:
    • Reference existing user story
    • Assign issue to team member and move to ongoing state
  • If issue require creating new User story or Epic:
    • Put appropriate label (User-story or Epic)
    • Follow workflow for new type (epic or US) from 'Grooming' phase
• Ongoing
  • Team member is assigned
  • Feature Development is ongoing
• Ready
  • Development is finished
  • Ready to be tested and included into release
• Done
  • Feature is delivered into release
  • Issue is marked as Closed

User story

• Backlog
  • Each new issue is automatically added to backlog
• Grooming
  • Assign theme label
  • Reference appropriate Epic
  • Check for possible duplication
  • Further discussion if needed
• Ongoing
  • Team member is assigned
  • Assigned team member update issue with clear expectations and technical details
  • If needed, new tasks are created and referenced
• Ready
  • Analysis is done
  • Technical structure, expectations and DoD are done
  • If needed, tasks are created and listed (referenced)
  • Ready to be tested and included into release
• Done
  • Feature is delivered into release
  • Issue is marked as Closed