As organisations grow, so does the complexity and scope of their projects. Evaluating how well the management practices adapt to these changes is essential.

This is where the Project Management Self-Assessment comes in.

We could ask many more questions, but the following 50 questions are designed specifically to get to the heart of matters across various project management aspects in the simplest way possible.

Who Is It For?

The assessment is for anyone needing to audit the status of a single or multiple projects. This could be for;

Project Manager
Project Sponsor
PMO Office
Project Assurance / Auditor
External Consultant

Benefits of the Project Managment Self-Assessment

Informed Decision-making: The assessment gives you a snapshot of your current capabilities, providing data to make strategic decisions.
Alignment with Business Objectives: Understanding your maturity level can ensure that your project management processes align with the organisation's goals and objectives.
Risk Mitigation: A higher maturity level often corresponds to a more robust risk management process, reducing the likelihood of project failure.
Resource Optimisation: The assessment helps identify areas where resources can be better allocated, thus optimising costs.
Continuous Improvement: Regular assessments can monitor progress over time, offering insights into areas where improvement efforts have succeeded and more work is needed.
Competitive Edge: A mature project management process can be a selling point for stakeholders and clients, making you a more attractive business partner.

How to Use the Assessment

The project management self-assessment is divided into various sections, each concentrating on different aspects of project management such as Planning, Execution and Control, Team Management, and more.

Decide on which sections you want to explore. For example, if you want to evaluate only the running of a single project, then you may wish to skip the first section on Governance and Strategy.

You'll find questions with multiple-choice answers ranging from 'Ad-hoc' to 'Optimised,' corresponding to the maturity scale of 1 to 5.

After answering all questions, tally your results to get an overall picture of your project management maturity. For each section, total the scores and divide by the number of questions to give you your average.

This indicates your overall maturity in that area and can serve as a foundation for improvement strategies.

Scoring Matrix

Section	# Questions	Section Score	Average Score
Governance & Strategy	5
Planning	9
Execution & Control	5
Change Management	5
Monitoring & Reporting	5
Risk & Issue Management	4
Communication & Stakeholder Management	3
Vendor & Supplier Management	4
Team Management & Culture	4
Benefits & Value Management	2
Documentation & Tools	2
Post-Project Evaluation	2
Totals	50

What To Do With The Results

After completing the assessment, you will have a set of results indicating your organisation's level of maturity in various aspects of project management. But what next? The real value lies in understanding and acting upon these insights.

Understanding Your Score

After completing the assessment and tallying up your results, you'll find yourself placed on a maturity scale from 1 (Ad-hoc) to 5 (Optimised) across various dimensions of project management.

This score offers an initial understanding of your organisational capabilities and maturity in specific areas.

Plotting on a Radar Chart

I recommend plotting your results on a radar chart using Excel or any other data visualisation tool.

A radar chart offers a graphical representation of your maturity levels across different categories.

How to Create a Radar Chart in Excel:

Input Data: Enter your results into an Excel spreadsheet, listing the categories (e.g., Governance, Resource Planning, Risk Management, etc.) in one column and their corresponding maturity levels in the next.
Select Data: Highlight the data, go to the 'Insert' tab, and select 'Radar Chart' from the 'Charts' group.
Customise: Once the chart is generated, you can customise it by adding titles, gridlines, and labels for better readability.

Detailed Analysis

Identify Strengths and Weaknesses: Evaluate which areas received higher scores and which need improvement. This will help focus your organisational resources where they are most needed.
Gather Stakeholder Input: Present the results to key stakeholders for further insights. Their perspectives could provide additional depth to the interpretation of the results.

Actionable Steps

Develop a Roadmap: Based on your maturity level, develop a roadmap for elevating your project management practices. Include specific, measurable, achievable, relevant, and time-bound (SMART) goals.

Here's a link to a strategy document that might help.

Resource Allocation: Determine the resources—personnel, time, or capital— necessary to implement this roadmap.
Training and Development: If the assessment indicates a knowledge gap, invest in targeted training and development programmes.
Tech Investments: For organisations that score lower in the use of project management tools and software, consider adopting advanced technology solutions.
Review and Adjust: Set periodic milestones to review your progress. Make data-driven adjustments to your roadmap and continue to measure your maturity.

Continuous Improvement

Remember that reaching a higher level of maturity is not a one-time achievement but an ongoing process.

Regular reassessments are essential to ensure that the strategies implemented yield the desired results and to make course corrections as needed.

The Maturity Model Explained

Successful project management is not merely the sum of individual actions but is an amalgamation of cohesively managed processes and practices.

As organisations strive to improve their project management capabilities, understanding the current state of their maturity can be instrumental.

The Project Management Maturity Assessment aims to provide an actionable framework to evaluate an organisation's proficiency in different dimensions of project management. This assessment uses a scale of 1 to 5, as outlined below:

1) Ad-hoc

At this level, an organisation has no formalised project management processes. Project success is often a result of individual effort rather than a repeatable, institutionalised process. Risks are not well-managed, and there is limited documentation to capture lessons learned or best practices.

2) Basic

The organisation has initiated the process of establishing project management standards but lacks consistency. Basic project documentation may exist, and some team members might be familiar with project management principles. However, these practices are not yet integrated into a standard operating procedure.

3) Structured

Here, the organisation has a set of defined project management processes in place. There is a structured approach to planning, executing, and monitoring projects. Templates and tools may be utilised to maintain consistency. However, these processes are not necessarily optimised and may not cover all areas of project management effectively.

4) Managed

The organisation not only has structured processes in place but also manages and reviews these processes regularly for effectiveness. Quality control measures are integrated, and there is a focus on continuous improvement. Stakeholders are well-engaged, and project management practices are aligned with the organisation's strategic objectives.

5) Optimised

At this pinnacle level, the organisation exhibits advanced project management practices characterised by a culture of continuous improvement. Data-driven decision-making is the norm, and there are mechanisms for real-time monitoring and adjustments. The organisation not only excels in project execution but also captures and utilises lessons learned for future projects effectively.

The Assessment Questions

Section 1: Governance and Strategy

How is project governance established in your organisation?

There is no formal project governance; we manage as we go.
We have some guidelines, but they are not strictly followed.
We have a well-defined project governance framework that is applied to most projects.
Our governance framework is reviewed periodically for effectiveness.
Governance is continuously improved and tailored for each project based on real-time metrics.

How are project roles and responsibilities defined?

Roles and responsibilities are generally unclear.
There are some role definitions, but they are not always communicated effectively.
Roles and responsibilities are well-defined and communicated.
Roles are not just defined but also assessed for effectiveness.
Roles and responsibilities are dynamically adjusted based on project needs and performance data.

How well are projects aligned with organisational strategy?

Projects are often executed without a clear link to organisational strategy.
Some projects align with the strategy, but this is not consistent.
Projects are primarily aligned with organisational strategy.
Strategic alignment is regularly reviewed.
Every project is rigorously vetted for strategic alignment and monitored throughout its lifecycle.

How is strategic planning integrated into project selection?

There is no standard process for project selection.
Projects are often chosen based on immediate needs rather than strategic fit.
A formal project selection process exists, ensuring alignment with strategic goals.
Strategic alignment is a critical metric in our project selection criteria.
Our project selection process is refined continually through performance feedback and alignment metrics.

How are projects prioritised in your portfolio?

There is no formal portfolio management; projects are selected ad hoc.
Some projects are prioritised based on urgency rather than overall strategic fit.
We have a portfolio management process that aligns projects with organisational strategy.
Our portfolio management is optimised regularly for strategic fit.
Portfolio management is a dynamic process using real-time data to allocate resources optimally.

Section 2: Planning

How is project scope defined in your organisation?

Scope is not formally defined; we work based on general requirements.
We attempt to define scope but often face issues with scope creep.
A well-defined scope document is developed for most projects.
Our scope documents are reviewed and approved by all relevant stakeholders.
Scope is continuously adjusted and optimised through stakeholder feedback and project metrics.

Is the defined scope aligned with project objectives and deliverables?

Alignment between scope and objectives is generally unclear.
There's some alignment, but it's not systematically checked.
We make sure that the scope is aligned with objectives during planning.
Scope-objective alignment is regularly reviewed during project execution.
Real-time data ensures ongoing alignment between scope, objectives, and deliverables.

How do you break down project work into tasks and sub-tasks?

Tasks are divided ad-hoc without a structured approach.
We use a basic list or to-do list to manage tasks.
A detailed Work Breakdown Structure (WBS) or equivalent is developed for most projects.
Our WBS is subject to periodic review and adaptation.
WBS is dynamically updated, drawing upon project performance metrics and stakeholder feedback.

How are project schedules created and maintained?

Schedules are created but rarely followed.
Basic timelines are set but often require adjustments.
Project schedules are developed using scheduling software and are generally adhered to.
Schedules are reviewed and updated periodically, incorporating lessons learned.
Our scheduling process uses real-time data to adapt and optimise project timelines dynamically.

How are project resources identified and allocated?

Resource allocation is mostly ad-hoc, often leading to resource crunches.
We have a basic idea of what resources are needed but no formal allocation plan.
Resources are formally identified, and an allocation plan is created.
Resource allocation plans are reviewed and adjusted based on project progress.
Resource allocation is dynamically optimised based on real-time project needs.

How is resource availability managed?

We often find out about resource unavailability at the last minute.
Some resource tracking is in place, but it is not always accurate.
Resource calendars are maintained and regularly updated.
Availability data is used to make strategic project decisions.
Resource availability is managed in real-time, allowing immediate reallocation.

How are human resources trained and prepared for the project?

Training is often skipped due to time constraints.
Basic onboarding is conducted, but not all team members are adequately prepared.
A formal training programme ensures team members are ready for their roles.
Training effectiveness is reviewed, and training programmes are updated.
Training is continuously adapted based on project needs and individual performance.

How are resource conflicts resolved?

Resource conflicts are usually resolved on the fly, causing delays.
Some prioritisations are made, but conflicts often arise.
A defined process exists for resolving resource conflicts.
Lessons from past conflicts are used to improve resource management.
Predictive analytics help preempt resource conflicts and facilitate seamless management.

How is resource performance monitored?

There is no systematic monitoring of resource performance.
Some key resources are monitored, but not comprehensively.
Performance metrics for all resources are tracked.
Resource performance data is analysed to make improvements.
Real-time performance metrics inform resource optimisation strategies.

Section 3: Execution and Control

How are tasks and activities managed during project execution?

Tasks are managed on the fly, often leading to delays and bottlenecks.
We have a simple task list, but it's not always up-to-date.
Tasks are managed using project management software and regularly updated.
Performance metrics for tasks are reviewed to ensure optimal execution.
Tasks are adaptively managed using real-time data, and adjustments are made proactively.

How is task delegation handled?

Delegation is sporadic and often based on availability rather than skill.
Some thought is given to task delegation, but it's not consistent.
Tasks are delegated based on skillsets and project needs.
The effectiveness of task delegation is reviewed and improved upon.
Delegation is fine-tuned based on performance metrics and team feedback.

How are project budgets managed?

Budgets are often overrun, with little to no monitoring.
We set budgets but don't always stick to them.
Budgets are planned, monitored, and generally well-controlled.
Budget performance is reviewed periodically, and learnings are applied to future projects.
Budgets are optimised in real-time based on performance metrics.

How are budget deviations handled?

Deviations are usually discovered too late to take corrective actions.
We try to manage deviations but lack a systematic approach.
We have a process for managing and correcting budget deviations.
Budget deviations are analysed to improve future budgeting.
Real-time data allows immediate action on budget deviations, minimising their impact.

How is the quality of project deliverables ensured?

Quality is often compromised due to a lack of proper controls.
Some quality checks are performed, but they are not comprehensive.
Quality control processes are in place and followed.
Quality metrics are reviewed, and improvements are made continually.
Quality control is proactive and predictive, based on data analytics and historical performance.

Section 4: Change Management

How are changes integrated into the ongoing project?

Changes are implemented without much planning, causing disruptions.
Changes are incorporated but often lead to delays or increased costs.
A formal change control board or process integrates changes smoothly.
The integration of changes is regularly audited for efficiency and effectiveness.
Change integration is automated and optimised in real-time based on project data.

How is the team prepared for changes?

The team is usually unaware of changes until they are implemented.
The team is notified of changes but given little time to adjust.
The team is well-informed and trained to handle changes.
Training and communication strategies for change are regularly updated.
Advanced tools provide the team with real-time updates and training for changes.

How are project metrics adjusted following changes?

Metrics are rarely adjusted to account for changes.
Metrics are sometimes updated but not always accurately.
Metrics are revised to reflect the impact of the change.
The metric adjustment process is audited and improved over time.
Metrics are dynamically and automatically updated when changes occur.

How are change risks managed?

Risks introduced by changes are generally not managed.
Some risk assessment is done, but not comprehensively.
Risks arising from changes are identified and mitigated.
Risk mitigation strategies for changes are reviewed and optimised.
Predictive analytics are used to manage risks introduced by changes proactively.

How is change performance monitored and reviewed?

There is no formal review of the impacts of changes.
Some review occurs, but it lacks depth and follow-through.
Changes are reviewed against initial expectations and lessons are documented.
Change performance reviews contribute to a knowledge base for future projects.
Real-time analytics monitor the impact of changes, allowing for immediate refinements.

Section 5: Monitoring and Reporting

How are performance metrics defined and utilised?

We do not have formal performance metrics for projects.
Metrics are defined but seldom used for decision-making.
Key performance indicators (KPIs) are defined, monitored, and utilised in most projects.
Performance metrics are reviewed and refined regularly.
Metrics are dynamically adjusted based on real-time project needs and performance data.

How is project performance communicated?

There is no structured communication of project performance.
Performance is occasionally discussed but not systematically reported.
Regular performance reports are generated and disseminated.
Performance reports are tailored to different stakeholder needs.
Real-time dashboards provide all stakeholders with current performance insights.

How is project progress tracked?

Progress tracking is ad-hoc, often leading to surprises.
We use basic methods to track progress, but they are unreliable.
A systematic approach to progress tracking is in place, using project management tools.
Progress tracking methods are reviewed and refined periodically.
Real-time tracking and predictive analytics are used to address issues preemptively.

How are project issues identified and managed?

Issues are typically addressed when they become critical.
We try to manage issues as they arise but lack a formal process.
Issues are identified and managed through a defined process.
Lessons learned from issue management are integrated into project processes.
Predictive analytics are used to identify potential issues before they occur.

How are project outcomes evaluated?

Outcomes are seldom evaluated in a structured manner.
We sometimes conduct a post-mortem, but lessons are not systematically applied.
A formal evaluation is conducted at the end of each project to assess outcomes.
Project outcomes are evaluated against initial goals, and lessons are applied to future projects.
Continuous evaluation occurs throughout the project, adjusting goals and expectations in real-time.

Section 6: Risk & Issue Management

How is Risk Identification managed?

Risks are generally not identified until they become issues.
Some risks are identified but not formally documented.
Risks are systematically identified and documented.
Risk identification is an ongoing process and is reviewed regularly.
Advanced tools and methods, like predictive analytics, are used for real-time risk identification.

How is Risk Analysis conducted?

Risk analysis is usually skipped or conducted informally.
Risks are somewhat analysed but lack quantification.
Formal methods, like SWOT or PESTLE, are used to analyse risks.
The risk analysis process is continually updated with project learnings.
Real-time data analytics are used for continuous risk assessment.

How is Risk Mitigation and Response managed?

Mitigation plans are usually made on the fly when risks occur.
Some generic mitigation strategies are in place but are not tailored to specific risks.
Detailed mitigation and response plans are developed for identified risks.
Past mitigation efforts are reviewed to improve future risk management.
Automated workflows and AI tools implement risk mitigation strategies in real-time.

How is Issue Resolution conducted?

Issues are generally resolved reactively, without a formal process.
A basic issue log exists, but the resolution lacks a structured approach.
Issues are systematically logged, and resolution plans are developed.
The effectiveness of issue resolutions is reviewed and used for continuous improvement.
Advanced tools are used to predict issues before they occur, enabling preemptive resolutions.

Section 7: Communication and Stakeholder Management

How is Internal Communication managed?

Internal communication is sporadic and unstructured.
Basic communication channels exist, but there's no formal plan.
A documented communication plan guides internal communication.
The effectiveness of internal communication is regularly reviewed.
Advanced tools and platforms are used for real-time internal communication.

How is External Communication managed?

External communication is often reactive and lacks planning.
External communication has some structure, but it's not comprehensive.
A formal plan outlines how and when to communicate with external parties.
Data is collected on the effectiveness of external communication for future improvement.
Automated workflows and dashboards enable seamless external communication.

How is Stakeholder Engagement conducted?

Stakeholder engagement is inconsistent and often ad-hoc.
Stakeholders are identified, but engagement is minimal.
A stakeholder engagement plan is followed, including regular check-ins.
Stakeholder feedback is actively sought and used to improve engagement.
Advanced analytics monitor stakeholder sentiment and adjust engagement strategies accordingly.

Section 8: Vendor and Supplier Management

How is Vendor Selection carried out?

Vendor selection is ad hoc with minimal criteria.
Some basic criteria are used for selecting vendors but are not comprehensive.
A formal vendor selection process exists, including vetting and performance analysis.
Vendor selection processes are regularly reviewed for effectiveness.
Advanced tools are used for real-time market analysis and vendor selection.

How is Supplier Relationship Management handled?

Relationships with suppliers are not actively managed.
There is some level of supplier engagement, but it lacks a formal structure.
A documented strategy guides supplier relationship management.
Supplier performance is regularly evaluated to foster long-term relationships.
Advanced analytics tools monitor supplier performance and adjust strategies in real-time.

How is Contract Management executed?

Contracts are often informal or poorly managed.
Contracts exist but aren't actively managed or enforced.
A formal contract management process is in place, including compliance checks.
Past contracts are reviewed to improve future contract management.
Automated systems handle contract compliance and renewal processes.

How is the Performance and Quality Assessment of vendors handled?

Assessment of vendor performance and quality is seldom done.
Basic assessments are carried out but lack depth and follow-through.
Comprehensive, periodic evaluations are performed on vendor quality and performance.
The assessment metrics and methods are continuously refined.
Real-time analytics are used for ongoing vendor performance and quality assessment.

Section 9: Team Management and Culture

How is Team Formation handled?

Team members are assigned without clear roles or responsibilities.
Basic roles are defined, but team dynamics are not considered.
A structured process is used to form teams with complementary skills.
Team formation strategies are regularly reviewed and improved.
Advanced analytics are used to optimise team composition in real-time.

How is Conflict Resolution managed?

Conflicts are generally ignored until they escalate.
Some efforts are made to resolve conflicts but are not systematic.
A formal conflict resolution process is in place and followed.
Lessons learned from past conflicts are used for continuous improvement.
Real-time feedback systems are employed to identify and resolve conflicts early.

How are Leadership and Motivation fostered?

Leadership and motivation are not actively cultivated.
Some initiatives like team meetings or basic rewards are used.
A well-defined strategy exists for leadership development and team motivation.
The effectiveness of leadership and motivation strategies is regularly reviewed.
Personalised motivation and leadership plans are adapted based on real-time metrics.

How is Performance Evaluation conducted?

Performance reviews are inconsistent or non-existent.
Basic evaluations occur but lack depth and follow-through.
Comprehensive performance reviews are conducted periodically.
Performance evaluation metrics and methods are continuously refined.
Real-time performance analytics are used for ongoing assessment and feedback.

Section 10: Benefits and Value Management

How is Value Delivery managed?

Value delivery is not measured or considered during project execution.
There is a basic understanding of value, but it's not systematically managed.
A formal process ensures that project execution aligns with value goals.
Value delivery methods are regularly reviewed for effectiveness.
Real-time analytics are used to adjust activities for optimal value delivery continuously.

How is Benefits Realisation conducted?

Benefits realisation is not planned or measured.
Benefits are outlined but are not formally tracked or realised.
A benefits realisation plan exists and is followed through the project life cycle.
Past projects are reviewed to improve benefits realisation in future projects.
Advanced tools track benefits realisation in real-time and adjust strategies accordingly.

Section 11: Documentation and Tools

How are Documentation Standards maintained?

Documentation is often incomplete or missing.
Some documentation exists but lacks standardisation.
A standardised documentation process is in place and followed.
Documentation standards are reviewed and improved periodically.
Advanced tools ensure real-time documentation and compliance with standards.

How are Project Management Tools and Software utilised?

Tools and software are either not used or are used inconsistently.
Basic tools are used but not integrated into a cohesive system.
A suite of project management tools is used for various project activities.
The use of tools is regularly evaluated for effectiveness and efficiency.
Advanced tools with AI capabilities are used for real-time project management.

Section 12: Post-Project Evaluation

How is Project Review and Lessons Learned managed?

Post-project reviews are often skipped or hastily done.
Reviews are done, but lessons learned are not documented.
A formal review process captures key learnings for future projects.
Lessons learned are reviewed and incorporated into an organisational knowledge base.
Automated systems capture learnings in real-time for immediate and future applications.

How is the Post-Implementation Audit conducted?