Certified In Practical Scaled Agile (CIPSA) Online Course

 

I’m excited and delighted to announce the availability of the Certified In Practical Scaled Agile (CIPSA) Online Course for Scaled Agile practitioners and Management professionals:

CERTIFIED IN PRACTICAL SCALED AGILE (CIPSA) 

It’s a complete video course on Scaled Agile Management. It covers both theory (30%) and practical (70%). Highest emphasis has been given to practical applicability. Though MS Project has been used, any other software tool can be used as the concepts are similar.

There are many Scaled Agile approaches and certifications in the world, but none of them really tells you how to do it in a practical, hands-on manner. CIPSA certification, following the CIPSA framework, is radically different from that perspective.  The CIPSA certification course is in-depth, hands-on, and practical-oriented. Literally, CIPSA (pronounced 'sip-sa') is the only such course, worldwide. It also comes with full money back guarantee. 

A complex, large-sized product will require multiple Teams. Such products have massive scope, big budget, a number of dependencies and above all, require large manpower. Scaling is inevitable in such scenarios. Because a single Product Owner or Scrum Master can’t manage a team of 50 or 70 people. Can they? Hence, scaling is inevitable. 

The CIPSA certification understands this need and is for Scaled Agile Practitioners. Both Scrum and Kanban are used at team-levels. These can be scaled to multiple teams. The meta-events, artifacts, roles and responsibilities also have to scaled. For example, in Scaled Scrum, the CIPSA framework informs about the role of Chief Product Owner (CPO) and Principal Scrum Master (PSM). Similarly, other roles are used in Scaled Kanban. 

This course is highly needed by Scaled Agile practitioners as scaling is truly advanced, and complex. However, the CIPSA framework, on which the CIPSA certification is based is not complex. Rather, it’s used to deliver complex work. 

With the CIPSA certification course, you will know:

• Scaled Scrum Management
• Advanced Scaled Scrum Management
• Scaled Kanban Management
• Advanced Scaled Kanban Management

You learn and work with a number of foundational as well as advanced concepts in Scaled Scrum and Scaled Kanban management: 

• Scaling multiple Scrum or Kanban teams
• Building a Scaled Scrum or Kanban Backlog, i.e., the CIPSA Backlog
• Working with multiple teams and multiple Sprints/Releases (Scrum or Kanban)
• Scaling Scrum Boards or Kanban Boards to manage and track
• Generating CIPSA Integrated Burndown/Burnup Chart (Scrum)
• Generating Integrated Cumulative Flow Diagrams (Kanban)
• And many more.

Because this practical-oriented course, you will see how Scaled Scrum or Scaled Kanban projects are managed with MS Project Agile. 

With this course, you will also have an End Course Exam. On clearing the exam, you get the Certified In Practical Scaled Agile, or in short the CIPSA credential, indicating your mastery over Scaled Agile Management. 

Above all, you’ll know how to do it in the real-world with real scaled projects, because the course is hands-on.

Top Features: Certified In Practical Scaled Agile (CIPSA)

1. Total Video Duration: 11+ hours 
2. Number of Videos: 153 
3. Number of Lessons: 11 (+1) 
4. One full-length Q&A Set: 40 Q&As 
5. Total Exercises (Practical): 80+ [downloadable]
6. End-course exam and credential as a Certified In Practical Scaled Agile (CIPSA).
7. In-depth understanding of Scaled Scrum, Scaled Kanban, Advanced Scaled Scrum, and Advanced Scaled Kanban.
8. Ability to apply the scaling concepts with the Hands-On tool of MS Project Agile.
9. Generate various reports such as CIPSA Integrated Burndown/Burnup Chart, Scaled Kanban Cumulative Flow Diagrams (CFDs), among many others.
10. A large number of exercise and solution files (over 80), which you can download, use and practice.
11. A large number of tips and tricks points to know throughout the course.

Course Breakdown: Certified In Practical Scaled Agile (CIPSA)

• Lesson 1 – Welcome to CIPSA (9 videos): 22m 29s [22 minutes 29 seconds]
• Lesson 2 – Understanding Scaling in Agile (17 videos): 1h 08m 39s
• Lesson 3 – The CIPSA Framework and Practical Scaled Agile (22 videos): 1h 23m 48s
• Lesson 4 – CIPSA – Practical Scaled Scrum (17 videos): 1h 16m 51s
• Lesson 5 – CIPSA – Advanced Practical Scaled Scrum (28 videos): 2h 32m 07s
• Lesson 6 – CIPSA – Practical Scaled Kanban (15 videos): 51m 33s
• Lesson 7 – CIPSA – Advanced Practical Scaled Kanban (24 videos): 2h 06m 33s
• Lesson 8 – CIPSA – Reporting in Practical Scaled Scrum (8 videos): 36m 06s
• Lesson 9 – CIPSA – Reporting in Practical Scaled Kanban (7 videos): 26m 09s
• Lesson 10 – The CIPSA Credential: (5 videos) 14m 57s
• Lesson 11 – Conclusion: (1 video) 03m 07s
• Lesson 12 – All Exercises and Solutions (CIPSA)

The details on it this course, with information on additional features, are available also available at:

https://www.managementyogi.com/p/certified-in-practical-scaled-agile.html 

What is the Certification Offered by the CIPSA Course?

This course comes with an end-exam with a set of questions on Scaled Scrum and Scaled Kanban management. To clear the CIPSA exam, you need at least an 80% score. 

With completion of the course and clearing of the end course exam, you will receive the unique and powerful credential: Certified In Practical Scaled Agile or the CIPSA credential. 

What is Full Money Back Guarantee for the CIPSA certification course?

There are no little tricks, such as – “terms and conditions apply”, “** conditions apply”, “guarantee not applicable if you have done this or that”, as you would have seen in many places. What you see and read here is exactly what you will get.

The premise is simple.

You have six (or three) months and two attempts to clear the CIPSA exam. Give the exam and clear the exam. Be a CIPSA. You WIN. 

If you can’t, I’ll refund your full money. You still WIN because you’ve the entire content free of cost for 6 (or 3) months! This is another WIN for you.

You’ve everything to win with this course, nothing to lose. You’ve entire 6 (or 3) months of access to the course for free, whether you go for the exam or not. It’s not mandatory to give the CIPSA end-course exam.

Note: You can also evaluate the videos before paying any money. Twenty (20) videos will be available for your evaluation, even before your purchase. 

CIPSA–Applicability and Validity

• Theory Used: Practical Scaled Agile Management using Team-Level Scrum and Team-Level Kanban from the CIPSA Framework
• Software Used: MS Project Online Desktop Client (2019/2021/2024)
• Theory Pre-requisites: Minimal Project Management, Scrum and Kanban
• Scaled Agile Pre-requisite: None. You’ll learn with the course.
• Course Duration: 3 or 6 months from the date of purchase
• Price: $119 USD / Rs 9,549 (for 3 months)
                $219 USD / Rs 17,549 (for 6 months)
• Available: From November, 2024
• Primary Format: Video 
• Course Extension: As per your need
  (Price calculation will be pro-rata)
• Status: Available
  (accessible via laptop/desktop)

CIPSA–Detailed Course Breakdown

The detailed course breakdown for the CIPSA certification course is shown below. It details hours of learning, number of videos and various exercise details. You can scroll to see the full content.  

If you want to buy this course or have any questions, please send an email to managementyogi@gmail.com. 

You may also like:

• Introducing Practical Scaled Agile Framework with CIPSA Certification
• The CIPSA Framework Guide, Free to Download, Learn and Apply
• Understanding the CIPSA Scrum Framework – Practical, Hands-on Scrum at Scale
• A Closer Look at the CIPSA Kanban Framework – Practical, Hands-on Kanban at Scale 

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] Introducing Practical Scaled Agile Framework with CIPSA Certification, by Satya Narayan Dash

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

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

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] Scrum at Scale: CIPSA Sprint Backlog Vs. Team Sprint Backlog, by Satya Narayan Dash 

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

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

[4] Scrum at Scale: Managing Multiple Teams and Boards with MS Project Agile, by Satya Narayan Dash, first published by MPUG.com