Business Apps Board

Each team operates a two board system. One board for demand and one board for delivery (supply). The majority of the backlog is on the demand board and organised by the various stakeholders. The image below only shows the delivery boards. Each delivery board has a part of the demand board on it so as to act as a funnel for the incoming work.

Demand column:

Used to visualise the various stakeholders and to get them thinking about priorities.

Input column:

This is possibly the most important column on the board. This column drives out the prioritisation conversation with stakeholders and provides protection for the delivery team. It forces conversations that used to be avoided and often pushed onto the delivery team to prioritise.

WIP column:

Team members pull work from the Input column only when they are ready to do so. If they get blocked on a piece of work then they first focus on unblocking the issue or assist other team members with their tasks. This particular team opted for a grid based layout (following pressure from management!) to include their individual names so everyone could see who was working on what. Initially it drove some wrong behaviours from management seeing an empty slot and trying to get it filled. This wrong behaviour was resolved by making an explicit policy around the purpose of the board and ensuring everyone was bought into it and honoured it. After several attempts by myself to remove the names, the team actually had many reasons why they wanted to keep the swim lanes. However wrong it feels, this setup actually works well for the team. As you can see, they still have avatars which allows them to swarm around the board where necessary.

Schedule column:

Once a piece of work has been done it often has to wait for a scheduled maintenance window (often out of hours) before it can be deployed and put live. This column is kind of a waiting for release column and used to plan maintenance windows.

Long term blockers:

This section of the board with lots of cards with magenta post-its on it is the long term blockers area. This team deals with many 3rd parties and regularly get blocked whilst waiting for the 3rd party to complete something. Unfortunately, the contracts with these 3rd parties do not provide enough leverage to get them to respond quicker so the team could only make them visible. Making them visible enabled senior management to see exactly who was blocking them and chase suppliers on a daily basis, applying pressure where possible.

Waste Envelope:

Any waste incurred by the team was captured, quantified, and stored in the waste envelope for discussion during retrospectives.

Blockers Envelope:

All magenta post-it notes (blockers) are kept once the blockage has been removed. These blockers are then analysed during retrospectives to look for trends, common blockages, or any other intel to assist in improving the process.


The team have stuck a paper based form to the left of the board to simplify the generation of a Cumulative Flow Diagram (CFD). They find it easier to write the card count for each column on the form and then update the electronic chart periodically – say at the end of each week.

“The Infra Card”:

Each day a new card is inserted directly into the WIP column (a slot is reserved so as not to blow wip limit). Each day between 13:30 and 15:00 the team hit the Infra queues for their team and complete what they can within the time box. The number of completed jobs/tickets in infra is added to the card and its then placed in the done column. The number of jobs/tickets completed is added to the CFD done value.

  1. Can you pls help explain the kind of cards that went into the Waste Envelope in your scenario? I have always had trouble discreetly identifying them.

    • for these teams it is mostly straight forward – if work is started, i.e. in the WIP column and ends up never getting out of this column due to not being required anymore then its waste. The team write on the card how many man hours/days have been spent. The reality is very little waste has been identified – in the order of 1 to 2 cards per month, although one team had a project canned which clocked up 16 man weeks of waste.

  2. Ok, I see.
    With “infra card” you refer to the work incoming through the ticketing tool (InfraEnterprise)

    • Yes, indeed. Infra is the ticketing tool used by the whole department. In theory it’s a great tool – but the reality is it drives the wrong behaviours just like every other ticketing tool in the industry. They all operate on a push mechanism and even contain functionality to automate the pushing of work around the system – automated chaos!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: