Kanban at Scale: Product Backlog Vs. CIPSA Kanban Backlog

In the CIPSA Framework, world’s only practical scaled agile framework, we have three backlogs: Product Backlog, CIPSA Backlog, and Team Backlog. Considering the CIPSA Kanban Framework, the CIPSA Backlog will be called the CIPSA Kanban Backlog.  In this article, we will explore the differences between Product Backlog and CIPSA Kanban Backlog.

In one of the earlier articles related to the CIPSA Kanban Framework, I wrote the following:

“In the CIPSA Kanban Planning meeting, a CIPSA Kanban Backlog is created with the Product Backlog items that can be delivered by multiple teams in the upcoming release. Post CIPSA Kanban Planning meeting, for each team, an individual team level Kanban Planning event takes place. This results in a Team Kanban Backlog for each team.”

Now, if the Product Backlog items are directly taken into the CIPSA Kanban Backlog, but we are actually executing the items in the Team Kanban Backlog, two questions come-up:

• What is the need of CIPSA Kanban Backlog? We already have Product Backlog and Team Kanban Backlog.
• If needed, what exactly are the differences between the Product Backlog and CIPSA Kanban Backlog?

Do note that while my explanation is specific to the CIPSA Kanban Framework, similar concepts are in the CIPSA Scrum Framework.

Why CIPSA Kanban Backlog?

First and foremost, we don’t execute the entire Product Backlog, but parts of it. Considering the Kanban framework, we have a CIPSA Kanban Backlog due to the following reasons:

1. We need to clearly segregate the items taken for the upcoming Release for all the Kanban teams. 
2. We need to add the meta-events into a backlog where the CIPSA Team will not be executing the work items, but also a plan for the meta-events such as CIPSA Kanban Planning, CIPSA Daily Stand-ups etc.
3. Segregation of Kanban teams (human resources) need to happen. This can happen only at the CIPSA Kanban Backlog level.
4. Allocation of resources doesn’t happen at the Product Backlog level. It can only happen at CIPSA Kanban Backlog and Team Kanban Backlog level. 

Hence, the CIPSA Kanban Backlog is created from the Product Backlog. It’s depicted in the figure below.

Next, let’s see the differences between the Product Backlog and the CIPSA Kanban Backlog.

Product Backlog Vs. CIPSA Kanban Backlog

Difference # 1: Product Backlog is a single one and stands on its own - separate, unique. CIPSA Kanban Backlog comes from the Product Backlog. 

Difference # 2: The Product Backlog will have the product backlog items. Some of the product backlog items will be part of the CIPSA Kanban Backlog.

Difference # 3: Product Backlog is a live document and continuously updated. The CIPSA Kanban Backlog will be for a Release and when the Release is over, it’s discarded.

Difference # 4: The Chief Product Owner (CPO) owns the Product Backlog. The CIPSA Team owns the CIPSA Kanban Backlog. If a complex service is delivered, then the CPO role will be replaced by Chief Service Request Manager (CSRM).

Difference # 5: The Product Backlog doesn’t contain any meta-events. The CIPSA Kanban Backlog will contain meta-events such as CIPSA Planning, CIPSA Daily Stand-ups, among others.

These differences are noted in the below table. 

Video Explanation: Product Backlog Vs. CIPSA Kanban Backlog

The video below [duration: 04m:38s], explains the diferences between the Product Backlog and CIPSA Kanban Backlog. For better experience, plug-in your earphones and go full screen with high-definition (HD). 

Before we close:

Can you think of a few other differences? Give it a try!

Closing Remarks

I believe you tried the above question! Now, you’d be thinking if there are any similarities between the Product Backlog and the CIPSA Kanban Backlog. One can think of the following ones: 

1. Like Product Backlog is one of the key artifacts in CIPSA Kanban framework, the CIPSA Kanban Backlog is also a key artifact.
2. Considering practical, hands-on approach (after all the CIPSA framework is mainly about that!), the Product Backlog Items and the CIPSA Kanban Backlog’s high-level items will be summary-level tasks. 

To know more about the roles (accountabilities), artifacts and events/meta-events, you can download the CIPSA Framework Guide. When you go through it, you will discover more differences on your own!

I believe this article gives you more clarity with respect to the differences between the Product Backlog and CIPSA Kanban Backlog.

References

[1] A Closer Look at the CIPSA Kanban Framework, by Satya Narayan Dash

[2] Introducing Practical Scaled Agile Framework with CIPSA Certification, by Satya Narayan Dash and ManagementYogi.com 

[3] New Practical Scaled Agile Framework – The CIPSA Framework Guide, by Satya Narayan Dash and ManagementYogi.com 

[4] Kanban at Scale: Managing Multiple Teams and Boards with MS Project Agile, by Satya Narayan Dash, first published by MPUG.com