Two Lean-Agile approaches are popular and widely used at the Team Level – Scrum and Kanban. The CIPSA framework recognizes this and hence, uses both of them. You can choose the approach you want for your organization and can scale using the CIPSA framework.
MS Project Agile is a widely used project-portfolio management software tool with extensive Agile capabilities. It also supports both Scrum and Kanban such as Sprints, Boards related to Sprints as well as Boards and Views related to Kanban.
In this post, we will learn more on CIPSA Scrum Framework.
The CIPSA Scrum Framework
The CIPSA Scrum framework extends the team level Scrum and will have the following artifacts, events and roles (accountabilities).
CIPSA Scrum Artifacts: There are three artifacts:
- Product Backlog,
- CIPSA Sprint Backlog, and
- CIPSA Integrated Increment.
All individual Scrum teams use a single Product Backlog. The Backlog items are distributed across the teams.
A CIPSA Sprint Backlog is built during the CIPSA Sprint Planning event and it's the sum of all work done by individual Scrum teams for the upcoming Sprint.
The third artifact is the CIPSA Integrated Increment, which is the sum of all integrated work from all Scrum teams and is given at the end of (or during) the Sprint.
CIPSA Scrum Meta-Events: There are Six (Meta) Events in CIPSA Scrum framework:
- Cross-Team Backlog Refinement,
- The Sprint,
- CIPSA Sprint Planning,
- CIPSA Daily Scrum,
- CIPSA Sprint Review, and
- CIPSA Sprint Retrospective.
CIPSA Scrum Roles: There are two distinct roles in CIPSA Scrum Framework complementing the accountabilities at the individual team level. They are
- Chief Product Owner (CPO), and
- Principal Scrum Master (PSM).
At the individual Scrum team level, there will be Product Owner and Scrum Master and Developers.
The CIPSA Scrum Framework – Graphical
The CIPSA Scrum framework is shown in the below figure.
The CIPSA Scrum Framework – Interactions
A single Product Backlog with ordered items is continuously refined with cross-team members as part of the Cross-Team Backlog Refinement event. The Product Backlog with the Product Goal is presented by the CPO in the CIPSA Scrum Planning (meta) event of the upcoming Sprint. In this meeting, a CIPSA Sprint Backlog is created with the Product Backlog items that can be delivered by multiple teams in the upcoming Sprint.
While individual Scrum teams are sprinting on their own, the Sprints are synchronized across the Scrum teams.
Post CIPSA Scrum Planning meeting, for each team, an individual team level Sprint Planning event takes place. This results in Team Sprint Backlog, for each team.
Next, each team begins to work on the respective Team Sprint Backlog items. A CIPSA Daily Scrum meeting happens everyday and it’s preceded by individual team-level Daily Scrums for the individual teams.
In the CIPSA Sprint Review meeting, a CIPSA Integrated Increment is presented to the entire CIPSA Scrum team and needed stakeholders. The CIPSA Sprint Review meeting replaces the individual Team Sprint Reviews.
The last event for CIPSA Scrum Framework is CIPSA Sprint Retrospective. Here the CIPSA team reflects on the effectiveness of the CIPSA team as a whole and determines the improvements that can be taken-up. This meeting is preceded by Team Sprint Retrospective, which is specific to the individual teams.
Video: The CIPSA Scrum Framework
The below video [duration: 6m:34s], explains the CIPSA Scrum Framework briefly with the roles, meta-events, and artifacts.
Conclusion
As noted earlier, the CIPSA Scrum Framework extends the team-level Scrum. Hence, the CIPSA Scrum framework and team-level Scrum are in harmony. In fact, most of the events, roles and artifacts followed by Scrum are directly employed in the CIPSA Scrum Framework – but at scale.
The CIPSA Scrum Framework is practical, hands-on and uses a single software tool – MS Project Agile. This is the ONLY such framework in the world! With practical applicability, you have a much better learning, understanding and applicability in your scaled Scrum team or organization.
References
[1] Introducing Practical Scaled Agile Framework with CIPSA Certification
[2] New Practical Scaled Agile Framework – The CIPSA Framework Guide
[3] Scrum at Scale: Multiple Teams and Synchronized Scaled Sprints with MS Project Agile
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.