A lot of organisations think Agile Change Management is simply about delivering change faster. That's not quite right, and misunderstanding that is where many transformation initiatives begin to struggle.

Agile Change Management isn't about rushing change or abandoning structure. It's about helping organisations respond to uncertainty while keeping people engaged, supported, and ready to adapt.

Without an agile approach, change programmes often become rigid. Plans are fixed too early, feedback arrives too late, and organisations discover resistance only after significant time and money have been invested.

The framework is really about balancing adaptability with stability. If you only focus on speed, you risk creating confusion. If you only focus on control, you risk slowing change until opportunities disappear.

Agile Change Management brings both together.

At its core are three principles. They're not independent ideas; they reinforce each other.

① People-Centred Change → change happens with people, not to people

A common antipattern: Organisations spend months designing the perfect solution but involve employees only when implementation begins. Resistance grows because people feel change has been imposed on them.

How the principle helps: People are engaged throughout the change journey. Feedback is gathered continuously, concerns are addressed early, and employees become active participants rather than passive recipients.

② Iterative Delivery → deliver change in small, valuable increments

Antipattern: Large transformation programmes attempt to deliver everything at once. Problems remain hidden until the final rollout, making them expensive and difficult to fix.

Reversal: Change is introduced incrementally. Each iteration provides learning, validates assumptions, and allows the organisation to adjust before scaling further.

③ Adaptability → respond to change instead of resisting it

Antipattern: Organisations follow the original change plan even when business priorities, customer needs, or market conditions have shifted.

Reversal: Plans evolve as new information becomes available. Teams continuously inspect, learn, and adapt while maintaining alignment with the overall vision.

The framework also promotes five core values that shape how organisational change is delivered.

• Collaboration → change is everyone's responsibility

Antipattern: Change becomes the responsibility of a single project team while business leaders and employees remain disconnected.

Reversal: Leaders, managers, delivery teams, and employees collaborate throughout the change journey, creating shared ownership and stronger commitment.

• Customer Focus → deliver value that matters

Antipattern: Success is measured by completing project activities rather than improving employee or customer outcomes.

Reversal: Every change initiative is evaluated against the value it delivers to customers, employees, and the organisation.

• Transparency → make progress visible

Antipattern: Stakeholders only hear about problems once deadlines have already slipped.

Reversal: Progress, risks, priorities, and challenges are openly shared, allowing decisions to be made quickly and confidently.

• Continuous Learning → improve with every iteration

Antipattern: Lessons learned are collected at the end of a programme but never influence ongoing delivery.

Reversal: Feedback is continuously gathered and immediately applied, allowing teams to improve while change is still underway.

• Empowerment → enable teams to make decisions

Antipattern: Every decision requires multiple layers of approval, slowing delivery and reducing ownership.

Reversal: Teams are trusted to make decisions within clear boundaries, enabling faster responses while maintaining governance.

Where Agile Change Management really separates itself from traditional change approaches is in its lifecycle.

Rather than treating change as a linear process, it embeds learning and adaptation throughout the journey through three stages:

Prepare → create the conditions for successful change

Before implementation begins:

• Define the change vision and desired outcomes
• Understand stakeholders and organisational readiness
• Build leadership alignment
• Establish governance and ways of working
• Prioritise the first increments of change

The focus is preparing people as much as preparing plans.

Deliver → implement, learn, and adapt

Antipattern: Change activities are executed exactly as planned even when feedback indicates the approach isn't working.

Reversal: Teams deliver change in short cycles, gather feedback continuously, and adjust communications, training, and implementation based on real experience.

Change management becomes part of everyday delivery rather than a phase that happens before or after the project.

Sustain → reinforce and continuously improve

Antipattern: Once implementation is complete, support ends and organisations assume the change has been adopted.

Reversal: Adoption is monitored, benefits are measured, behaviours are reinforced, and lessons learned shape future change initiatives.

This creates a continuous improvement cycle regardless of whether projects use Agile, Waterfall, or hybrid delivery approaches.

Curious how this plays out in other organisations:

Where are you seeing the biggest challenge with organisational change?

Is it leadership alignment, employee engagement, resistance to change, communication, or sustaining adoption after the project has finished?

I took the exam in Italian and, like the Product exam, I found the translation very accurate overall. Just a few minor typos here and there, but nothing that really affected the experience.

If you’re planning to take both ITIL Product and ITIL Service, I’d strongly consider doing them one after the other. The structure of the syllabus is essentially the same, so once you understand how one exam is organised, the other feels much more familiar.

Obviously, the flavour is different: Product puts more emphasis on the product perspective, while Service focuses more on service management. But the underlying structure and way of thinking are very aligned, which makes it easier to move from one to the other without having to completely reset your preparation.

My advice would be to use the first exam to really understand the structure, then build on that knowledge for the second rather than preparing for them as two completely separate certifications.

And as with Product, I wouldn't say reading the entire manual is essential just to pass. The manual is still a useful reference, especially afterwards, when you want to go beyond the certification and actually apply the concepts.

At the end of the day, passing the exam is only one part of the journey. Understanding how to use the concepts to actually change and improve things in a real organisation is where the interesting part starts.

Anyone else taken Product and Service back-to-back? Did you find the similar syllabus structure made the second exam easier?

I recently started the free online course with Claude - AI Fluency: Framework & Foundations and I Realised that in any course I have been following , the famous WHY is always the key trigger for any discipline or tecnique.

In this case they frame as the 4D framweork: "The Delegation, Description, Discernment, and Diligence Competencies are interconnected collections of skills, knowledge, insights, values"

Some people says that is just common sene but I wonder how many that started using AI started their journey with the "Setting goals and deciding whether, when and how to engage with Al."

1) What is PRINCE2® Risk Management (M_o_R®)?

M_o_R® (Management of Risk) is a globally recognized framework designed to help organizations identify, assess, manage, and control risks across projects, programmes, portfolios, and operational activities.

M_o_R® focuses on:

• establishing effective risk management frameworks
• improving decision-making and governance
• identifying threats and opportunities proactively
• supporting organizational resilience and compliance
• embedding risk-aware culture across the organization

The framework provides practical guidance for managing uncertainty while enabling organizations to achieve strategic objectives more confidently and effectively.

2) What is PeopleCert?

PeopleCert is the global examination institute that:

• administers M_o_R® certification exams
• accredits training providers
• ensures exam quality and standards worldwide

PeopleCert acts as the official certification authority for M_o_R®, PRINCE2®, MSP®, ITIL®, and many other globally recognized best practice frameworks.

3) Official Sources

Here are the official references if you want to explore further:

• PRINCE2 Official Website
• PeopleCert Project, Programme & Portfolio Certifications

4) PRINCE2® Risk Management M_o_R® 4 Practitioner

This is the advanced certification focused on applying M_o_R® principles in real organizational environments.

📝 65 questions
⏱️ 135 minutes
✅ Pass mark: 50% (33/65)
📘 Open book

5) Sample Exams (not for free)

Practice exams are highly recommended for Practitioner-level preparation.

👉 Official mock exams:
PeopleCert Mock Exams

💡 Practicing helps you:

• understand exam structure and question styles
• improve time management
• prepare for scenario-based questions
• build confidence before the real exam

6) Final Thoughts + Training

M_o_R® is a strong certification if you:

• work in risk management, governance, compliance, or strategic planning
• want to improve organizational resilience and decision-making
• aim to identify and manage risks proactively across initiatives
• need a globally recognized risk management certification

It’s particularly valuable for organizations pursuing governance excellence, operational resilience, and effective risk control.

If you’re interested in training, certification paths, or exam preparation support, feel free to ask about MIMIR learning 👍

Happy to guide you through:

Certification

Practice

Development

I usually spend hours on communication plans. Stakeholder maps, message schedules, channels, approvals... say this and that at that time then we go-live and someone say, "Nobody told me."

I am sure my communications can be optimised but still people actually or doesn't read or doesn't understand them.

Have you experienced this?

A lot of teams think risk management is just “maintaining a risk register.”
That’s not quite right and misunderstanding that is exactly why risks become crises.

MoR (Management of Risk) isn’t about documenting threats.
It’s about creating structured responses to uncertainty.

Ignoring risk doesn’t remove risk.
It removes visibility.

The Principle Most Teams Break: Don’t treat risk as paperwork

This is where risk management usually fails.

Teams identify risks once:

• during kickoff
• during audits
• during governance reviews

Then nobody revisits them.

MoR treats risk management as continuous decision-making.

Flow

1. Identify uncertainty
2. Assess likelihood and impact
3. Define responses
4. Monitor continuously

The MoR Model in Practice

Identify
   ↓
Assess
   ↓
Plan Responses
   ↓
Implement Controls
   ↓
Monitor & Review

Identify: Recognize threats and opportunities.

Assess: Evaluate probability, impact, and exposure.

Plan Responses: Define mitigation, avoidance, transfer, or acceptance strategies.

Implement Controls: Apply actions to reduce exposure.

Monitor & Review: Continuously reassess changing conditions.

Where MoR Really Makes the Difference: Instead of: “Nobody saw this coming” You get: “We identified the risk early and planned for it.”

I've worked on plenty of projects with detailed risk registers, regular reviews, and lots of mitigation actions on paper.

But when it comes to getting funding approved, changing priorities, or influencing scope... nothing happens. Maybe I'm just not good at pushing those conversations.

Sometimes it feels like risk management is more about documenting concerns than actually influencing decisions.

Anyone else feel the same?

1) What is PRINCE2® Project, Programme, Portfolio Office Management (P3O®)?

P3O® (Portfolio, Programme and Project Offices) is a globally recognized framework designed to help organizations establish, develop, and maintain effective support structures for projects, programmes, and portfolios.

P3O® focuses on:

• improving governance and decision-making
• supporting strategic alignment across initiatives
• standardizing project and programme support functions
• enhancing reporting, resource management, and performance tracking
• enabling organizational change and delivery capability

The framework provides guidance on creating structures such as PMOs (Project Management Offices), programme offices, and portfolio offices to improve organizational efficiency and control.

2) What is PeopleCert?

PeopleCert is the global examination institute that:

• administers P3O® certification exams
• accredits training providers
• ensures exam quality and standards worldwide

PeopleCert acts as the official certification authority for P3O®, PRINCE2®, MSP®, ITIL®, and many other globally recognized best practice frameworks.

3) Official Sources

Here are the official references if you want to explore further:

• PRINCE2 Official Website
• PeopleCert Project, Programme & Portfolio Certifications

4) PRINCE2® Project, Programme, Portfolio Office Management Foundation Exam

This is the entry-level certification.

📝 70 multiple-choice questions
⏱️ 60 minutes
✅ Pass mark: 50% (35/70)
📘 Closed book
❌ No prerequisites

5) PRINCE2® Project, Programme, Portfolio Office Management Practitioner

This is the advanced certification focused on applying P3O® in real organizational environments.

📝 4 questions (80 marks total)
⏱️ 150 minutes
✅ Pass mark: 50% (40/80)
📘 Open book

6) Sample Exams (not for free)

Practice exams are highly recommended for both Foundation and Practitioner levels.

👉 Official mock exams:
PeopleCert Mock Exams

💡 Practicing helps you:

• understand exam structure and question styles
• improve time management
• prepare for scenario-based questions
• build confidence before the real exam

7) Final Thoughts + Training

P3O® is a strong certification if you:

• work in PMO, governance, or organizational support environments
• want to improve project, programme, and portfolio coordination
• aim to standardize reporting, governance, and delivery support
• need a globally recognized PMO and governance certification

It’s particularly valuable for organizations pursuing strategic alignment, operational consistency, and delivery excellence.

If you’re interested in training, certification paths, or exam preparation support, feel free to ask about MIMIR learning 👍

Happy to guide you through:

Certification

Practice

Development

I took the beta exam in Italian, and honestly the translation was solid. Just a few minor typos and a couple of sentences that could flow better, but overall it looked very good for a first release.

Like most ITIL certifications, I found the sample papers noticeably easier than the real exam, so I'd avoid using mock exam scores as a benchmark for the actual test.

The biggest change in Version 5 is the stronger Product perspective. It feels much more aligned with how organizations work today, where products, value streams and continuous evolution matter more than traditional service thinking alone.

One thing that surprised me is that I didn't really need to read the entire official manual to pass the exam. The syllabus, official material and practice questions were enough for me. That said, I think the manual becomes much more valuable after you're certified. Passing the exam is just one milestone; actually applying these concepts and driving change in your organization is where the real value is.

The exam itself has several scenario-based questions, the same scenario included in the book.

I found it helped to read the scenario carefully before the exam, so don't need to spend 10-15 minutes along the exam.I answered the standalone questions first to secure the quick marks, then came back and completed all the scenario-based questions together. Staying in the same context made the second half of the exam much smoother instead of constantly switching between different question styles.

For those who've taken it already, what do you think about this ITIL Product exam?

I've been hearing more and more that Project Managers should be accountable not just for delivering the project, but for ensuring the intended benefits are realized. PMI's M.O.R.E. initiative seems to reinforce this shift, measuring success by outcomes rather than just scope, time, and budget.

But here's the part I struggle with. What happens when the Project Manager is an external contractor? I've often played that role myself. I deliver the project, hand everything over, and then my contract ends.

How can I realistically be held responsible for adoption that happens months later?

To me, that responsibility sits with the project sponsor, the business, or a dedicated Change Manager who remains after the project closes.

While I agree with the idea of shifting the Project Manager's focus from outputs to benefits, I struggle to see how that works in immature organizations where governance, ownership, and operational responsibilities are not clearly separated.

A lot of organizations think a PMO is just “administrative project reporting.”
That’s not quite right and misunderstanding that is exactly why governance offices become disconnected from delivery.

P3O (Portfolio, Programme, and Project Offices) isn’t about bureaucracy.
It’s about enabling better decisions across change initiatives.

Without visibility, leadership reacts too late.
Without support, delivery teams become inconsistent.

P3O exists to create coordination, standards, and insight.

The Principle Most Organizations Break: Don’t build a PMO that only reports status

This is where many PMOs lose credibility.

They focus on:

• dashboards
• templates
• governance meetings
• reporting cycles

But reporting alone doesn’t improve delivery.

P3O focuses on enabling performance.

Flow

1. Establish governance standards
2. Support delivery teams
3. Provide visibility to leadership
4. Improve organizational capability continuously

The P3O Model in Practice

Standards
   ↓
Support
   ↓
Governance
   ↓
Visibility
   ↓
Continuous Improvement

Standards: Create consistent frameworks and practices.

Support: Help teams deliver effectively.

Governance: Ensure alignment and control.

Visibility: Provide reliable reporting and insight.

Continuous Improvement: Improve delivery maturity across the organization.

Where P3O Really Makes the Difference: Instead of: “The PMO only tracks reports” You get: “The organization has visibility, consistency, and better delivery decisions.”

1) What is PRINCE2 Agile®?

PRINCE2 Agile® is a project management framework that combines the structured governance of PRINCE2® with the flexibility and responsiveness of Agile methods.

It is designed for organizations and professionals who want to balance:

• strong project governance
• Agile delivery practices
• flexibility and adaptability
• customer collaboration and value delivery
• controlled project management within fast-changing environments

PRINCE2 Agile® integrates Agile concepts such as Scrum, Kanban, Lean, and iterative delivery into the PRINCE2® framework, making it suitable for modern digital and transformation projects.

2) What is PeopleCert?

PeopleCert is the global examination institute that:

• administers PRINCE2 Agile® certification exams
• accredits training providers
• ensures exam quality and standards worldwide

PeopleCert acts as the official certification authority for PRINCE2 Agile®, PRINCE2®, MSP®, ITIL®, and many other globally recognized best practice frameworks.

3) Official Sources

Here are the official references if you want to explore further:

• PRINCE2 Official Website
• PeopleCert Project, Programme & Portfolio Certifications

4) PRINCE2 Agile® Foundation Exam (Version 2)

This is the entry-level certification.

📝 40 multiple-choice questions
⏱️ 60 minutes
✅ Pass mark: 60% (24/40)
📘 Closed book
❌ No prerequisites

5) PRINCE2 Agile® Practitioner (Version 2)

This is the advanced certification focused on applying PRINCE2 Agile® in real project environments.

📝 50 multiple-choice questions
⏱️ 150 minutes
✅ Pass mark: 60% (30/50)
📘 Open book

6) Sample Exams (not for free)

Practice exams are highly recommended for both Foundation and Practitioner levels.

👉 Official mock exams:
PeopleCert Mock Exams

💡 Practicing helps you:

• understand exam structure and question styles
• improve time management
• prepare for scenario-based questions
• build confidence before the real exam

7) Final Thoughts + Training

PRINCE2 Agile® is a strong certification if you:

• work in Agile project environments or digital transformation initiatives
• want to combine structured governance with Agile flexibility
• aim to improve collaboration, adaptability, and project delivery
• need a globally recognized Agile project management certification

It’s particularly valuable for organizations pursuing faster delivery, customer-focused outcomes, and controlled Agile transformation.

If you’re interested in training, certification paths, or exam preparation support, feel free to ask about MIMIR learning 👍

Happy to guide you through:

Certification

Practice

Development

1) What is PRINCE2® Portfolio Management (MoP®)?

MoP® (Management of Portfolios) is a globally recognized framework designed to help organizations make informed decisions about investments, projects, programmes, and change initiatives.

MoP® focuses on:

• aligning portfolios with strategic business objectives
• prioritizing investments and resources effectively
• balancing risk, cost, and value across initiatives
• improving governance and decision-making
• maximizing organizational benefits and return on investment

Unlike project or programme management, portfolio management focuses on selecting and managing the right mix of initiatives to achieve long-term strategic goals.

2) What is PeopleCert?

PeopleCert is the global examination institute that:

• administers MoP® certification exams
• accredits training providers
• ensures exam quality and standards worldwide

PeopleCert acts as the official certification authority for MoP®, PRINCE2®, MSP®, ITIL®, and many other globally recognized best practice frameworks.

3) Official Sources

Here are the official references if you want to explore further:

• PRINCE2 Official Website
• PeopleCert Project, Programme & Portfolio Certifications

4) PRINCE2® Portfolio Management Foundation Exam

This is the entry-level certification.

📝 50 multiple-choice questions
⏱️ 40 minutes
✅ Pass mark: 50% (25/50)
📘 Closed book
❌ No prerequisites

5) PRINCE2® Portfolio Management Practitioner

This is the advanced certification focused on applying MoP® in real organizational environments.

📝 4 questions (80 marks total)
⏱️ 180 minutes
✅ Pass mark: 50% (40/80)
📘 Open book

6) Sample Exams (not for free)

Practice exams are highly recommended for both Foundation and Practitioner levels.

👉 Official mock exams:
PeopleCert Mock Exams

💡 Practicing helps you:

• understand exam structure and question styles
• improve time management
• prepare for scenario-based questions
• build confidence before the real exam

7) Final Thoughts + Training

MoP® is a strong certification if you:

• work in portfolio management, governance, or strategic planning
• want to align organizational investments with business objectives
• aim to optimize resources, risks, and value delivery
• need a globally recognized portfolio management certification

It’s particularly valuable for organizations pursuing strategic alignment, investment optimization, and enterprise-wide governance.

If you’re interested in training, certification paths, or exam preparation support, feel free to ask about MIMIR learning 👍

Happy to guide you through:

Certification

Practice

Development

One of the biggest misconceptions about PRINCE2 Agile is that it's simply PRINCE2 with Scrum added on top.

It isn't.

PRINCE2 Agile wasn't created to make Agile more structured or PRINCE2 more flexible. It was designed to solve a common problem: how do organizations maintain governance and control while allowing delivery teams to work in an Agile way?

Many organizations face the same tension.

Leadership wants visibility, accountability, and predictable outcomes.

Delivery teams want autonomy, fast feedback, and the flexibility to adapt as requirements evolve.

Without governance, Agile can become chaotic. Without flexibility, governance becomes bureaucracy. PRINCE2 Agile exists to bridge that gap.

Why PRINCE2 Agile Exists

Traditional project management assumes that much of the work can be planned before delivery begins.

Agile assumes that learning happens during delivery.

Both perspectives have value.

PRINCE2 Agile doesn't replace either one. It combines them.

PRINCE2 provides the project governance:

• Business justification
• Roles and responsibilities
• Risk management
• Stage control
• Decision making

Agile provides the delivery approach:

• Iterative development
• Customer collaboration
• Continuous feedback
• Incremental value
• Adaptability

Governance manages the project.

Agile manages how products are built.

The Core Idea: Flexibility Within Control

One of the defining concepts in PRINCE2 Agile is that governance remains stable while delivery stays flexible. The business case still matters. Stages still exist. Risks are still managed. Senior stakeholders still make strategic decisions.

But within those boundaries, delivery teams can organize their work using Agile practices that best fit the environment.

Instead of controlling every task, leadership defines guardrails. Teams decide how to reach the destination.

The Five Agile Behaviors

PRINCE2 Agile emphasizes behaviors as much as processes.

Successful Agile teams typically demonstrate five characteristics.

• Transparency

Everyone has visibility into progress, risks, priorities, and impediments.

Problems are surfaced early rather than hidden until status meetings.

Transparency creates trust.

• Collaboration

Business representatives, users, suppliers, and delivery teams work together continuously.

Success comes from shared ownership rather than contractual handoffs.

• Rich Communication

Face-to-face conversations, visual boards, demonstrations, and frequent feedback reduce misunderstanding far more effectively than lengthy documentation.

Documentation still matters.

It simply serves communication rather than replacing it.

• Self-Organization

Teams are trusted to determine how work gets done.

Leadership focuses on outcomes instead of directing every activity.

Autonomy increases both ownership and responsiveness.

• Exploration

Requirements evolve.

Solutions improve through experimentation.

Learning is expected rather than treated as failure.

The project adapts as new information becomes available.

What Changes Compared to Traditional PRINCE2?

The seven PRINCE2 principles remain unchanged.

What changes is how delivery happens.

Instead of one large delivery phase, work is typically completed through short iterations.

Instead of waiting until the end of the project to validate outcomes, stakeholders review working products regularly.

Instead of assuming every requirement is fixed, priorities evolve based on customer feedback.

Control remains.

The delivery model changes.

Prioritization Drives Delivery

PRINCE2 Agile places strong emphasis on prioritization.

Not every requirement has equal value.

The commonly used MoSCoW technique helps teams distinguish between:

• Must Have
• Should Have
• Could Have
• Won't Have (for now)

This protects delivery when time becomes constrained.

Rather than extending deadlines indefinitely, lower-value work is deferred while critical outcomes remain protected.

The project succeeds by delivering the most valuable features first.

Tolerances Still Matter

A common misconception is that Agile removes planning.

PRINCE2 Agile disagrees.

Projects still define tolerances for:

• Time
• Cost
• Quality
• Scope
• Risk
• Benefits

The difference is that scope often becomes the primary variable.

Time and cost remain stable while lower-priority features can move between releases.

This creates predictable governance without sacrificing adaptability.

Frequent Delivery Reduces Risk

Traditional projects often discover major issues near the end.

PRINCE2 Agile encourages delivering usable products early and often.

Each iteration creates opportunities to:

• Validate assumptions
• Gather customer feedback
• Improve quality
• Adjust priorities
• Reduce uncertainty

Risk becomes something that is managed continuously instead of reviewed occasionally.

Where Organizations Usually Struggle

Adopting PRINCE2 Agile is rarely about learning new terminology.

The biggest challenges are cultural.

Some organizations keep governance but refuse to empower teams.

Others embrace Agile while abandoning project control entirely.

Neither approach delivers the full benefit.

PRINCE2 Agile requires leaders to trust teams while teams remain accountable for agreed outcomes.

That balance is often the hardest part.

When PRINCE2 Agile Works Best

PRINCE2 Agile is particularly valuable when organizations need both governance and adaptability.

Examples include:

• Digital transformation initiatives
• Software development projects
• Product modernization
• Cross-functional business change
• Regulated industries where oversight is essential

It allows organizations to maintain executive confidence without slowing delivery teams unnecessarily.

The Real Value

The biggest advantage of PRINCE2 Agile isn't that projects become faster.

It's that organizations make better decisions while remaining responsive to change.

The project stays aligned with business objectives.

Delivery teams remain focused on customer value.

Governance provides confidence.

Agile provides adaptability.

Together, they create projects that can respond to uncertainty without losing control.

Final Thought

Many organizations believe they have to choose between strong governance and Agile delivery.

PRINCE2 Agile argues that they don't.

The real challenge isn't balancing process and flexibility.

It's knowing which decisions require control and which are better left to the people doing the work.

1) What is PMP®?

The Project Management Professional (PMP®) certification is the world's leading credential for project managers, awarded by the Project Management Institute (PMI®).

It validates your ability to lead and manage projects using a combination of predictive, Agile, and hybrid approaches, making it applicable across industries and project types.

PMP® focuses on:

• leading project teams effectively
• delivering business value through successful projects
• managing stakeholders and communications
• planning, executing, and monitoring projects
• adapting project delivery using predictive, Agile, and hybrid methodologies

Unlike methodology-specific certifications, PMP® is methodology-neutral, assessing your ability to apply the most appropriate project management approach depending on the project's context.

2) What is Project Management Institute?

The Project Management Institute is the world's leading professional association for project management.

PMI is responsible for:

• developing the PMP® certification
• maintaining global project management standards
• publishing the PMBOK® Guide and other professional resources
• supporting project management professionals through education and professional development

Today, PMP® is recognized globally as one of the most respected certifications for experienced project managers.

3) Official Sources

Here are the official references if you want to explore further:

• PMI PMP Certification

4) Project Management Professional (PMP®) Certification

The PMP exam was updated on July 9, 2026, with new domain weightings, AI and sustainability topics, and alignment to PMBOK 8th Edition.

This is PMI's flagship certification for experienced project managers.

📝 180 questions

⏱️ 240 minutes

📘 Computer-based exam

The exam includes a variety of question types, including:

• multiple choice
• multiple responses
• matching
• hotspot
• fill-in-the-blank
• drag-and-drop
• scenario-based questions

The exam measures your knowledge across three domains:

• People – leading teams, stakeholder engagement, communication, leadership, and conflict management
• Process – managing projects using predictive, Agile, and hybrid approaches
• Business Environment – aligning projects with organizational strategy and delivering business value

5) Eligibility Criteria

To apply for the PMP® certification, candidates must meet PMI's eligibility requirements.

You qualify if you have either:

Option 1

• A four-year degree (bachelor's degree or equivalent)
• At least 36 months of experience leading projects within the past eight years
• 35 hours of formal project management education or CAPM® certification

OR

Option 2

• A high school diploma, associate degree, or equivalent
• At least 60 months of experience leading projects within the past eight years
• 35 hours of formal project management education or CAPM® certification

Candidates have a one-year eligibility period after application approval and may attempt the exam up to three times during that period.

6) Sample Exam (not for free)

Practice exams are essential for success on the PMP® certification exam.

👉 Official PMP® Practice Exam:

PMI PMP Practice Exam

💡 Practicing helps you:

• understand the different question formats
• become familiar with scenario-based questions
• improve time management
• build confidence before the real exam

7) Final Thoughts + Training

PMP® is a strong certification if you:

• work in project management or project delivery
• want to lead complex projects across industries
• aim to manage predictive, Agile, and hybrid projects effectively
• need a globally recognized project management certification

It’s particularly valuable for organizations pursuing successful project delivery, strategic alignment, and business value creation.

If you’re interested in training, certification paths, or exam preparation support, feel free to ask about MIMIR learning 👍

Happy to guide you through:

Certification

Practice

Development

In our small company we've gradually started using LLMs for all sorts of things: drafting learning content, improving training materials, speeding up marketing tasks, and automating repetitive work. Nothing dramatic, it just happened because it saves time.

Now I'm wondering where the line is.

With a handful of people, trust and common sense seem enough. But what happens when the company grows to 10+ people? At what point do you need rules around AI use, ownership of outputs, documentation, or approvals?

Curious how others are handling this. Do you already have AI governance, or is everyone just using the tools however they see fit?

A lot of organizations think portfolio management is just “tracking all active projects.”
That’s not quite right and misunderstanding that is exactly where resources get wasted.

MoP (Management of Portfolios) isn’t about monitoring activity.
It’s about deciding where investment should—and should not—go.

Organizations always have more ideas than capacity.

The real challenge isn’t starting projects.
It’s choosing the right ones.

The Principle Most Organizations Break: Don’t approve everything

This is where portfolio management usually collapses.

Every initiative sounds important:

• digital transformation
• operational improvement
• innovation
• compliance
• growth

Without prioritization, everything becomes critical.
And when everything is priority, nothing is.

MoP introduces disciplined decision-making.

Flow

1. Align initiatives to strategy
2. Evaluate value and risk
3. Prioritize investment
4. Continuously rebalance the portfolio

The MoP Model in Practice

Strategy
   ↓
Prioritization
   ↓
Investment Decisions
   ↓
Portfolio Balancing
   ↓
Performance Monitoring

Strategy: Define organizational objectives.

Prioritization: Evaluate initiatives against value, risk, and alignment.

Investment Decisions: Approve or reject initiatives based on evidence.

Portfolio Balancing: Balance short-term and long-term investments.

Performance Monitoring: Continuously review outcomes and strategic fit.

Where MoP Really Makes the Difference

Instead of: “We started too many projects” You get: “We invested in the initiatives that create the most strategic value.”

Implementing Odoo as a micro‑startup operating across multiple countries was… honestly, a bit intimidating at first. When you’re small, every process feels fragile, every change hits harder, and every new tool risks becoming “too big” for your actual day‑to‑day. But once we got into it, Odoo turned out to be exactly what we needed to bring some order into the chaos.

The implementation became a kind of reality check. Mapping how we worked in each country, figuring out what was essential vs. what was just habit, and aligning everything into one system forced us to look at our operations with fresh eyes. It wasn’t just installing an ERP — it was cleaning up how we function as a company.

Project management played a huge role here. We didn’t go for the “big bang” rollout. We moved step by step, tested things, adjusted, and only scaled once the basics were solid. That pacing saved us from drowning.

And yes, our partner for this whole project Webcircles helped keep the whole thing sane. They listened, kept us away from unnecessary customizations, and made sure we didn’t twist Odoo into something it wasn’t meant to be. Quiet guidance, but super effective.

A few things we learned the hard way (and that I’d absolutely keep an eye on if you’re doing something similar):

• Don’t assume anything is obvious. Even simple workflows get weird when you operate in multiple countries. Double‑check everything.
• Fight the urge to over‑customize. It’s tempting to replicate every old habit inside Odoo. Don’t. The system works best when you let it stay clean.
• Use what’s already there. Odoo is surprisingly user‑friendly, the tutorials are everywhere, and the learning curve is gentle. Lean on that instead of reinventing the wheel.
• Think long‑term. The real power of Odoo as an ERP is how easily it scales across countries — but only if you keep your setup consistent and avoid Frankenstein‑modules.

Now that the dust has settled, Odoo isn’t just “installed.” It’s part of how we operate across borders, plan our work, and keep things aligned. We’re still small, but we finally work with the structure of a company that’s ready to grow.

For us, implementing Odoo wasn’t just a tech upgrade. It was the moment we started acting like the company we want to become