Scrum at Scale: Differentiating Between Product Backlog and CIPSA Sprint Backlog

  

Like there are differences between the CIPSA Sprint Backlog and the Team Sprint Backlog, we also have differences between the Product Backlog and the CIPSA Sprint Backlog. When you go for the upcoming CIPSA Certification, you need to know the differences. In this article, we will explore a few differences. 

In one of the earlier articles, I wrote the following:

“The line items in the CIPSA Sprint Backlog are taken from the Product Backlog. In the CIPSA Sprint backlog, the items are not broken down into individual tasks, but they are in the Team Sprint Backlog. This distinction is important to understand.”

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

Why CIPSA Sprint Backlog?

We need a CIPSA Sprint Backlog for the following reasons.

• Adding of meta-events such as CIPSA Sprint Planning, CIPSA Daily Scrums.
• Segregation of work items with respect to individual Scrum teams.
• Assignment of Sprints across the individual Scrum teams.
• Allocating resources to the work items.

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

Product Backlog and CIPSA Sprint Backlog

While the individual teams are sprinting, the entire CIPSA Scrum Team is also sprinting. It happening on the same Sprint number. While the backlog items are available in the Product Backlog, the final, ordered or prioritized items to be taken in the upcoming Sprint is at the CIPSA Sprint Backlog level.

Now, let’s see the differences between the Product Backlog and the CIPSA Sprint Backlog.

Product Backlog Vs. CIPSA Sprint Backlog

Difference # 1: Product Backlog is a single one and stands on its own - separate, unique. CIPSA Sprint 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 (post prioritization) the CIPSA Sprint Backlog.

Difference # 3: The Product Backlog will have a Product Goal. The CIPSA Sprint Backlog will have a CIPSA Sprint Goal. The final goal is to reach the Product Goal by achieving a number of CIPSA Sprint Goals.

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

Difference # 5: The Chief Product Owner owns the Product Backlog. The CIPSA Team owns the CIPSA Sprint Backlog.

These differences are noted in the below table. 

Can you think of any other difference(s)? 

Video Explanation: Product Backlog Vs. CIPSA Sprint Backlog

The video below [duration: 04m:02s], explains the diferences between the Product Backlog and CIPSA Sprint Backlog. For better experience, plug-in your earphones and go full-screen HD. 

Closing Remarks 

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 Sprint Backlog.

References

[1] *NEW* Certification Course: Certified In Practical Scaled Agile (CIPSA), Satya Narayan Dash 

[2] Scrum at Scale: CIPSA Sprint Backlog Vs. Team Sprint Backlog, by Satya Narayan Dash 

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

[4] New Practical Scaled Agile Framework – The CIPSA Framework Guide, , by Satya Narayan Dash