In the previous post, we learned about:
- Synchronized Sprints in CIPSA
- Stock-Trading System's Product Backlog (single one)
- Planning and Addition of Sprints
- Seggregation of Individual Scrum Teams
Add the Individual Scrum Teams
In this step, we will associate the work items with the respective Scrum teams. This will be decided in the CIPSA Sprint Planning meeting, where the “what” part is decided. Do not confuse this meeting with an individual Team Sprint Planning meeting, which happens later. It’s the CIPSA Sprint Planning, during which the planning is taking place at scale.
To have the work items associated, add a new column into Sprint Planning Sheet view and associate with respective Scrum teams. Next, choose the team from the drop-down list and associate it with respective work items.
Associate the Sprints the Scrum Teams
Our next step is to associate the planned Sprints with the individual Scrum Teams.
To associate the teams with Sprints, select the Sprint column available in the Sprint Planning Sheet view and select the Sprint number from the drop-down list. This is shown in the below figure. While we have planned for five Sprints, our upcoming Sprint is Sprint 1 and each team will Sprint on its own with this Sprint number – Sprint 1.
In the above figure, again, did you notice that all teams will be sprinting on the same Sprint, i.e., Sprint 1?
This is a significant point to understand. There are no separate Sprints for separate teams. Rather the Sprint Planning is happening at the Global Level for all the teams and then we are associating the Sprints with the teams.
An alternative and relatively familiar view for many of you will be the Gantt Chart view. This is depicted in the below figure.
In the above figure, I’ve added three new columns:
- Built-in field of “Sprint” informing the Sprint number.
- Built-in field of “Sprint Start” and “Sprint Finish” which shows that the features across the teams are to be completed within the Sprint duration.
- The custom field of “Team” shows the feature distribution across Scrum teams.
As explained earlier in the first video, the CIPSA Sprint Planning will be succeeded by the individual Team Sprint Planning event and tasks will be further decomposed. When the respective sub-tasks are added, the CIPSA Sprint Backlog will be the sum of all individual Team Sprint Backlogs. This is shown in the below figure.
The above highlighted areas in the figure is the CIPSA Sprint Backlog, consisting of individual Team Sprint Backlogs. This backlog will get progressively built-up with CIPSA Frameworks’ meta events and other events.
Again, the key points to note here are these:
- All Scrum Teams are sprinting on the same Sprint – Sprint 1. But they are executing the work items separately.
- All Scrum Teams are sprinting towards the same CIPSA Sprint Goal, which is in sync with the Product Goal.
- Individual Scrum Teams will have individual Team Sprint Goals, but these goals must be in sync with the CIPSA Sprint Goal.
Demonstration: Scrum at Scale using CIPSA Framework
Let’s have a demonstration of what we have learned so far with our practical scaled approach using Scrum to deliver a product. The below video [duration: 7m:19s] demonstrates such scaling with MS Project Agile. Again, plug-in your headphones to understand with more clarity.
Conclusion *** UPDATED ***
Scaling is complex, but the framework need not be complex. Scaling involves complex cross-team dependency management, collaboration, multi-Sprint management, multi-team tracking, board management, integration of individual team increments and above all, delivering value to the customer or end user. However, with the right practical scaled agile framework – in this case CIPSA, right software tool, much of the heavy lifting can be done.
A big misconception in Agile practitioners’ circles is that MS Project is not at all suitable for Agile at Scale, not just Agile! As we just reviewed in this article, MS Project Agile can effectively be used to scale multiple Scrum Teams with multiple synchronized Sprints and deliver complex products.
The series is concluded.
I welcome your thoughts, comments, and feedback in the comments section below.
--
This article was first published by MPUG.com on September 4, 2024. This is an updated version.
References
[1] NEW Scaled Agile Certification Course: Certified In Practical Scaled Agile (CIPSA)
[2] New Practical Scaled Agile Framework – The CIPSA Framework Guide
[3] Understanding the CIPSA Scrum Framework – Practical, Hands-on Scrum at Scale
[4] Understanding the CIPSA Kanban Framework – Practical, Hands-on Kanban at Scale
[5] The CIPSA Framework Clock - A Unique Way
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.