Practical Scaled Agile (CIPSA) Certification: The CIPSA Sprint – What It’s and What It’s Not!

 

The CIPSA Sprint is the container meta-event in the CIPSA Scrum Framework. This meta-event will have multiple contained meta-events such as:

  - CIPSA Sprint Planning,

  - CIPSA Sprint Review,

  - CIPSA Sprint Retrospective, and

  - CIPSA Daily Scrum. 

In this article, we know more about a container meta-event, i.e., the CIPSA Sprint. There is another meta-event of CIPSA Cross-Team Backlog Refinement. However, it's not a contained meta-event. You learn more here. 

To reaffirm, CIPSA is world's only Practical Scaled-Agile certification. 

To read all articles of this series use the below link: 

What It's and What It's Not series for CIPSA

Here are seven differentiators in the same format (it’s vs it’s not) for CIPSA Sprint. Exhaustive explanation is part of the CIPSA Certification Course. See here. 

Now, let's dive-in to this contained meta-event.

The CIPSA Sprint Meta-Event – What It’s and What It’s Not

1. Not Isolated Team Cycles, but Synchronized CIPSA Team Cadence.

A CIPSA Sprint is not a separate sprint for each individual Scrum teams. But all teams sprint together with the same start and finish dates in a synchronized way. The CIPSA Sprint meta-event is the encompassing event for all other meta-events and it's the synchronized with the individual Team-level Sprints. 

2. Not Independent Goals, but a Unified CIPSA Sprint Goal.

The CIPSA Sprint is not driven by individual team Sprint Goals, which will be part of the individual Team Sprint Backlogs. Rather, it’s driven by a single shared CIPSA Sprint Goal.

The CIPSA Sprint Goal is aligned with the Product Goal, which is part of the Product Backlog.

3. Not Random Durations, but Consistent Timeboxes.

The CIPSA Sprint is not ad‑hoc or is of uneven duration. It’s a fixed timebox and is usually consistent duration across all teams. There is a reason we have Sprints in Scrum. The same rule applies for the CIPSA Scrum at Scale. 

4. Not Merely Team Task Execution, but Cross‑Team Coordination.

In the IPSA Sprint, it's not merely about individual teams’ execution. It establishes coordination points across teams for planning, reviews, and retrospectives. As stated earlier, the CIPSA Sprint is the container meta-event for other meta-events.

5. Not Individual Increments, but CIPSA Integrated Increment.

The result of a CIPSA Sprint is not fragmented increments coming from individual Scrum team. At the end of the CIPSA Sprint, we get a CIPSA Integrated Increment that is tested, integrated, and valuable.

6. Not only Local Backlog Work, but Product‑Goal Alignment.

A CIPSA Sprint is not focused on completing only team backlog tasks. Rather, it keeps alignment with the long‑term Product Goal through the CIPSA Sprint Goal. In every Sprint, the CIPSA team inches closer to the Product Goal.  

7. Not Siloed Team Scrum Boards, but Integrated CIPSA Team Board.

A CIPSA Sprint is a coordinated effort across teams to deliver value together. It is not separate scrum boards where teams never touch or coordinate dependencies. 

As you proceed with the CIPSA course, you’ll quickly know the tracking at the CIPSA team level is done with the integrated CIPSA Scrum Team Board. This board provides the integrated view for all individual Scrum teams. 

Summary Table – The CIPSA Sprint 

I’ve provided this summary table in conclusion. This is for a quick recap and understanding. 

In Conclusion

Want to know how a CIPSA Sprint is created?

Want to know how multiple CIPSA Sprints can be managed at scale?

Want to know how CIPSA Sprints will be associated with the CIPSA Team?

Want to know how to have contained meta-events with CIPSA Sprint?

Want to know how to synchronize multiple Sprints for the CIPSA team?

Detailed, hands-on explanations is part of the CIPSA certification course. Become a CIPSA – it’s truly worth the investment, as affirmed by CIPSAs worldwide. 

CIPSA Success Stories and Reviews:

[1] From CHAMP to CIPSA – Taking Agile to the Next Level with Scaled Scrum and Scaled Kanban

[2] Scaling Agile: Key Insights from the CIPSA Framework Introduction

CIPSA Sample Videos and Questions:

[1] CIPSA Sample Video List (Choose a Video)

[2] CIPSA Video Playlist (Complete Playlist)

CIPSA Certification:

[1] Scaled Agile Certification Course: Certified In Practical Scaled Agile (CIPSA)

[2] Frequently Asked Questions (FAQs) - CIPSA Certification

Portfolios, Programs and Projects – The NEW Definitions in PMBOK 8th Edition

In the value-delivery system of an organization, all 3 Ps – Portfolios, Programs, and Projects – are integral parts. Interestingly, the definitions of all three have changed in the latest PMI-PMBOK Guide, 8th edition. 

Put differently, in the future it will impact all – aspiring Portfolio Management Professionals (PfMP), Program Management Professionals (PgMP), Project Management Professionals (PMP), and Risk Management Professionals (RMP). Do note that the impact is not immediate, but in the future. 

Definitions are important because they create a clear and shared understanding. Without precise definitions, communication can become confusing or misleading, as people may interpret the same word in different ways. 

In management as in everyday contexts, definitions act as a foundation for learning, discussion, and critical thinking. They help us to organize knowledge, set boundaries for meaning, and ensure that our arguments or explanations are consistent, coherent, clear, and logical. 

In this article, we will explore these concepts in more detail. In organizations, initiatives typically begin at the portfolio level, so we will first examine the definition of a portfolio, followed by those of a program and a project.

Portfolio Definition

Earlier, we had the following definition:

A collection of projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives.

Now, the definition is significantly changed: 

A collection of programs, projects, and operations managed as a group to maximize overall value delivery and achieve strategic objectives, meet mandatory obligations, or generate income streams.

There are a few noticeable differences here:

1. Subsidiary portfolios are no longer mentioned, but in reality, it’ll be there!
2. Overall value maximization is emphasized explicitly.
3. Generation of income streams are introduced for the first time. 
4. In addition, it can be also about meeting mandatory obligations, e.g., legal, regulatory or others.

Above all, the continued focus on achieving strategic business objectives is there.  

The "generation of income streams" part is completely new. In fact, it has been added for the first time. In a portfolio context, an organization might run multiple initiatives that each create different income streams, so they’re not dependent on just one source of revenue.

Let’s take an example. You’re running a set of initiatives in a SaaS (software-as-a-service) start-up to get recurring revenue from software tools. These projects, within a portfolio, are not related, but can have some commonalities such as technology being used and hence, part of a portfolio. 

Program Definition

Earlier, we had the following definition:

A group of related projects, subsidiary programs, and program activities that are managed in a coordinated manner to obtain benefits not available from managing them individually.

Now the definition is changed to: 

A group of related projects and program activities managed in a coordinated manner to obtain benefits not available from managing them individually. 

Here we have one difference:

1. Subsidiary programs are no longer mentioned, but in reality, it’ll be there!

Programs are always about benefits and hence value. In addition, it's coordinated management of program components to deliver benefits. 

Program has a dedicated domain called Benefits Management, where we do benefits analysis, planning, delivery, transition, and finally, sustainment of benefits. The whole idea of having a program is to have coordinated work in order to deliver benefits/value to organization. 

Project Definition

Earlier the definition of the project was:

A temporary endeavor undertaken to create a unique product, service, or result.

Now the definition has changed and it is: 

A temporary initiative in a unique context undertaken to create value.

This is a real change of words here. The differences are:

1. No longer an endeavor, but an initiative.
2. Context has to be unique.

The initiative word confuses many. It need not be the case. 

As I've written here many times at ManagementYogi, an organization's strategic plan is subdivided into a set of organizational initiatives influenced by the market conditions, customer requests, or obligations etc. to be met. 

Next, a number of initiatives are grouped into a portfolio. In other words, a portfolio can contain proposals for various initiatives such as projects, programs, subportfolios, operations etc. It can also encompass already existing projects or programs within an organization. 

In that sense, the definition of a project is perfectly aligned with portfolio and its management. Because a project is indeed is an initiative within a portfolio. 

The other aspect is the uniqueness of context. It’s possible for two projects to involve constructing two identical buildings, but the context can still differ. For example, the location, technology, and resources may vary between these projects. Isn’t that right? 

The most important one is the final aspect of the definition – creation of value. Project is now about creating value by producing tangible and/or intangible deliverables. 

Figurative Representation 

The following figure outlines portfolios, programs, and projects in an organization.

                                 

As shown above, an organization’s vision, mission and strategic objectives are documented in the strategic plan. This plan is subdivided into a set of initiatives. Initiatives are then grouped into portfolios. 

Portfolios of programs and projects in an organization provide the value delivery system. And, as we just learned, all 3 Ps – Portfolios, Programs and Projects – are about creation, enablement and/or maximization of value delivery.

Conclusion

If you've followed my books and/or used my courses, you'll know that I say the following:

Project creates and delivers. Programs coordinates and guides. Portfolio decides and drives.

For more details, check out this article and also Part 2.

By now, you would have noticed that a shift has occurred across all three Ps toward value delivery. I'll change it from the value delivery perspective. 

Project creates and delivers value. Program coordinates to obtain benefits and value. Portfolio maximizes overall value. 

I can also shorten it further and say:

👉 Project creates value. 

👉 Program coordinates benefits/value. 

👉 Portfolio maximizes overall value.

References:

[1] PfMP Live Lessons - Guaranteed Pass or Your Money Back, by ManagementYogi.com

[2] PMP Live Lessons - Guaranteed Pass or Your Money Back, by ManagementYogi.com

[3] RMP Live Lessons - Guaranteed Pass or Your Money Back, by ManagementYogi.com

What Does it Take to Be a PfMP? If it Were Easy, Everyone Would Do it!

Becoming a Portfolio Management Professional (PfMP) from the Project Management Institute (PMI) requires more than just passing an exam. It demands a strong understanding of portfolio management concepts, the right mindset, and consistent preparation. 

PfMP is PMI's highest-level certification. 

Unlike project or program management, portfolio management is strategic in nature and focuses on selecting and governing the right investments for an organization by choosing the right components in a timely manner. 

As I keep saying:

Projects create. Programs guide. Portfolios decide.

At the portfolio-level, you decide the components to take or drop, the investment to make or cancel, and of course, the strategic business objectives to be met.

Your success in the PfMP journey depends on how well you understand the underlying processes, apply concepts in real-world contexts, and prepare with disciplined practice. 

The following key points provides practical guidance to help you approach your PfMP preparation in a structured and effective way.

There are two assumptions: a) Your application has been approved following PMI's panel review. Management Yogi provides support for it. b) You've decided to prepare for and proceed with the PfMP exam.

The following ones are based on my interactions and experiences with certified PfMPs as well as enabling many professionals to become certified PfMPs over the years. 

--

1. Understand the flow of Portfolio Management processes.

In portfolio management, there are multiple process groups, processes as well as knowledge areas. It's easy to get lost with such vast content. 

This is where understanding the flow of processes becomes important. The flow helps you build a mind map and clearly presents the big picture in a narrative way. When you prepare in this manner, you gain a clear understanding of what portfolio management, as illustrated by PMI, is all about.

Most providers of PfMP courses don’t understand this flow, but it is very important. 

2. Learn with hands-on tools whenever you can.

Portfolio management is fundamentally different from program or project management. You need to learn it with a different mindset. 

Using software tools such as Primavera or MS Project adds clarity. With just theory, achieving that clarity is difficult.

In addition, there will be plethora of tools and techniques (T&Ts). Software tools will help you tackle these T&Ts.

3. Use high-quality questions.

In your PfMP exam, questions will be of a high standard. They are situational in nature and will ask what to do next, what you should do, or even, what you should not do! Rote learning will not help. You must understand the concepts.

You can expect confusing, puzzle-like questions. Sometimes they can be frustrating – for example, all choices may seem valid, or the question itself may not be very clear. 

Don’t expect the questions to be grammatically perfect or linearly structured. They are designed to challenge you. They are not testing your grammar or linear thinking, but these:

• Are you truly suitable to be a portfolio manager?
• Can you apply portfolio management concepts in the real-world?
• Are you psychologically prepared to grasp and apply these concepts?
• Can you apply various portfolio management tools and techniques?

These insights come from high-quality questions. If you want low-quality ones, the internet is full of them. Everyone claims to be an expert on the web, but reality is different.

4. Always remind yourself: "There is no shortcut. I've to work for it."

You must truly work hard to become a PfMP. As the saying goes: 

On the highway to success, there are no shortcuts. 

You not only need the required portfolio management and business experience, but also sincere preparation. 

If you expect a magic wand or quick tricks to succeed in days or weeks, you will be disappointed. Again remember, there are no shortcuts. 

5. Choose a truly good and simplified course.

Your chosen course must be good, understandable, and digestible. Because portfolio management is vast, it’ll take time to digest. With the right course, your learning will be effective. Of course, real-world portfolio management experience is also important. 

Online learning is preferred because:

• You can access it anytime, from anywhere in the world.
• You can revise as many times as you want. You can also focus on areas where you are weak or not scoring well.
• You can learn at your own pace without feeling rushed or held back.
• It is usually more cost-effective, saving on travel, food, and accommodation.
• The duration is longer compared to classrooms. You can balance learning with your professional and personal commitments.

With a good mentor, you can ask questions and get them clarified.

The course creator or your PfMP coach plays a significant role in your journey. 

6. Practice, practice and practice.

The old saying “practice makes perfect” is true. The more you practice, the better and more confident you become. This complements the previous one, i.e., a good course.

The tools, techniques, content, explanations should be top-notch and high-quality. Practicing with high-quality material gives you the best value. You’ll also remember more when you practice more. 

7. Have a different mindset – the strategic mindset.

Portfolio management is strategic in nature, whereas program and project management are usually tactical. Portfolios focus on choosing the right work, while projects and programs focus on doing the work right. 

Selecting the right work for an organization is inherently strategic.

Projects and programs deal with execution, whereas portfolio management is more business-oriented. This is where key investment decisions are made. Hence, while going for the PfMP, you need to have a strategic mindset. 

8. All domains are important: Strategic, Governance, Performance, Communication, and Risk.

Your PfMP exam is based on the Examination Content Outline (ECO), not strictly on PMI books, references, or standards. 

The ECO provides the blueprint for the exam.

Unfortunately, many courses follow their own templates without mapping to the ECO domains or tasks. If you prepare this way, you risk failing the exam. 

9. Stay in touch with your coach. 

Throughout your preparation, your coach – most likely the course creator – will be extremely important. He or she will motivate, inspire, and guide you. 

In addition, as I've seen, when you stay in touch, you are more likely to prepare consistently with patience and in the end, it works out better for you.

Some may charge high fees but won’t provide proper support or guidance. In such cases, success becomes difficult. Many also don’t know the exact content needed to be a PfMP!

Your determination matters greatly and there is no substitute for it. Consistent support is also important. 

10. Never give-up.

Success is not final and failure is not permanent. Life itself is a continuous learning process. We learn every day until the end. 

When you understand this, giving up is not an option.

Becoming a PfMP is not easy, and as the tile of this article goes – if it were easy, everyone would do it.

You've a dream to be a PfMP. Pursue that dream. Dreams do come true and many have become PfMP with my PfMP courses and/or PfMP book. Check out few of the PfMP SUCCESS STORIES.

--

There are very few PfMPs in the world, unlike PMPs, which have around 1.5 million certified professionals. In comparison, the number of PfMPs is significantly lower. In fact, it’s not even 1% of the number of PMPs! Yes, not even 1%!

You can now understand the significance of the PfMP certification. There are tens of millions of project professionals worldwide. Only a small fraction pursue the PMP certification. 

Hence, achieving the PfMP places you among the top 1% of the top 1% within PMI’s PPP certifications and gives a boost to your career. It also serves as a strong differentiator in your profile and resume.

ManagementYogi’s PfMP courses have a proven track record, with many candidates successfully becoming PfMP certified. Some even achieve this without holding a single PMI certification beforehand!

These courses and books will help you understand, learn, and apply the required concepts and ultimately become a certified PfMP.

PfMP Exam Courses and Book:

[1] PfMP Live Lessons - Guaranteed Pass or Your Money Back, by ManagementYogi.com

[2] PfMP Exam Prep Online Course with Money-Back Guarantee, by ManagementYogi.com

[3] PfMP Exam Prep Book – I Want To Be A PfMP, First Edition, by Satya Narayan Dash, CIPSA, CHAMP