While both the Product Backlog and the CIPSA Sprint Backlog are key artifacts in the CIPSA Scrum Framework, the real action happens with the CIPSA Sprint Backlog. It’s the CIPSA Sprint Backlog which gets executed by the CIPSA Team.
The product backlog items taken from the Product Backlog are executed by individual Scrum Teams and a CIPSA Integrated Increment is given at the end of the Sprint. The below differentiations clearly inform the characteristics of the CIPSA Sprint Backlog.
The content of this article uses the CIPSA Scrum Framework. Similar ones will be applicable to the CIPSA Kanban Framework.
To read all articles of this series use this link: What It's and What It's Not series for CIPSA.
CIPSA Sprint Backlog – What It’s and What It’s Not
Among many, I've outlined the following ones for your understanding. Exhaustive explanation is part of the CIPSA certification course.
1 Not Tasks, But Value: The CIPSA Sprint Backlog is not just a list of tasks or line items. The CIPSA Sprint Backlog can contain features, user stories and tasks.
The CIPSA Sprint Backlog goes beyond a simple task list and focuses on delivering customer and business value. It includes features, user stories, and tasks to ensure a value-driven approach to sprint planning and execution.
Remember the execution of this backlog finally leads to the CIPSA Integrated Increment. See here.
2. Not CPO-Owned, But Team-Owned: The CIPSA Sprint Backlog is not managed by the Chief Product Owner. The CIPSA Sprint Backlog is managed by the CIPSA team. See here.
Unlike the Product Backlog, the CIPSA Spring Backlog is managed and owned by the CIPSA team. In other words, it’s a collaborative one by the individual Scrum teams. The oversight is provided by the Principal Scrum Master (PSM). See here.
3. Not Static, But Evolving: The CIPSA Sprint Backlog is not static or fixed. The CIPSA Sprint Backlog can evolve during the Sprint.
The CIPSA Sprint Backlog is dynamic and can adapt as the Sprint progresses. It allows flexibility to respond to change and emerging tasks or insights. Sometimes, it's highly possible that new tasks can come-up.
4. Not Performance, But Progress: The CIPSA Sprint Backlog is not about measuring the individual team performance. The CIPSA Sprint Backlog is for checking the progress towards the CIPSA Sprint Goal.
The CIPSA Sprint Backlog is used to track progress toward the CIPSA Sprint Goal, not to evaluate individual Scrum Team performance. The focus is on collective delivery, not on individual Team metrics.
5. Not Kept, But Discarded: The CIPSA Sprint Backlog is not going to be retained throughout the project. The CIPSA Sprint Backlog will be discarded at the end of the Sprint.
The CIPSA Sprint Backlog is a temporary one and it's discarded at the end of the Sprint. Its value lies in guiding current work and finally delivering the Integrated Increment.
6. Not Backlog-Led, But Goal-Led: The CIPSA Backlog items do not drive the CIPSA Sprint Goal. The CIPSA Sprint Goal drives the work items in the CIPSA Sprint Backlog.
The CIPSA Sprint Backlog is shaped by the CIPSA Sprint Goal, not the other way around. The CIPSA Sprint Goal is in alignment with the Product Goal (see here). Work items are selected and executed to achieve the CIPSA Sprint Goal, ensuring purpose-driven progress.
Did you properly read the last (previous) one?
It’s an important one to note. The Product Goal drives “what” will constitute the Product Backlog. Similarly, the CIPSA Sprint Goal drives “what” will constitute the CIPSA Sprint Backlog. The meta-events are added to finalize the backlog.
CIPSA Sprint Backlog – Summary Table
The summary table of what we have learned so far is shown below.
.png)
Final Words
I believe the above differentiations will bring a lot of clarity regarding the CIPSA Sprint Backlog. Remember, this is where the real action happens!
Recently, a successful CIPSA informed hands-on learning with .mpp solution files has been invaluable. You can read the CIPSA Success Story.
Want to experience it hands-on? Become a CIPSA practitioner – part of the world’s only practical scaled agile framework.
Among many things, you’ll learn (hands-on):
- How to build the CIPSA Sprint Backlog?
- How to break down backlog items in a proper way?
- How to estimate the items in the CIPSA Sprint Backlog?
- What are the various ways to assign resources?
- When to schedule CIPSA Sprint Backlog related events?
- When and where to include CIPSA meta-events?
CIPSA – What It's and What It's Not Series:
All Articles in What It's and What It's Not - CIPSA
CIPSA Sample Videos:
CIPSA Sample Questions:
CIPSA Certification:
No comments:
Post a Comment
Sign- or Log-in and put your name while asking queries in comments. Any comment is welcome - comments, review or criticism. But off-topic, abusive, defamatory comments will be moderated or may be removed.