LACE (CCSQ Lean Agile Center of Excellence)

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Program

Work in progress — Tantus HCD


Background

Work in progress — This is the background. Why is the program reaching out for assistance?


Workflow Analysis

The HCD work is managed under a Jira project. Nine (9) boards are created to support their work. The goal of this section is to analyze the current active boards:

  • The HCD Daily Scrum is used by the team to manage their daily work. The Board is composed of 6 columns representing the steps a work item can follow from start to completion: To Do, Started, Today, Blocked, Waiting, and Done. The Board is also composed of 7 lines AKA Swimlanes that represent the team members and active participants to who the work items can be assigned: Amy, Brandy, Brian, Chelsea, Howard, Meaghan, and Rob.    
    • At the time of our analysis on August 25th, the board shows a total of 56 work items spread throughout the board as follows: To Do (9), Started (11), Today (14), Blocked (0), Waiting (10), and Done (12). Also, the Board revealed that the 56 work items are assigned to the team members and participants as follows: Amy (6), Brandy (1), Brian (12), Chelsea (11), Howard (8), Meaghan (13), and Rob (5).
    • Observation 1: There is an interrogation about the purpose and the benefit of the "Started" vs "Today" and "Blocked" vs "Waiting"; as someone may think that Today's work items should be included in "Started" work items, and also Waiting's work items should are a type of "Blocked" work items and should be grouped together. Furthermore, the work items are grouped under various predefined epic such as Training, HCD Community and CoP, Thought Leadership, Team Consulting, PRA, CSAT, ... It would be interesting to understand the nature of their work items and to review what process can best help or support the completion of each work item type.     
    • Observation 2: The HCD team is working on a 4-week iteration cadence, roughly 20 business days if there's no holiday. 7 business days before the end of the iteration, we can notice that 35 work items are in progress, which represents about 65%of the work planned for the iteration. This looks like a lot of work in progress at a time. Also, there are no visible work-in-progress (WIP) limits per column or per team member/participant. It would be interesting to understand the team capacity, capacity allocation and determine the right WIP limits for each of the columns in the process when relevant.     
  • No labels