DCM Boards

Owned by James Seabrook
Jul 30, 2021
2 min read

Background

Current Situation (2021)

Currently there are two DCM boards:

  • Scrum Backlog (Seko DCM) which is only used for the backlog, visible to Adam Marriott

  • Kanban board, (DCM full) which is visible only to Indigina.

 

Problems occur because of a conflict in priorities. The kanban uses “highest priority” whereas the backlog uses ranking.

Proposed Solution

Use one scrum board for the development with ranked backlog priorities. The priority label becomes information only and should not be used for prioritising work.

Use a kanban board for working out “state of readiness” as far as the pre-development work is concerned. It should be ready for development prior to being worked on. Note that this is not a scrum requirement but is a good idea for business requirement elicitation.

The Voyager Scrum Team use this model and it works well.

The active sprint (which would normally be for two weeks, ie. time-boxed) is specifically designed for the business to know the tickets which have been committed to. This is useful for seeing what gets done over the period which to an extent helps with mapping out future request timelines.

There need to be a number of statuses:

  • business analysis - to do / defined / ready to refine / ready for sprint planning etc

  • development

    • design and implementation

    • quality assurance

  • user acceptance testing

 

Backlog

Full backlog with active sprint backlog

 

  • Generally user stories only, apart from technical changes which might have been added by the dev team

  • Active sprint backlog is items to be done in this sprint)

  • The rest are currently uncommitted, but the highest priority is at the top

 

 

Active Sprint with Development Tasks

Kanban Board for Ticket Design

Purpose of this is to show tickets which are acceptable to the dev team regarding elaboration of requirements and those which still need some business requirements input.