Book for PMP Exam Prep: I Want To Be A PMP, 2nd Edition – Updated with PMBOK7 Content

I’m pleased to announce the public availability of the book for the Project Management Professional (PMP®) exam preparation, updated with PMBOK7 content. 

'I WANT TO BE A PMP - The Plain and Simple Way to be A PMP',

updated with PMBOK7 Content

The book continues to remain in the second edition, but with this extensive update with respect to PMBOK7 and Process Group Practice Guide. PMBOK7 is added as another management way, i.e., a principle-based approach to manage projects. It’s a separate and dedicate chapter of the book. 

With this update, the I Want To Be A PMP book, is now fully aligned with:

• PMBOK Guide, 7th and 6th editions
• Process Groups (PG) – A Practice Guide from PMI
• Very similar to PMBOK Guide, 6th edition
• Agile Practice Guide from PMI 
• A list of reference books (latest, see here)

Now, few important questions first, which I usually receive while interacting with aspiring PMPs.

Question – 1: Is the PMBOK Guide, 8th edition available? When it'll be effective?

Answer: Yes. It’s available this month – November, 2025. 

It’ll be effective later next year (2026). It’s almost one year away. You’ve sufficient time to prepare for the PMP exam. You need not wait 1 year to prepare.

Question – 2: Why should one go with this book?

Answer: It has the addition of principle-based approach to project management. PMBOK8 has also a principle-based approach. In addition, there are a lot of commonalities with PMBOK8 when you combine PMBOK6 and PMBOK7. Hence, it'll help you going forward.

Question – 3: Is PMBOK7 content coming in the PMP exam in 2024/25?

Answer: I’ve frequently informed that PMBOK7 content in the actual PMP exam is not high! In fact, a recent PMP Success Story confirmed so. Earlier, another PMP Success Story wrote on it. However, it's good to know PMBOK7 content.

Question – 4: Are the courses of PMP 35 Contact Hours and PMP Live Lessons getting updated?

Answer: Yes, both the above courses are being updated now. They will be available with PMBOK7 content.  

--

Now, the PMBOK Guide, 7th edition (PMBOK7) has 12 principles, 8 performance domains along with a number of models, methods and artifacts (MMAs). This book incorporates them with special emphasis on the areas, where you might face questions.

Since the release of I Want To Be A PMP book in 2021 with Agile content (see here), the book has seen multiple success stories. You can read the success stories here. 

Writing a book is not easy. For enabling me to write this book, I want to thank Shreya A S, Ashita Singh, Shalini Pathak, Amodh Sinha, Shivakumar Viswanathan, Varun Amirthakumar, Kumari Varsha Goel, Rohit Kumar Pandey, Bibhuti Bhusan Bagha, Ram Babu, Bhavani Sankar, V Satya Viswanadha Raju, Poornima Nagaraja, Tanushree Bhoi, Prasad Ramamurthy Kadambi, Rahul Nagle, Vinny Dsilva, Kavita Nambiar, Sarayu Gajendra, Shams Ul Haq, Vishwa Deepak Tiwari, Sandip Kumar Nath, Annarao Patil, Sandeep Jacob, Ansuman Mishra, Shubhra Rishi, Adinarayana Murthy Bhuvanagiri, Masood Ahmed, and Lakshmi Narayan Dash.

They not only became PMPs, but also wrote their success stories. Very few people do that. Usually, less than 5% write. But that’s important as they believe, one day, you can be a PMP, too.

The book has also seen continuous internal updates from 2021. 

Key Features - I Want To Be A PMP, 2nd Edition with PMBOK7

• Fully aligned with PMBOK7, PMBOK6, Process Groups – A Practice Guide and Agile Practice Guide.
• A number of Yogic Tips to crack the PMP exam – specifically related to the PMBOK, 7th edition. This includes inputs from the many successful PMP, who have shared their success stories. 
• A number of Revision Tips and Practice Questions to prepare for the PMP Exam. It links back to the various Knowledge Areas (from PMBOK6 and Process Group Guide) and Agile Project Management area (from Agile Practice Guide).
• Chapter-end Practice Questions and Answers, with specific reference to the PMBOK, 7th edition.
• Interaction-diagrams to make you understand with respect to the PMBOK7 content. 
• Highly simplified language. The book focuses on what you need to know for the PMP exam and written in an easily understandable way. 

Overall Content of the Book

• Number of Chapters: 16 (+2)
• Number of Pages: ~1,000 (approx.)
• Excluding pages for questions, number of pages: ~600 (approx.)
• Number of Tips and Revisions: Numerous
• Number of Questions: Numerous
• Updated with latest PMBOK Guide, 7th edition and Process Group Practice Guide
• Price and Access: Please refer to this page (1st book in the list):
• https://www.managementyogi.com/p/books.html

Updated Book Index

To know the breakdown content of the book, please check the below index (partial one). The detailed index is part of the book.

Note: As you can see in the above index, the PMBOK7 content has been highlighted as *** NEW *** with its content towards the end. When you go through the book, you’ll get a deeper understanding of it. 

For price, payment and access, you can refer to the below link:

https://www.managementyogi.com/p/books.html

If you are want to buy or have any queries on  this book, please send a mail to managementyogi@gmail.com. 

PMP Success Stories:

• PMP Success Stories of 2020s
• PMP Success Stories of 2010s

Book  for PMP exam:

• Book for PMP Exam Prep: "I Want To Be A PMP" (2021 Update)

PMP 35 Contact Hours Online Course:

• PMP 35 Contact Hours Online: Full Money Back Guarantee

PMP LIVE LESSONS - Guaranteed Pass:

• PMP LIVE LESSONS: Guaranteed Pass or Your Money Back

Agile on the Fly! Mastering Real-Time Sprint Operations with MS Project Agile (2)

In the first part of this article (read here), we understood the following:

• Our Current Sprint State
• Performing Activate/Inactivate Operation
• Performing Delete Operation
• Performing Add Operation

In this part, we will check certain additional operations, which are crucial as you manage your Sprint hands-on. There are many other operations, which you - the Scrum Master or Product Owner - have to perform in your Scrum project. Detailed, hands-on videos are part of the Mastering MS Project Agile course. See here.

We will start with the modify operation. 

Performing Modify Operation

As you proceed with your Sprint, you are also likely to perform several edit or modify operations, such as duration, resources, start date, and end date, among others. This can be done by simply double-clicking on the Card (work item) in the Current Sprint Planning Board view and changing the necessary fields. 

As shown for the featured item of Create a new user, I first double-clicked on the corresponding card, and then I can change the resources in the popped-up Task Information dialog box. You can change multiple fields with this option. 

You can also select the card, right-click and choose the Information option from the drop-down list to see the Task Information dialog box. 

Performing Move Operation

Not every work item included in the Current Sprint will be completed. It’s highly possible that some of the items are not started or are partially complete. In such a case, the items are to be moved into the next Sprint. This is one of the rules in the Scrum framework (see here). Note that the incomplete feature items don’t count toward velocity (see here). 

To move a work item into the next Sprint, again you can use the Current Sprint Board view. Select the work item (Card) and use the Move to Next Sprint command from the list. 

When you use this command, the item will be moved into the immediate next Sprint, not any other! To be sure, you can verify it in the Sprint Planning Sheet view, which is for all the Sprints in the project. Keep in mind that once a work item is complete, it won’t be visible in the Current Sprint Board or Current Sprint Sheet view. This is because of the Sprint Planning Filter (see here).  

As shown in the above figure, the feature Edit an existing user is now part of Sprint 2. Earlier, it was part of Sprint 1.

As it’s moved into the next immediate Sprint, the board status is maintained as Next up. The % Complete value for this work item will also be preserved. Your team can work on this item in the next Sprint. 

Performing % Complete Change Operation

While the % Complete mapping is done for the various workflow states in the Board, it’s not written on stone. For example, in our case the % Complete Mapping is %, 10%, 50%, and 100% for Sprint Backlog, Next up, In progress and Done, respectively. 

It’s possible that you may want to change this % Complete for a particular work item. This can be done by opening the Task Information dialog box and changing the % Complete value in the General tab. This is shown below. 

As shown, for the work item, I’ve changed the % Complete to 20%, in place of the default 10%. You can cross-check this % complete update in the Current Sprint Sheet view.  

While you changed the % Complete value to 20%, notice that the Board Status is not changed, and it still remains in the Next up workflow state.

Demonstration and Key Points

Now, let’s demonstrate what we have learned so far, along with some key points to remember while adjusting a Sprint in progress. I’ve prepared the below video [duration: 5m: 29s] for this purpose. For the best experience, you may want to go full screen in HD mode and plug in your earphones.

Conclusion

In some of the cases, it’s possible that while performing these operations, resources may be overallocated. You can quickly solve overallocation using the Team Planner view available with MS Project Online Desktop client, which has the Agile features.

Projects, like human beings, are living entities. Just as every human being changes, so does a project. If the environment is high-churn, then humans must rapidly adapt and adopt, and so does a Sprint project.

This article outlines certain key operations to adjust a Sprint project. I hope it gives you the understanding to perform various operations within a Sprint, the confidence to conduct any operation in a Scrum project, and brings value to your work.

--

This article was first published by MPUG on March 14, 2023. This an updated version. 

References

[1] Online Course: Practical Scrum using MS Project Agile, by MPUG.com

[2] Online Course: Mastering MS Project 2019 Agile (Scrum and Kanban), by ManagementYogi.com

[3] Certification Course: Certified Hybrid-Agile Master Professional (CHAMP), by ManagementYogi.com 

[4] Certification Course: Certified In Practical Scaled Agile (CIPSA), by ManagementYogi.com

Agile on the Fly! Mastering Real-Time Sprint Operations with MS Project Agile (1)

A Sprint is a mini-project within a larger Scrum project, and it's usually timeboxed for two to four weeks. Though timeboxed, a number of things can change within these weeks. In fact, adjustment of a Sprint in progress is the norm, not the exception. 

In an environment with rapid changes (see here) in requirements and technological uncertainties, a number of areas such as scope, resources, risk, and even business priorities may change. Agile/Scrum, after all, is all about change. In fact, one of the principles in the Agile manifesto states: Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.

Note: The content of this article has been taken from Mastering MS Project Agile course. See here. It's world's only hands-on, in-depth course to master MS Project Agile.

For a project executed in Agile mode, one can have the following:

• Addition, removal, or modification of work items within a Sprint, i.e., changes to the Sprint Backlog.
• Refinement of Release Plan (see here for release planning), i.e., change in features for the Sprints within a Release.
• Refinement of the (Product) Backlog (see here), i.e., addition, removal, movement, or replacement of backlog items, which can be features or stories.
• Rolling-wave planning (see here) for upcoming Sprints, as the current Sprint draws to a closure, among others.

In this article, we will specifically learn how to adjust a Sprint which is in progress. We will see the following real-time Sprint operations:

• Activate/Inactive Operation
• Delete Operation
• Add Operation
• Modify Operation
• Move Operation
• % Complete Change Operation

If you’re working hands-on with MS Project to manage your Scrum project, these operations are vital to know. So, let's start with our Current Sprint State.

Current Sprint State – Timeline View

The current situation for our Sprint is shown in the Timeline view of MS Project Agile. Our Sprint is of two weeks duration from September 11, 2023 to September 24, 2023.

As shown in the above figure:

• There are 3 items to be delivered: Login to the online trading system, Create a new user, and Edit an existing user, which are 50%, 50%, and 10% complete, respectively.
• The Sprint event of Sprint 1 Planning is 100% complete, along with four Daily Scrums. These are indicated with a tick mark for the events.
• Our status date is September 18, 2023, which is one week after the Sprint begins on September 11, 2023.

As we proceed, we will perform several operations. These are important to know if you are really working in a Project with multiple Sprints. As any real-world Agile practitioner would tell you, all these operations may happen.  

However, before you proceed, there are important instructions you need to know before starting, which are mentioned in the below video [duration: 2m:38s].

Next, let's us see our current Sprint board to understand the status date and various workflow items available in respective workflow states.

Current Sprint State – Current Sprint Board 

The current situation for our Sprint is shown in the Current Sprint Board view. 

As shown, several items are either complete (shown with a tick mark on the Cards) or progressed as on the status date, i.e., one week into the Sprint. 

The % Complete of features and Scrum events for the entire Sprint can be seen in the below Current Sprint Sheet view. You have to add this column.

As shown above:

• The features Login to the online trading system and Create a new user are 50% complete, whereas the feature Edit an existing user is 10% complete. 
• A number of Daily Scrums are complete.
• The Sprint Planning event is also complete.

Now, we will proceed with various operations.

Performing Activate/Inactivate Operation

When you try to inactivate a task in any column state, except in the Sprint Backlog state, MS Project software won’t allow it to function! The reason is simple – you can’t inactivate a work item, which is activated and in progress.  

A work item (or task) can be inactivated by going to the Task tab, then Schedule group, and using the Inactivate command. It’s highlighted in the below figure. 

Now you may be wondering how to inactive such a work item. You have to take it back to the Sprint Backlog state to inactivate. This can be done either in the Current Sprint Planning Board or the Current Sprint Planning Sheet view. 

As you can see, the work item is inactivated because of the column state (Sprint Backlog), and the % completion. 

Performing Delete Operation

While you can’t inactivate an in-progress task, you are allowed to delete it. You can do so by selecting the work item in the column (workflow) state, right-clicking and using the Delete Task command. This is shown below. 

But then the MS Project software will pop up a soft message for you, unlike the hard message shown for inactivation we saw earlier.   

As shown for the selected feature item of Edit an existing user, when the delete command is pressed, a message pops up. This message wants you to confirm that you really want to delete it. 

If you proceed, the work item will be fully removed from all the views. In other words, the backend database completely removes the work item. Hence, be careful! 

Performing Add Operation

This is another operation that MS Project Agile practitioners use. While scope addition during the Sprint is not encouraged, it’s very likely to happen in the real world. Even though you may not want your scope to expand, new tasks related to a feature might come up anyway, and those must be added. 

You can add a new task by going to the Current Sprint Sheet view, right-clicking, and using the Insert Task command. Notice that as you add a new work item, the default Board Status used will be Sprint Backlog. 

You can also add the new work items using the Gantt Chart view or the using the New Task command of the Current Sprint Board view. After you add a new work item and associate the resources (see here) to it, it can be properly visualized in the Current Sprint Board view with the needed fields. This is depicted below.

This article continues into part 2. See here.

In the next part, we have additional operations for a Sprint in progress. 

References

[1] Online Course: Practical Scrum using MS Project Agile, by MPUG.com

[2] Online Course: Mastering MS Project 2019 Agile (Scrum and Kanban), by ManagementYogi.com

[3] Certification Course: Certified Hybrid-Agile Master Professional (CHAMP), by ManagementYogi.com 

[4] Certification Course: Certified In Practical Scaled Agile (CIPSA), by ManagementYogi.com

Practical Scaled Agile (CIPSA) Certification: CIPSA Kanban Backlog – What It Is and What It Is Not!

 

Both the Product Backlog and the CIPSA Kanban Backlog are key artifacts in the CIPSA Kanban Framework. However, from an execution point of view, the real action happens in the CIPSA Kanban Backlog, because it is the CIPSA Kanban Backlog that is executed by the CIPSA Kanban Team.

Product backlog items taken from the Product Backlog are executed by individual Kanban Teams, resulting in a CIPSA Integrated Increment at the end of the release. The following differentiations clearly define the characteristics of the CIPSA Kanban Backlog. 

The content of this article is based on the CIPSA Kanban Framework. See here. 

Exhaustive explanation is part of the CIPSA certification course. See here. CIPSA is world's only Practical Scaled-Agile certification. It supports both Scrum and Kanban.

To read all articles of this series use this link: 
What It's and What It's Not series for CIPSA

CIPSA Kanban Backlog – What It’s and What It’s Not

Among many, the following are some of the top ones:

1. Not Ongoing, but Release-Bound: The CIPSA Kanban Backlog is not a continuous artifact. The CIPSA Kanban Backlog is discarded when the Release ends.

The CIPSA Kanban Backlog is not kept for indefinitely and is not ongoing is nature. When one release is over, it’s discarded and another is taken-up. 

2. Not a Superset, but a Subset: The sum of all CIPSA Kanban Backlogs across Releases is not equal to the Product Backlog. The CIPSA Kanban Backlog is a smaller, Release-specific subset.

There will be multiple releases while using the CIPSA Kanban Backlog. The sum of all CIPSA Kanban Backlog across releases doesn’t equal to the Product Backlog. It’ll always remain a subset of the Product Backlog. See here to learn more.

3. Not Just Tasks, but also Meta-Events: The CIPSA Kanban Backlog does not only hold work items. The CIPSA Kanban Backlog also includes CIPSA Meta-Events.

Other than the work items, the meta-events included in the CIPSA Kanban Backlog can be CIPSA Kanban Planning, CIPSA Daily Stand-ups, CIPSA Kanban Review, and CIPSA Kanban Retrospective.

4. Not Self-Directed, but Facilitated: The CIPSA Kanban Backlog is not managed without guidance. The CIPSA Kanban Backlog is facilitated by the Principal Flow Master (PFM).  

While the CIPSA Kanban Team owns the CIPSA Kanban Backlog and the team-members execute the tasks (from the individual Team Backlog), it’s not without guidance. The PFM provides the necessary guidance. See the PFM video here. 

5. Not Isolated, but Dependency-Aware: The CIPSA Kanban Backlog does not ignore inter-team needs. The CIPSA Kanban Backlog allows inter-team dependencies to be noted and tracked.

The inter-team dependencies, i.e., the dependencies across the individual Kanban Teams are noted in the CIPSA Kanban Backlog. With right software tool(s), it’s highly useful. 

CIPSA Kanban Backlog – Summary Table

The summary table is shown below.

Final Words

I believe the above differentiations will bring a lot of clarity regarding the CIPSA Kanban Backlog. Detailed explanations will be part of the CIPSA certification course.

Want to experience it hands-on? Become a CIPSA. It’s world’s only Practical Scaled Agile certification.

Among many things, you’ll learn:

• How to build the CIPSA Kanban Backlog?
• How to associate with single- or multi-Releases?
• How to go with both CIPSA Kanban Backlog and Team Kanban Backlogs?
• What are the various ways to assign resources at Scale?
• When, why and how to schedule CIPSA Kanban Backlog related events?

--

CIPSA – What It's and What It's Not Series:

All Articles in What It's and What It's Not - CIPSA

CIPSA Sample Videos and Questions:

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

[2] CIPSA Video Playlist (Complete Playlist)

CIPSA Sample Questions:

[1] CIPSA Certification Sample Questions (Part - 1)

[2] CIPSA Certification Sample Questions (Part - 2)

CIPSA Certification:

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

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

[3] New Practical Scaled Agile Framework – The CIPSA Framework Guide

[4] A Close Look at the CIPSA Kanban Framework – Practical, Hands-on Kanban at Scale

[5] The CIPSA Framework Clock - A Unique Way

Practical Scaled Agile (CIPSA) Certification: CIPSA Sprint Backlog – What It Is and What It Is Not!

While both the Product Backlog and the CIPSA Sprint Backlog are key artifacts in the CIPSA Scrum Framework, the real action happens with the CIPSA Sprint Backlog. It’s the CIPSA Sprint Backlog which gets executed by the CIPSA Team.

The product backlog items taken from the Product Backlog are executed by individual Scrum Teams and a CIPSA Integrated Increment is given at the end of the Sprint. The below differentiations clearly inform the characteristics of the CIPSA Sprint Backlog. 

The content of this article uses the CIPSA Scrum Framework. Similar ones will be applicable to the CIPSA Kanban Framework. 

To read all articles of this series use this link: What It's and What It's Not series for CIPSA. 

CIPSA Sprint Backlog – What It’s and What It’s Not

Among many, I've outlined the following ones for your understanding. Exhaustive explanation is part of the CIPSA certification course. See here.

1 Not Tasks, But Value: The CIPSA Sprint Backlog is not just a list of tasks or line items. The CIPSA Sprint Backlog can contain features, user stories and tasks. 

The CIPSA Sprint Backlog goes beyond a simple task list and focuses on delivering customer and business value. It includes features, user stories, and tasks to ensure a value-driven approach to sprint planning and execution. 

Remember the execution of this backlog finally leads to the CIPSA Integrated Increment. See here.

2. Not CPO-Owned, But Team-Owned: The CIPSA Sprint Backlog is not managed by the Chief Product Owner. The CIPSA Sprint Backlog is managed by the CIPSA team. See here.

Unlike the Product Backlog, the CIPSA Spring Backlog is managed and owned by the CIPSA team. In other words, it’s a collaborative one by the individual Scrum teams. The oversight is provided by the Principal Scrum Master (PSM). See here.  

3. Not Static, But Evolving: The CIPSA Sprint Backlog is not static or fixed. The CIPSA Sprint Backlog can evolve during the Sprint. 

The CIPSA Sprint Backlog is dynamic and can adapt as the Sprint progresses. It allows flexibility to respond to change and emerging tasks or insights. Sometimes, it's highly possible that new tasks can come-up.

4. Not Performance, But Progress: The CIPSA Sprint Backlog is not about measuring the individual team performance. The CIPSA Sprint Backlog is for checking the progress towards the CIPSA Sprint Goal.

The CIPSA Sprint Backlog is used to track progress toward the CIPSA Sprint Goal, not to evaluate individual Scrum Team performance. The focus is on collective delivery, not on individual Team metrics.

5. Not Kept, But Discarded: The CIPSA Sprint Backlog is not going to be retained throughout the project. The CIPSA Sprint Backlog will be discarded at the end of the Sprint.

The CIPSA Sprint Backlog is a temporary one and it's discarded at the end of the Sprint. Its value lies in guiding current work and finally delivering the Integrated Increment.

6. Not Backlog-Led, But Goal-Led: The CIPSA Backlog items do not drive the CIPSA Sprint Goal. The CIPSA Sprint Goal drives the work items in the CIPSA Sprint Backlog.

The CIPSA Sprint Backlog is shaped by the CIPSA Sprint Goal, not the other way around. The CIPSA Sprint Goal is in alignment with the Product Goal (see here). Work items are selected and executed to achieve the CIPSA Sprint Goal, ensuring purpose-driven progress.

Did you properly read the last (previous) one? 

It’s an important one to note. The Product Goal drives “what” will constitute the Product Backlog. Similarly, the CIPSA Sprint Goal drives “what” will constitute the CIPSA Sprint Backlog. The meta-events are added to finalize the backlog.

CIPSA Sprint Backlog – Summary Table

The summary table of what we have learned so far is shown below.

Final Words

I believe the above differentiations will bring a lot of clarity regarding the CIPSA Sprint Backlog. Remember, this is where the real action happens!

Recently, a successful CIPSA informed hands-on learning with .mpp solution files has been invaluable. You can read the CIPSA Success Story.

Want to experience it hands-on? Become a CIPSA practitioner – part of the world’s only practical scaled agile framework.

Among many things, you’ll learn (hands-on):

• How to build the CIPSA Sprint Backlog?
• How to break down backlog items in a proper way?
• How to estimate the items in the CIPSA Sprint Backlog?
• What are the various ways to assign resources?
• When to schedule CIPSA Sprint Backlog related events?
• When and where to include CIPSA meta-events?

CIPSA – What It's and What It's Not Series:

All Articles in What It's and What It's Not - CIPSA

CIPSA Sample Videos:

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

[2] CIPSA Video Playlist (Complete Playlist)

CIPSA Sample Questions:

[1] CIPSA Certification Sample Questions (Part - 1)

[2] CIPSA Certification Sample Questions (Part - 2)

CIPSA Certification:

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

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

[3] New Practical Scaled Agile Framework – The CIPSA Framework Guide

[4] Understanding the CIPSA Scrum Framework – Practical, Hands-on Scrum at Scale

[5] The CIPSA Framework Clock - A Unique Way

Unleash Your Agile Spirit For Scaling – Be a CIPSA

ManagementYogi's Certified In Practical Scaled Agile (CIPSA) course embodies a dynamic and transformative spirit, captured vividly in the latest trailer (26 seconds). CIPSA is pronounced as 'sip-sa'.

The course is hands-on and deeply practical. It's also highly economical. It allows learners to master Scaled Scrum and Scaled Kanban in a hands-on manner with the needed theory.

The below table shows a brief comparison between CIPSA and other certification. Rating is given for each category based on inputs from CIPSAs. The star rating given is based on a scale where five stars represent the highest and one star, the lowest.

Check the items one-by-one to determine the value.

Whether you're navigating Scrum at Scale or Kanban at Scale, CIPSA equips you to rise above conventional limitations and embrace a new Scaled Agile excellence. It's unique in its approach. 

CIPSA not just a certification – it’s a movement to have real-world learning and applicability, which seriously lacks in every other Scaled Agile certification. Rest of the scaled agile certifications are not at all practical, but only theory and more theory. 

To really learn Agile scaling, consider becoming a CIPSA. It’s worth your money. 

Watch the value of being a CIPSA here. 

To know more about the CIPSA certification course, see here.

For this course, many FAQs have been answered. See here. 

If you have any questions or clarifications, please send an email to managementyogi@gmail.com.

CIPSA Certification Course

• Certified In Practical Scaled Agile (CIPSA) – Practical and Economical

CIPSA Sample Videos

• CIPSA Sample Video List (Choose a Video)
• CIPSA Video Playlist (Complete Playlist)

CIPSA – What It's and What It's Not Series:

• All Articles in What It's and What It's Not - CIPSA

RMP Success Story: Mastering Risk, Not Just the Exam Using ManagementYogi’s RMP 30 Contact Hours – A Practitioner Approach to Success

By Vallabha Chebiyyam, RMP, PMP

Introduction

I’ve been certified Project Management Professional (PMP) from PMI and hence wanted to advance my knowledge, understanding and application of Risk Management in a deeper way. 

Hence, I decided to go with the Risk Management Professional (RMP), which is considered to be valuable in my field of work.

Why ManagementYogi’s RMP 30 Contact Hours

The RMP 30 contact hours program from Management Yogi gives you a practitioner-first approach and it’s an exam-true program. It blends PMI-RMP exam alignment with field-grade techniques. 

With this contact hours course, I believe I received a clean path for not only my exam, but also subsequent application. 

RMP 30 Contact Hours Course: Key Features

Management Yogi’s RMP 30 Contact Hours stands out for a practitioner-first structure with concise videos that move from concept to application to short practice. The course maintains a strong governance lens around thresholds, reserves, authority, and change control, and its exam-style scenarios reflect PMI wording and decision patterns. 

The topics that helped me most were data quality assessment before qualitative analysis, response strategy trade-offs across threats and opportunities, and clear reserve policies with drawdown rules. 

This course covers the advanced content fully:

• Expected Monetary Value (EMV) Analysis 
• Decision Tree Analysis (DTA)
• Earned Value Management (EVM)
• Sensitivity Analysis with Tornado Charts
• Various Probability Distributions
• Selecting appropriate distributions such as Triangular, BetaPERT, and Lognormal
• Correlation in Risk Management
• Monte Carlo Analysis and its interpretations with percentiles and drivers

In addition, it covers the areas of the PMBOK Guide, 7th edition and 6th edition with special emphasis on Risk Management. It covers:

• Agile Management considering risks
• Hybrid Management considering risks 
• Various associated Risk Artifacts
• Risk Attitude Spectrum 

Own Study for the RMP Exam 

For practice, the combination of chapter-end questions for retention, full-length exams for pacing, and new items aligned to current standards, PMBOK 7 and 6, and agile and hybrid references were effective. Hence, I used and practiced them all. 

While studying, I found the below ones most useful:

• Quantitative analysis with many techniques outlined above
• Plan and implement risk responses 
• Practical tool snapshots that map insights into scheduling platforms like Primavera or Microsoft Project

These made my workplace adoption straightforward.

The formula sets are concise and usable for exam preparation and day-to-day work, and the revision tips throughout the course and checklists were genuinely helpful for my final reviews. 

Contact Hours Assessment

The assessment for the 30 contact hours was fair, aligned to the content, and served as a clear consolidation of learning rather than a surprise test. Post the assessment, I received the completion certificate.  

Final PMI-RMP Exam

After receiving the contact hours certificate, I went for RMP application fill-up and submitted the application. Post approval, I took the exam in Canada and successfully cleared the exam on 27th September, 2025.

Conclusion 

I want to apply my learnings in my profession and field work. 

Brief Profile: Vallabha Chebiyyam, RMP, PMP 

Assistant Project Manager: I’m working as a management and leadership professional with an engineering background and is based out of Canada. 

RMP Live Lessons - Guaranteed Pass:

• RMP Live Lessons Course - Guaranteed Pass or Your Money Back

RMP 30/40 Contact Hours Online:

• RMP 30/40 Contact Hours Online - Full Moneyback Guarantee

Book for RMP Exam:

• New Book for RMP Exam Prep: I Want To Be A RMP, 2nd Edition (Updated)

RMP Success Stories:

• RMP Success Stories from Management Yogi

Upcoming Webinar: From Chaos to Control – Managing Risks with Primavera P6

In the realm of a project, certainty is a rare, though a welcome, guest. A project, which is a temporary endeavor, unfolds within a landscape filled with ambiguities, changing conditions with unforeseen twists and turns.

Such things are the norms, not the exceptions. Risk, then, is not an intruder, but a native of this terrain!

Risk Management in a Project

Project management rises in this uncertain landscape as it tries to bring certain order and structure amidst turbulence, sometimes even chaos. Project management is the steady hand that tries to sketch order onto the fog of uncertainty. While doing so, Project Managers (PMs) must court risk, not shun it. For to manage projects is to manage its risks! It’s not a separate, but an indispensable function.

It's the job of the PM to anticipate the tremors before the project ground is shaken and to reap rewards when the sun shines upon the project terrain. For to address risks without any anticipation of rewards, is not a wise act. In other words, whether the project is a gentle stream or a turbulent sea, the PM must know the language of risks and risk management.

Thus, when a project management software tool offers the intelligence to navigate and address risks, it becomes more than a software. It becomes a partner because of its embedded risk management capabilities, which can in turn empower PMs to lead with clarity, confidence and conviction. 

In my upcoming webinar, we will exactly do that with Primavera P6 software tool, which provides certain risk management capabilities to you – the Project or Portfolio Manager. 

Webinar Agenda

We will discuss the followings:

• Live demonstration of a project with risks.
• Working with both threats and opportunities.
• Determining the risk score.
• Applying risk responses (strategies).
• Face-to-face questions and answers (Q&As)

Event Details

• Registration: https://mpug.com/events/managing-risks-with-primavera-p6
• Tool Used: Primavera P6 Pro (Learn more here)
• Software Version: Primavera P6 R24.x, the latest one (see here)
• Date: 15th October, 2025, Wednesday
• Time: 9:30 PM IST (India); 12 PM ET (US)
• Duration: 1 hour

Update: The event has been rescheduled to 15th October, 2025.

Registration is closed. The event has concluded.

Primavera P6 Pro Course:

• Primavera P6 Pro Live Lessons

FAQs – Primavera P6 Pro Course:

• Frequently Asked Questions - Primavera P6 Pro Live Lessons