The CIPSA Framework – A Simple Clock View

The Certified In Practical Scaled Agile (CIPSA) is a very simple framework with hands-on applicability and full demonstrative usage of scaling using either Scrum or Kanban at the team level. In this post, I’ll outline the CIPSA Framework in a clock view.

The CIPSA Framework Clock

The below figure informs the CIPSA Framework Clock, or simply, the CIPSA Clock. 

As shown in above figure and as it happens in a clock, we have the following activities associatd with each clock pointer.

Clock Pointer 1: Establish the Product Goal.

Here the Product Goal is created by the Chief Product Owner (CPO). 

Clock Pointer 2: We have Cross-team Backlog Refinement. 

The Cross-Team Backlog Refinement happens. The Product Goal drives the top ordered items (content) of the Product Backlog.

Clock Pointer 3: With CIPSA Planning, Build the CIPSA Backlog.

The CIPSA Backlog will be built by the CIPSA Team. The CIPSA Backlog will have the CIPSA Goal, which is in alignment with the Product Goal.

Clock Pointer 4: In the Sprint/Release, Execute the Work Items.

For scaled Scrum, in the Sprint, the work items are executed. For scaled Kanban, in a release – based on cadence – the work items will be executed.

Clock Pointer 5: Conduct the CIPSA Daily Stand-ups.

The CIPSA Daily Stand-ups happen in the Sprint or Release and the needed representatives from the CIPSA team participate.

Clock Pointer 6: Remove issues, impediments and mitigate risks.

This happens through the Sprint or Release.

Clock Pointer 7: Ensure Continuous Integration.

Integration is not a one-time work, but happens continuously cutting across the individual teams under the CIPSA Team.

Clock Pointer 8: Have the CIPSA Integrated Increment.

The CIPSA Integrated Increment is the sum of all work coming from the individual teams.

Clock Pointer 9: Conduct the CIPSA Review.

This meta-event is the second to last one and the CIPSA Integrated Increment is presented here.

Clock Pointer 10: Update the Product Backlog. 

The Product Backlog can be updated based on the feedback received in the CIPSA Review meeting.

Clock Pointer 11: Conduct the CIPSA Retrospective.

This is the final meta-event for improvements. 

Clock Pointer 12: Repeat.

As the pointer name tells, repeat the work!

Video Explanation: The CIPSA Framework Clock 

The below video explains the CIPSA framework clock or simply the CIPSA clock. The duration is around 5 minutes [5m:32s]. Put your earphones (or buds) and go full HD in order to have a better experience. 

==

In summary, that’s what happens in the CIPSA Framework for scaling Scrum or Kanban teams. Yes, that’s all! 

Isn’t it a very simple framework to learn and use? 

Scaling frameworks need not be complex, heavy on documentation, but low on practical applicability and usage. In fact, for any real Scaled Agile practitioner, it should be the opposite! 

However, worldwide, not a single framework tells how to scale with software tools. If at all they do, it becomes very cumbersome with multiple tools and high complexities. 

The CIPSA Framework is not complex, but enables you to deliver work, which is complex!

The CIPSA Framework Clock demonstrates scaling in a simple manner. To know more on the CIPSA Framework, you can download the CIPSA Framework Guide.

References

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

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

[3] Scrum at Scale: Multiple Sprints and Synchronized Scaled Sprints with MS Project Agile, by Satya Narayan Dash

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