DTU ProjectLab - User contributions [en-gb]

Project Management Maturity Models

2016-09-26T21:54:20Z

S104809:

== Abstract ==
In being able to make improvements in an organisation, it is key to know both strengths and weaknesses. This also applies to project management which is seen as an extremely important factor in achieving success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness in the market. Project Management Maturity Models (PMMM’s) is a tool for exactly that. The model helps the organisation learn about itself and makes it aware of current strengths and weaknesses. The result is an assessment of which level of maturity the project management in an organisation is currently at. In extend to that, the model provides the basis for a plan to achieve continuous improvements and higher levels of maturity. The models are criticised for being subjective. This is because the assessment is based on humans subjective answers. This article analyses the use and relevance of maturity models in project management. Furthermore the element of managing humans and securing useful results will be discussed. The key elements of the article are as follows;
* Big idea
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** The LKAB Case Study
* Limitations
* Reflections

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Maturity can be described as the organisation's effectiveness. A mature organisation is in position to perform to reach the goals set <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. Today, project management is an important factor in being able to succeed and well performed project management is accounted as a competitive advantage on the market. Typically, the PMMMs consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows <ref name="BRO"> [''Using Maturity Models to Improve Project Management Practice''] '' Brooks, N.; Clark, R. 2009'' </ref>. ;
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the project management execution in the given organisation with PM standards (e.g. PMBOK Guide). The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in its strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

==== Concept ====
The above is a generic description of the idea behind the PMMMs. Firstly, the models did not just appear out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence <ref name="Jud"> [''Project Management Maturity Models: The Silver Bullets of Competitive Advantage''] '' Judgev, K.; Thomas, J. 2002'' </ref>. This was the beginning of development of maturity models. Today, app. 30 PMMMs exist. The models can be divided into three types, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest on the market, is more complex and holistic in its form.

The first type of model is named ''technical delivery process model''. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management performance. The level the organisation is appointed descries the stage that the organisation should now try to reach. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ <ref name="GR"> ["PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?"] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed further. An example of a technical delivery process model is the P3M3 model, which also include portfolio and program management.

The second type of PMMM is named ''project management process model''. This type of model also uses the five level of maturity, though it does so a little differently from the first one. The project management process models take base in five processes within nine knowledge areas in PM <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The five levels in this model are; 1) common language, 2) common processes, 3) singular methodology, 4), benchmarking, 5) continuous improvement <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. As illustrated in figure 1, level 3-5 are meant for continues benchmarking and improvements.

[[File:sofpic2.jpg|600px|thumb|center|Figure 1. Illustration of the five levels of a project management process model <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

The last type is the "organisational models". As mentioned above, this type of model is the newest type of maturity model for use in project management and is a more holistic one, compared to the two types described before. The reason is, that this type of models does not only consider project management performance but all of the organisation's performance. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The idea is, that it is not adequate to improve the project management performance, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. Now, all of the business processes’ maturity levels are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance. This type of PMMM is more nuanced than the first two. Though, it also has a higher demand in time and resources. Whereas some types of models are applicable by the organisation itself, the organisational models might need assistance of consultancy company. [[File:sofpic1.jpg|600px|thumb|center|Figure 2. Result of assessment illustrated in a radar chart <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change <ref name="KOT"> [''Using Kotter's Eight Stage Process to Manage an Organisational Change Program: Presentation and Practice''] '' Pollack, J.; Pollack, R. 2015'' </ref> . The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, maybe tools like PMMM will be taken into use earlier in the process.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves internally. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management, with variations dependent on the type of model. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper.

=== The LKAB Case Study ===
Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> presents a case study in application of PMMM’s. One of the companies in the study is the Swedish mining company, LKAB, primarily working in mining, refining and logistics. The company is 100 percent state owned, has a net turnover of approximately 31 billion SEK and also operates in Norway<ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. The company consists of approximately 4200 employees of which around 100 are employed in the project department, carries out hundreds of project every single year with the assistance of- and corporation with experts from other departments of the company. In 2012 LKAB initiated a maturity assessment of project management within the organisation [F. Backlund et al, 2014]. The assessment was executed by a consultancy company, using a model inspired by the P3M3, which is also described in the Big Idea section in this article. The assessment was based on seven PM processes; Management Control, Benefits Management, Financial Management, Stakeholder Engagement, Risk Management, Organisational Governance and Resource Management <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>.
In practice, the assessment was executed by an electronic (app. 20 minutes’) survey, which was send to the participants by email. The confidential survey was a questionnaire with questions for each PM process including one open question for each of the seven processes. 73 % of the responders answers the questions within the two weeks that was given as a time limit <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>.
Open questions was meant to give the participants the opportunity to express themselves more nuanced. At the time the article of the case study was written, the assessment was finished and somewhat presented to the participants. Though, no exact plan for improvements was conducted. The plan was though to do the assessment every second year <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve level of maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. A lot of elements could be customized for a given organisation, as for instance industry. A well defined PM practise could make it easier to apply the model as it is easier to make it tailored. For instance, if the organisation is based on PRINCE2, a model can be made to fit and in that way it will also be easier to benchmark with other organisations using the same models <ref name="Prince2"> [''PRINCE2 Based Project Management Maturity Model'] '' Chen, J.; Zhang, X.. 2010'' </ref>.

Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

The application of the maturity model in the LKAB case study, was also evaluated by participants afterwards. Some respondents expressed their frustration of the use of the model. They criticized the following use of the assessment, as they pointed out that the results were primarily presented to the employees without any further plan to improve and solve the assessed problems. Also, there was dissatisfaction in terms the difference in engagement in presentation of results amongst the organisation. <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> Leaders of the company, though explained, that such plans and solutions were to be executed, but where simply not finished at the time of the evaluation of the PMMM.
Moreover, the evaluation of the experiences of the responders’ also showed very little enthusiasm and engagement in answering the survey.

Of the other organisations within the studies of Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>, none of them where using maturity models in PM at the time of the studies. One argument was that the application of the model has a very high demand on time and resources. It might not be the execution of the survey as it is simply done electronic, but the preparation and the following result presentation. That maybe makes the models of most relevance for larger PM based organisations.

== Reflections ==
The fact, that approximately 30 different project management maturity models exist, illustrates the common need for improvements in project management in organisations.

Literature research and case studies indicates, that PMMM’s are not a simple tool to apply. Challenges in engaging participants combined with risk of misunderstood questions in the survey clarifies the need for particularly preparation before applying a PMMM. Firstly, the models are based on people’s engagement, thus the quality of the results are dependent on the participants. Thus it is extremely important to make sure, the participants know the relevance of the assessment and their participation i.e. the answers to the questions; Why are we doing this assessment? Why should I spent time to participate? What is the outcome? Etc. If they are able to answer these questions and the answers are positive and make the assessment appear relevant it might be easier for the participants to put a little more effort into their answers as opposed to if the surveys were just giving as extra workload without any further information. If the results reveals big difference between the department, there can be a risk of people only looking out for themselves and their results. That is why it also important to create a common goal by using the PMMMs. If the facilitators of the assessment (or the leaders of the organisation) are able to motivate the participants, they will probably see the survey as an opportunity to express their view on the PM processes.By using supporting tools, this should be doable.

Furthermore, it is important for the organisation to keep working with the maturity after the execution of the survey. The case study shows, that it is far from enough to just show the results of the assessment in numbers. It is very important to know what they want to achieve within PM. This will help reaching a higher level of maturity by setting direction by prioritising actions and starting the change of culture in the organisation [F. Backlund et al, 2014]. Last but not least, organisations using PMMMs should keep making assessments to ensure that the plan is on track and that the organisation keeps improving in terms of project management. In that way it should be possible to benefit from using the Project Management Maturity Models and improve performance by setting targets and changing culture.

== Annotated bibliography ==
Brooks, N.; Clark, R. 2009: Using Maturity Models to Improve Project Management Practice
* This article outlines three author's different maturity models and how to measure maturity in an organisation. Whether it is only based on knowledge or also factors as actions and attitudes.

Grobler, P.J.; Steyn, H. 2006, PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?
* This article explains the need for improvements in PM and outlines the different types of models within project management maturity. The authors concludes that the existing models are still very generic.

Judgev, K.; Thomas, J. 2002, Project Management Maturity Models: The Silver Bullets of Competitive Advantage
* This article focus on how PM has a paramount influence on business success. It also has a description of PMMMs and furthermore a explanation of RBV (however, this is not considered in this article).

Backlund, F.; Chronéer, D.; Sundqvist, E. 2014, Project Management Maturity Models – A Critical Review
*A case study of application of PMMM in swedish construction companies. The case study both concerns the application but also the participants reflections on the use of the model.

Chen, J.; Zhang, X. 2010, PRINCE2 Based Project Management Maturity Model'
* An example of a PMMM. This one is based on the PRINCE2 PM processes, which makes the model tailor-made to an organisation which bases their PM on the PRINCE2. The model is thus based on eight PM processes and eight PM elements.

== References ==

<references />

Project Management Maturity Models

2016-09-26T21:52:49Z

S104809:

== Abstract ==
In being able to make improvements in an organisation, it is key to know both strengths and weaknesses. This also applies to project management which is seen as an extremely important factor in achieving success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness in the market. Project Management Maturity Models (PMMM’s) is a tool for exactly that. The model helps the organisation learn about itself and makes it aware of current strengths and weaknesses. The result is an assessment of which level of maturity the project management in an organisation is currently at. In extend to that, the model provides the basis for a plan to achieve continuous improvements and higher levels of maturity. The models are criticised for being subjective. This is because the assessment is based on humans subjective answers. This article analyses the use and relevance of maturity models in project management. Furthermore the element of managing humans and securing useful results will be discussed. The key elements of the article are as follows;
* Big idea
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** The LKAB Case Study
* Limitations
* Reflections

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Maturity can be described as the organisation's effectiveness. A mature organisation is in position to perform to reach the goals set <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. Today, project management is an important factor in being able to succeed and well performed project management is accounted as a competitive advantage on the market. Typically, the PMMMs consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows <ref name="BRO"> [''Using Maturity Models to Improve Project Management Practice''] '' Brooks, N.; Clark, R. 2009'' </ref>. ;
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the project management execution in the given organisation with PM standards (e.g. PMBOK Guide). The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in its strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

==== Concept ====
The above is a generic description of the idea behind the PMMMs. Firstly, the models did not just appear out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence <ref name="Jud"> [''Project Management Maturity Models: The Silver Bullets of Competitive Advantage''] '' Judgev, K.; Thomas, J. 2002'' </ref>. This was the beginning of development of maturity models. Today, app. 30 PMMMs exist. The models can be divided into three types, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest on the market, is more complex and holistic in its form.

The first type of model is named ''technical delivery process model''. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management performance. The level the organisation is appointed descries the stage that the organisation should now try to reach. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ <ref name="GR"> ["PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?"] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed further. An example of a technical delivery process model is the P3M3 model, which also include portfolio and program management.

The second type of PMMM is named ''project management process model''. This type of model also uses the five level of maturity, though it does so a little differently from the first one. The project management process models take base in five processes within nine knowledge areas in PM <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The five levels in this model are; 1) common language, 2) common processes, 3) singular methodology, 4), benchmarking, 5) continuous improvement <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. As illustrated in figure 1, level 3-5 are meant for continues benchmarking and improvements.

[[File:sofpic2.jpg|600px|thumb|center|Figure 1. Illustration of the five levels of a project management process model <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

The last type is the organisational models. As mentioned above, this type of model is the newest type of maturity model for use in project management and is a more holistic one, compared to the two types described before. The reason is, that this type of models does not only consider project management performance but all of the organisation's performance. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The idea is, that it is not adequate to improve the project management performance, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. Now, all of the business processes’ maturity levels are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance. This type of PMMM is more nuanced than the first two. Though, it also has a higher demand in time and resources. Whereas some types of models are applicable by the organisation itself, the organisational models might need assistance of consultancy company. [[File:sofpic1.jpg|600px|thumb|center|Figure 2. Result of assessment illustrated in a radar chart <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change <ref name="KOT"> [''Using Kotter's Eight Stage Process to Manage an Organisational Change Program: Presentation and Practice''] '' Pollack, J.; Pollack, R. 2015'' </ref> . The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, maybe tools like PMMM will be taken into use earlier in the process.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves internally. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management, with variations dependent on the type of model. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper.

=== The LKAB Case Study ===
Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> presents a case study in application of PMMM’s. One of the companies in the study is the Swedish mining company, LKAB, primarily working in mining, refining and logistics. The company is 100 percent state owned, has a net turnover of approximately 31 billion SEK and also operates in Norway<ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. The company consists of approximately 4200 employees of which around 100 are employed in the project department, carries out hundreds of project every single year with the assistance of- and corporation with experts from other departments of the company. In 2012 LKAB initiated a maturity assessment of project management within the organisation [F. Backlund et al, 2014]. The assessment was executed by a consultancy company, using a model inspired by the P3M3, which is also described in the Big Idea section in this article. The assessment was based on seven PM processes; Management Control, Benefits Management, Financial Management, Stakeholder Engagement, Risk Management, Organisational Governance and Resource Management <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>.
In practice, the assessment was executed by an electronic (app. 20 minutes’) survey, which was send to the participants by email. The confidential survey was a questionnaire with questions for each PM process including one open question for each of the seven processes. 73 % of the responders answers the questions within the two weeks that was given as a time limit <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>.
Open questions was meant to give the participants the opportunity to express themselves more nuanced. At the time the article of the case study was written, the assessment was finished and somewhat presented to the participants. Though, no exact plan for improvements was conducted. The plan was though to do the assessment every second year <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve level of maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. A lot of elements could be customized for a given organisation, as for instance industry. A well defined PM practise could make it easier to apply the model as it is easier to make it tailored. For instance, if the organisation is based on PRINCE2, a model can be made to fit and in that way it will also be easier to benchmark with other organisations using the same models <ref name="Prince2"> [''PRINCE2 Based Project Management Maturity Model'] '' Chen, J.; Zhang, X.. 2010'' </ref>.

Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

The application of the maturity model in the LKAB case study, was also evaluated by participants afterwards. Some respondents expressed their frustration of the use of the model. They criticized the following use of the assessment, as they pointed out that the results were primarily presented to the employees without any further plan to improve and solve the assessed problems. Also, there was dissatisfaction in terms the difference in engagement in presentation of results amongst the organisation. <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> Leaders of the company, though explained, that such plans and solutions were to be executed, but where simply not finished at the time of the evaluation of the PMMM.
Moreover, the evaluation of the experiences of the responders’ also showed very little enthusiasm and engagement in answering the survey.

Of the other organisations within the studies of Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>, none of them where using maturity models in PM at the time of the studies. One argument was that the application of the model has a very high demand on time and resources. It might not be the execution of the survey as it is simply done electronic, but the preparation and the following result presentation. That maybe makes the models of most relevance for larger PM based organisations.

== Reflections ==
The fact, that approximately 30 different project management maturity models exist, illustrates the common need for improvements in project management in organisations.

Literature research and case studies indicates, that PMMM’s are not a simple tool to apply. Challenges in engaging participants combined with risk of misunderstood questions in the survey clarifies the need for particularly preparation before applying a PMMM. Firstly, the models are based on people’s engagement, thus the quality of the results are dependent on the participants. Thus it is extremely important to make sure, the participants know the relevance of the assessment and their participation i.e. the answers to the questions; Why are we doing this assessment? Why should I spent time to participate? What is the outcome? Etc. If they are able to answer these questions and the answers are positive and make the assessment appear relevant it might be easier for the participants to put a little more effort into their answers as opposed to if the surveys were just giving as extra workload without any further information. If the results reveals big difference between the department, there can be a risk of people only looking out for themselves and their results. That is why it also important to create a common goal by using the PMMMs. If the facilitators of the assessment (or the leaders of the organisation) are able to motivate the participants, they will probably see the survey as an opportunity to express their view on the PM processes.By using supporting tools, this should be doable.

Furthermore, it is important for the organisation to keep working with the maturity after the execution of the survey. The case study shows, that it is far from enough to just show the results of the assessment in numbers. It is very important to know what they want to achieve within PM. This will help reaching a higher level of maturity by setting direction by prioritising actions and starting the change of culture in the organisation [F. Backlund et al, 2014]. Last but not least, organisations using PMMMs should keep making assessments to ensure that the plan is on track and that the organisation keeps improving in terms of project management. In that way it should be possible to benefit from using the Project Management Maturity Models and improve performance by setting targets and changing culture.

== Annotated bibliography ==
Brooks, N.; Clark, R. 2009: Using Maturity Models to Improve Project Management Practice
* This article outlines three author's different maturity models and how to measure maturity in an organisation. Whether it is only based on knowledge or also factors as actions and attitudes.

Grobler, P.J.; Steyn, H. 2006, PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?
* This article explains the need for improvements in PM and outlines the different types of models within project management maturity. The authors concludes that the existing models are still very generic.

Judgev, K.; Thomas, J. 2002, Project Management Maturity Models: The Silver Bullets of Competitive Advantage
* This article focus on how PM has a paramount influence on business success. It also has a description of PMMMs and furthermore a explanation of RBV (however, this is not considered in this article).

Backlund, F.; Chronéer, D.; Sundqvist, E. 2014, Project Management Maturity Models – A Critical Review
*A case study of application of PMMM in swedish construction companies. The case study both concerns the application but also the participants reflections on the use of the model.

Chen, J.; Zhang, X. 2010, PRINCE2 Based Project Management Maturity Model'
* An example of a PMMM. This one is based on the PRINCE2 PM processes, which makes the model tailor-made to an organisation which bases their PM on the PRINCE2. The model is thus based on eight PM processes and eight PM elements.

== References ==

<references />

Project Management Maturity Models

2016-09-26T21:04:52Z

S104809:

== Abstract ==
In being able to make improvements in an organisation, it is key to know both strengths and weaknesses. This also applies to project management which is seen as an extremely important factor in achieving success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness in the market. Project Management Maturity Models (PMMM’s) is a tool for exactly that. The model helps the organisation learn about itself and makes it aware of current strengths and weaknesses. The result is an assessment of which level of maturity the project management in an organisation is currently at. In extend to that, the model provides the basis for a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as a result of run to failure strategy in project management. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management. The key elements of the article are as follows;
* Big idea
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** Reactive or proactive? – the optimal way of using the model
** Workload versus results
* Limitations
* Reflections

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Today, project management is an important factor in being able to succeed and well performed project management is accounted as a competitive advantage on the market. Typically, the PMMMs consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows <ref name="BRO"> [''Using Maturity Models to Improve Project Management Practice''] '' Brooks, N.; Clark, R. 2009'' </ref>. ;
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the project management execution in the given organisation with standards (e.g. PMBOK Guide). The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in its strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

==== Concept ====
The above is a generic description of the idea behind the PMMMs. Firstly, the models did not just appear out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence <ref name="Jud"> [''Project Management Maturity Models: The Silver Bullets of Competitive Advantage''] '' Judgev, K.; Thomas, J. 2002'' </ref>. This was the beginning of development of maturity models. Today, app. 30 PMMMs exist. The models can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ <ref name="GR"> ["PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?"] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of model also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The five levels in this model are; 1) common language, 2) common processes, 3) singular methodology, 4), benchmarking, 5) continuous improvement <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. As illustrated in figure 1, level 3-5 are meant for continues benchmarking and improvements.

[[File:sofpic2.jpg|600px|thumb|center|Figure 1. Illustration of the five levels of a project management process model <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

The last type is the organisational models. As mentioned above, this type of model is the newest type of maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. Now, all of the business processes’ maturity levels are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance. This type of PMMM is more nuanced than the first two. Though, it also has a higher demand in time and resources. Whereas some types of models are applicable by the organisation itself, the organisational models might need assistance of consultancy company. [[File:sofpic1.jpg|600px|thumb|center|Figure 2. Result of assessment illustrated in a radar chart <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change [REF: Kotter’s eight steps]. The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. In situations like that, it can be accounted as a reactive action. … As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, one might say that the maturity level of an organisations project management performance and processes, should be assessed continuously to ensure improvements. This raises the question; how? –how to actually improve. For now, the result of the assessment is only the problems, but what about the solutions? This will be dealt with later on in this article.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper.

=== The LKAB Case Study ===
Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> presents a case study in application of PMMM’s. One of the companies in the study is the Swedish mining company, LKAB, primarily working in mining, refining and logistics. The company is 100 percent state owned, has a net turnover of approximately 31 billion SEK and also operates in Norway<ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. The company consists of approximately 4200 employees of which around 100 are employed in the project department, carries out hundreds of project every single year with the assistance of- and corporation with experts from other departments of the company. In 2012 LKAB initiated a maturity assessment of project management within the organisation [F. Backlund et al, 2014]. The assessment was executed by a consultancy company, using a model inspired by the P3M3, which is also described in the Big Idea section in this article. The assessment was based on seven PM processes; Management Control, Benefits Management, Financial Management, Stakeholder Engagement, Risk Management, Organisational Governance and Resource Management <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. XXX
In practice, the assessment was executed by an electronic app. 20 minutes’ survey, which was send to the participants by email. The confidential survey was a questionnaire questions for each PM process including one open question for each of the seven processes. 73 % of the responders answers the questions within the two weeks that was given as a time limit <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>.
Open questions XXX. The results were presented in the noget med afdelinger. The results ..

== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve level of maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. A lot of elements could be customized for a given organisation, as for instance industry. An example is the XXX company, which operates within construction in Sweden.

Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems.

All in all, there are still some limitations to this tool, but with the support of other tools, like for instance RBV (will be described), combined with a customisation for the specific organisation, this type of model could be a step in changing culture…

The application of the maturity model in the XXX case study, was also evaluated by participants afterwards. Some respondents expressed their frustration of the use of the model. They criticized the following use of the assessment, as they pointed out that the results were primarily presented to the employees without any further plan to improve and solve the assessed problems. Also, there was dissatisfaction in terms the difference in engagement in presentation of results amongst the organisation. <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> Leaders of the company, though explained, that such plans and solutions were to be executed, but where simply not finished at the time of the evaluation of the PMMM.
Moreover, the evaluation of the experiences of the responders’ also showed very little enthusiasm and engagement in answering the survey.

Of the organisations within the studies of Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>, none of them where using maturity models in PM at the time of the studies. One argument was that the application of the model has a very high demand on time and resources. It might not be the execution of the survey as it is simply done electronic, but the preparation and the following result presentation. That maybe makes the models of most relevance for larger PM based organisations.

A well defined PM practise could make it easier to apply the model. tailored . <ref name="Prince2"> [''PRINCE2 Based Project Management Maturity Model'] '' Chen, J.; Zhang, X.. 2010'' </ref>

== Reflections ==
The fact, that approximately 30 different project management maturity models exist, illustrates the common need for improvements in project management in organisations. Though, the study

Literature research and case studies indicates, that PMMM’s are not a simple tool to apply. Challenges in engaging participants combined with risk of misunderstood questions in the survey clarifies the need for particularly preparation before applying a PMMM. Firstly, the models are based on people’s engagement, thus the quality of the results are dependent on the participants. Thus it is extremely important to make sure, the participants know the relevance of the assessment and their participation i.e. the answers to the questions; Why are we doing this assessment? Why should I spent time to participate? What is the outcome? Etc. If they are able to answer these questions and the answers are positive and make the assessment appear relevant it might be easier for the participants to put a little more effort into their answers as opposed to if the surveys were just giving as extra workload without any further information. If the results reveals big difference between the department, there can be a risk of people only looking out for themselves and their results. That is why it also important to create a common goal by using the PMMMs. If the facilitators of the assessment (or the leaders of the organisation) are able to motivate the participants, they will probably see the survey as an opportunity to express their view on the PM processes.
Simple supporting tools can help this. XXX

Furthermore, it is important for the organisation to keep working with the maturity after the execution of the survey. The case study shows, that it is far from enough to just show the results of the assessment in numbers. It is very important to know what they want to achieve within PM. This will help reaching a higher level of maturity by setting direction by prioritising actions and starting the change of culture in the organisation [F. Backlund et al, 2014]. Last but not least, organisations using PMMMs should keep making assessments to ensure that the plan is on track and that the organisation keeps improving in terms of project management. In that way it should be possible to benefit from using the Project Management Maturity Models and improve performance by setting targets and changing culture.

== Annotated bibliography ==
Brooks, N.; Clark, R. 2009: Using Maturity Models to Improve Project Management Practice
* This article outlines three author's different maturity models and how to measure maturity in an organisation. Whether it is only based on knowledge or also factors as actions and attitudes.

Grobler, P.J.; Steyn, H. 2006, PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?
* This article explains the need for improvements in PM and outlines the different types of models within project management maturity. The authors concludes that the existing models are still very generic.

Judgev, K.; Thomas, J. 2002, Project Management Maturity Models: The Silver Bullets of Competitive Advantage
* This article focus on how PM has a paramount influence on business success. It also has a description of PMMMs and furthermore a explanation of RBV (however, this is not considered in this article).

Backlund, F.; Chronéer, D.; Sundqvist, E. 2014, Project Management Maturity Models – A Critical Review
*A case study of application of PMMM in swedish construction companies. The case study both concerns the application but also the participants reflections on the use of the model.

Chen, J.; Zhang, X. 2010, PRINCE2 Based Project Management Maturity Model'
* An example of a PMMM. This one is based on the PRINCE2 PM processes, which makes the model tailor-made to an organisation which bases their PM on the PRINCE2. The model is thus based on eight PM processes and eight PM elements.

== References ==

<references />

Project Management Maturity Models

2016-09-26T20:51:34Z

S104809:

== Abstract ==
In being able to make improvements in an organisation, it is key to know both strengths and weaknesses. This also applies to project management which is seen as an extremely important factor in achieving success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness in the market. Project Management Maturity Models (PMMM’s) is a tool for exactly that. The model helps the organisation learn about itself and makes it aware of current strengths and weaknesses. The result is an assessment of which level of maturity the project management in an organisation is currently at. In extend to that, the model provides the basis for a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as a result of run to failure strategy in project management. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management. The key elements of the article are as follows;
* Big idea
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** Reactive or proactive? – the optimal way of using the model
** Workload versus results
* Limitations
* Reflections

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Today, project management is an important factor in being able to succeed and well performed project management is accounted as a competitive advantage on the market. Typically, the PMMMs consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows <ref name="BRO"> [''Using Maturity Models to Improve Project Management Practice''] '' Brooks, N.; Clark, R. 2009'' </ref>. ;
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the project management execution in the given organisation with standards (e.g. PMBOK Guide). The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in its strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

==== Concept ====
The above is a generic description of the idea behind the PMMMs. Firstly, the models did not just appear out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence <ref name="Jud"> [''Project Management Maturity Models: The Silver Bullets of Competitive Advantage''] '' Judgev, K.; Thomas, J. 2002'' </ref>. This was the beginning of development of maturity models. Today, app. 30 PMMMs exist. The models can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ <ref name="GR"> ["PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?"] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of model also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The five levels in this model are; 1) common language, 2) common processes, 3) singular methodology, 4), benchmarking, 5) continuous improvement <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. As illustrated in figure 1, level 3-5 are meant for continues benchmarking and improvements.

[[File:sofpic2.jpg|600px|thumb|center|Figure 1. Illustration of the five levels of a project management process model <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

The last type is the organisational models. As mentioned above, this type of model is the newest type of maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. Now, all of the business processes’ maturity levels are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance. This type of PMMM is more nuanced than the first two. Though, it also has a higher demand in time and resources. Whereas some types of models are applicable by the organisation itself, the organisational models might need assistance of consultancy company. [[File:sofpic1.jpg|600px|thumb|center|Figure 2. Result of assessment illustrated in a radar chart <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change [REF: Kotter’s eight steps]. The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. In situations like that, it can be accounted as a reactive action. … As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, one might say that the maturity level of an organisations project management performance and processes, should be assessed continuously to ensure improvements. This raises the question; how? –how to actually improve. For now, the result of the assessment is only the problems, but what about the solutions? This will be dealt with later on in this article.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper.

=== The LKAB Case Study ===
Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> presents a case study in application of PMMM’s. One of the companies in the study is the Swedish mining company, LKAB, primarily working in mining, refining and logistics. The company is 100 percent state owned, has a net turnover of approximately 31 billion SEK and also operates in Norway<ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. The company consists of approximately 4200 employees of which around 100 are employed in the project department, carries out hundreds of project every single year with the assistance of- and corporation with experts from other departments of the company. In 2012 LKAB initiated a maturity assessment of project management within the organisation [F. Backlund et al, 2014]. The assessment was executed by a consultancy company, using a model inspired by the P3M3, which is also described in the Big Idea section in this article. The assessment was based on seven PM processes; Management Control, Benefits Management, Financial Management, Stakeholder Engagement, Risk Management, Organisational Governance and Resource Management <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. XXX
In practice, the assessment was executed by an electronic app. 20 minutes’ survey, which was send to the participants by email. The confidential survey was a questionnaire questions for each PM process including one open question for each of the seven processes. 73 % of the responders answers the questions within the two weeks that was given as a time limit <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>.
Open questions XXX. The results were presented in the noget med afdelinger. The results ..

== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve level of maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. A lot of elements could be customized for a given organisation, as for instance industry. An example is the XXX company, which operates within construction in Sweden.

Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems.

All in all, there are still some limitations to this tool, but with the support of other tools, like for instance RBV (will be described), combined with a customisation for the specific organisation, this type of model could be a step in changing culture…

The application of the maturity model in the XXX case study, was also evaluated by participants afterwards. Some respondents expressed their frustration of the use of the model. They criticized the following use of the assessment, as they pointed out that the results were primarily presented to the employees without any further plan to improve and solve the assessed problems. Also, there was dissatisfaction in terms the difference in engagement in presentation of results amongst the organisation. <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> Leaders of the company, though explained, that such plans and solutions were to be executed, but where simply not finished at the time of the evaluation of the PMMM.
Moreover, the evaluation of the experiences of the responders’ also showed very little enthusiasm and engagement in answering the survey.

Of the organisations within the studies of Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>, none of them where using maturity models in PM at the time of the studies. One argument was that the application of the model has a very high demand on time and resources. It might not be the execution of the survey as it is simply done electronic, but the preparation and the following result presentation. That maybe makes the models of most relevance for larger PM based organisations.

A well defined PM practise could make it easier to apply the model. tailored . <ref name="Prince2"> [''PRINCE2 Based Project Management Maturity Model'] '' Chen, J.; Zhang, X.. 2010'' </ref>

== Reflections ==
The fact, that approximately 30 different project management maturity models exist, illustrates the common need for improvements in project management in organisations. Though, the study

Literature research and case studies indicates, that PMMM’s are not a simple tool to apply. Challenges in engaging participants combined with risk of misunderstood questions in the survey clarifies the need for particularly preparation before applying a PMMM. Firstly, the models are based on people’s engagement, thus the quality of the results are dependent on the participants. Thus it is extremely important to make sure, the participants know the relevance of the assessment and their participation i.e. the answers to the questions; Why are we doing this assessment? Why should I spent time to participate? What is the outcome? Etc. If they are able to answer these questions and the answers are positive and make the assessment appear relevant it might be easier for the participants to put a little more effort into their answers as opposed to if the surveys were just giving as extra workload without any further information. If the results reveals big difference between the department, there can be a risk of people only looking out for themselves and their results. That is why it also important to create a common goal by using the PMMMs. If the facilitators of the assessment (or the leaders of the organisation) are able to motivate the participants, they will probably see the survey as an opportunity to express their view on the PM processes.
Simple supporting tools can help this. XXX

Furthermore, it is important for the organisation to keep working with the maturity after the execution of the survey. The case study shows, that it is far from enough to just show the results of the assessment in numbers. It is very important to know what they want to achieve within PM. This will help reaching a higher level of maturity by setting direction by prioritising actions and starting the change of culture in the organisation [F. Backlund et al, 2014]. Last but not least, organisations using PMMMs should keep making assessments to ensure that the plan is on track and that the organisation keeps improving in terms of project management. In that way it should be possible to benefit from using the Project Management Maturity Models and improve performance by setting targets and changing culture.

== Annotated bibliography ==
Brooks, N.; Clark, R. 2009: Using Maturity Models to Improve Project Management Practice
*

Grobler, P.J.; Steyn, H. 2006, PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?
* This article outlines the different types of models within project management maturity. The authors ..

Judgev, K.; Thomas, J. 2002, Project Management Maturity Models: The Silver Bullets of Competitive Advantage
*

Backlund, F.; Chronéer, D.; Sundqvist, E. 2014, Project Management Maturity Models – A Critical Review
*

Chen, J.; Zhang, X. 2010, PRINCE2 Based Project Management Maturity Model'
*

== References ==

<references />

File:Sofpic2.jpg

2016-09-26T20:39:29Z

S104809:

Project Management Maturity Models

2016-09-26T20:39:11Z

S104809:

== Abstract ==
In being able to make improvements in an organisation, it is key to know both strengths and weaknesses. This also applies to project management which is seen as an extremely important factor in achieving success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness in the market. Project Management Maturity Models (PMMM’s) is a tool for exactly that. The model helps the organisation learn about itself and makes it aware of current strengths and weaknesses. The result is an assessment of which level of maturity the project management in an organisation is currently at. In extend to that, the model provides the basis for a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as a result of run to failure strategy in project management. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management. The key elements of the article are as follows;
* Big idea
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** Reactive or proactive? – the optimal way of using the model
** Workload versus results
* Limitations
* Reflections

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Today, project management is an important factor in being able to succeed and well performed project management is accounted as a competitive advantage on the market. Typically, the PMMMs consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows <ref name="BRO"> [''Using Maturity Models to Improve Project Management Practice''] '' Brooks, N.; Clark, R. 2009'' </ref>. ;
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the project management execution in the given organisation with standards (e.g. PMBOK Guide). The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in its strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

==== Concept ====
The above is a generic description of the idea behind the PMMMs. Firstly, the models did not just appear out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence <ref name="Jud"> [''Project Management Maturity Models: The Silver Bullets of Competitive Advantage''] '' Judgev, K.; Thomas, J. 2002'' </ref>. This was the beginning of development of maturity models. Today, app. 30 PMMMs exist. The models can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ <ref name="GR"> ["PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?"] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of model also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The five levels in this model are; 1) common language, 2) common processes, 3) singular methodology, 4), benchmarking, 5) continuous improvement <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

As illustrated in figure XX, level 3-5 are..

The last type is the organisational models. As mentioned above, this type of model is the newest type of maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. Now, all of the business processes’ maturity levels are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance. This type of PMMM is more nuanced than the first two. Though, it also has a higher demand in time and resources. Whereas some types of models are applicable by the organisation itself, the organisational models might need assistance of consultancy company. [[File:sofpic1.jpg|600px|thumb|center|Figure 1. Result of assessment illustrated in a radar chart <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change [REF: Kotter’s eight steps]. The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. In situations like that, it can be accounted as a reactive action. … As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, one might say that the maturity level of an organisations project management performance and processes, should be assessed continuously to ensure improvements. This raises the question; how? –how to actually improve. For now, the result of the assessment is only the problems, but what about the solutions? This will be dealt with later on in this article.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper.

=== The LKAB Case Study ===
Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> presents a case study in application of PMMM’s. One of the companies in the study is the Swedish mining company, LKAB, primarily working in mining, refining and logistics. The company is 100 percent state owned, has a net turnover of approximately 31 billion SEK and also operates in Norway<ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. The company consists of approximately 4200 employees of which around 100 are employed in the project department, carries out hundreds of project every single year with the assistance of- and corporation with experts from other departments of the company. In 2012 LKAB initiated a maturity assessment of project management within the organisation [F. Backlund et al, 2014]. The assessment was executed by a consultancy company, using a model inspired by the P3M3, which is also described in the Big Idea section in this article. The assessment was based on seven PM processes; Management Control, Benefits Management, Financial Management, Stakeholder Engagement, Risk Management, Organisational Governance and Resource Management <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. XXX
In practice, the assessment was executed by an electronic app. 20 minutes’ survey, which was send to the participants by email. The confidential survey was a questionnaire questions for each PM process including one open question for each of the seven processes. 73 % of the responders answers the questions within the two weeks that was given as a time limit <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>.
Open questions XXX. The results were presented in the noget med afdelinger. The results ..

== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve level of maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. A lot of elements could be customized for a given organisation, as for instance industry. An example is the XXX company, which operates within construction in Sweden.

Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems.

All in all, there are still some limitations to this tool, but with the support of other tools, like for instance RBV (will be described), combined with a customisation for the specific organisation, this type of model could be a step in changing culture…

The application of the maturity model in the XXX case study, was also evaluated by participants afterwards. Some respondents expressed their frustration of the use of the model. They criticized the following use of the assessment, as they pointed out that the results were primarily presented to the employees without any further plan to improve and solve the assessed problems. Also, there was dissatisfaction in terms the difference in engagement in presentation of results amongst the organisation. <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> Leaders of the company, though explained, that such plans and solutions were to be executed, but where simply not finished at the time of the evaluation of the PMMM.
Moreover, the evaluation of the experiences of the responders’ also showed very little enthusiasm and engagement in answering the survey.

Of the organisations within the studies of Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>, none of them where using maturity models in PM at the time of the studies. One argument was that the application of the model has a very high demand on time and resources. It might not be the execution of the survey as it is simply done electronic, but the preparation and the following result presentation. That maybe makes the models of most relevance for larger PM based organisations.

== Reflections ==
The fact, that approximately 30 different project management maturity models exist, illustrates the common need for improvements in project management in organisations. Though, the study

Literature research and case studies indicates, that PMMM’s are not a simple tool to apply. Challenges in engaging participants combined with risk of misunderstood questions in the survey clarifies the need for particularly preparation before applying a PMMM. Firstly, the models are based on people’s engagement, thus the quality of the results are dependent on the participants. Thus it is extremely important to make sure, the participants know the relevance of the assessment and their participation i.e. the answers to the questions; Why are we doing this assessment? Why should I spent time to participate? What is the outcome? Etc. If they are able to answer these questions and the answers are positive and make the assessment appear relevant it might be easier for the participants to put a little more effort into their answers as opposed to if the surveys were just giving as extra workload without any further information. If the results reveals big difference between the department, there can be a risk of people only looking out for themselves and their results. That is why it also important to create a common goal by using the PMMMs. If the facilitators of the assessment (or the leaders of the organisation) are able to motivate the participants, they will probably see the survey as an opportunity to express their view on the PM processes.
Simple supporting tools can help this. XXX

Furthermore, it is important for the organisation to keep working with the maturity after the execution of the survey. The case study shows, that it is far from enough to just show the results of the assessment in numbers. It is very important to know what they want to achieve within PM. This will help reaching a higher level of maturity by setting direction by prioritising actions and starting the change of culture in the organisation [F. Backlund et al, 2014]. Last but not least, organisations using PMMMs should keep making assessments to ensure that the plan is on track and that the organisation keeps improving in terms of project management. In that way it should be possible to benefit from using the Project Management Maturity Models and improve performance by setting targets and changing culture.

== Annotated bibliography ==

== References ==

<references />

Project Management Maturity Models

2016-09-26T20:30:37Z

S104809:

== Abstract ==
In being able to make improvements in an organisation, it is key to know both strengths and weaknesses. This also applies to project management which is seen as an extremely important factor in achieving success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness in the market. Project Management Maturity Models (PMMM’s) is a tool for exactly that. The model helps the organisation learn about itself and makes it aware of current strengths and weaknesses. The result is an assessment of which level of maturity the project management in an organisation is currently at. In extend to that, the model provides the basis for a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as a result of run to failure strategy in project management. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management. The key elements of the article are as follows;
* Big idea
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** Reactive or proactive? – the optimal way of using the model
** Workload versus results
* Limitations
* Reflections

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Today, project management is an important factor in being able to succeed and well performed project management is accounted as a competitive advantage on the market. Typically, the PMMMs consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows <ref name="BRO"> [''Using Maturity Models to Improve Project Management Practice''] '' Brooks, N.; Clark, R. 2009'' </ref>. ;
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the project management execution in the given organisation with standards (e.g. PMBOK Guide). The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in its strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

==== Concept ====
The above is a generic description of the idea behind the PMMMs. Firstly, the models did not just appear out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence <ref name="Jud"> [''Project Management Maturity Models: The Silver Bullets of Competitive Advantage''] '' Judgev, K.; Thomas, J. 2002'' </ref>. This was the beginning of development of maturity models. Today, app. 30 PMMMs exist. The models can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ <ref name="GR"> ["PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?"] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of model also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The five levels in this model are;

;Level 1, common language :the organisation does not recognize the benefits of project management - there is knowledge about project management terms but not necessarily the correct meaning of them – there is a lack of framework for decision making. <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

;Level 2, common processes :the

;Level 3, singular methodology :bla bla

;Level 4, Benchmarking :bla bla

;Level 5, continuous improvement :bla bla

As illustrated in figure XX, level 3-5 are..

The last type is the organisational models. As mentioned above, this type of model is the newest type of maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>. Now, all of the business processes’ maturity levels are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance. This type of PMMM is more nuanced than the first two. Though, it also has a higher demand in time and resources. Whereas some types of models are applicable by the organisation itself, the organisational models might need assistance of consultancy company. [[File:sofpic1.jpg|600px|thumb|center|Figure 1. Result of assessment illustrated in a radar chart <ref name="GR"> [''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?''] '' Grobler, P.J.; Steyn, H. 2006'' </ref>]]

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change [REF: Kotter’s eight steps]. The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. In situations like that, it can be accounted as a reactive action. … As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, one might say that the maturity level of an organisations project management performance and processes, should be assessed continuously to ensure improvements. This raises the question; how? –how to actually improve. For now, the result of the assessment is only the problems, but what about the solutions? This will be dealt with later on in this article.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper.

=== The LKAB Case Study ===
Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> presents a case study in application of PMMM’s. One of the companies in the study is the Swedish mining company, LKAB, primarily working in mining, refining and logistics. The company is 100 percent state owned, has a net turnover of approximately 31 billion SEK and also operates in Norway<ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. The company consists of approximately 4200 employees of which around 100 are employed in the project department, carries out hundreds of project every single year with the assistance of- and corporation with experts from other departments of the company. In 2012 LKAB initiated a maturity assessment of project management within the organisation [F. Backlund et al, 2014]. The assessment was executed by a consultancy company, using a model inspired by the P3M3, which is also described in the Big Idea section in this article. The assessment was based on seven PM processes; Management Control, Benefits Management, Financial Management, Stakeholder Engagement, Risk Management, Organisational Governance and Resource Management <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>. XXX
In practice, the assessment was executed by an electronic app. 20 minutes’ survey, which was send to the participants by email. The confidential survey was a questionnaire questions for each PM process including one open question for each of the seven processes. 73 % of the responders answers the questions within the two weeks that was given as a time limit <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>.
Open questions XXX. The results were presented in the noget med afdelinger. The results ..

== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve level of maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. A lot of elements could be customized for a given organisation, as for instance industry. An example is the XXX company, which operates within construction in Sweden.

Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems.

All in all, there are still some limitations to this tool, but with the support of other tools, like for instance RBV (will be described), combined with a customisation for the specific organisation, this type of model could be a step in changing culture…

The application of the maturity model in the XXX case study, was also evaluated by participants afterwards. Some respondents expressed their frustration of the use of the model. They criticized the following use of the assessment, as they pointed out that the results were primarily presented to the employees without any further plan to improve and solve the assessed problems. Also, there was dissatisfaction in terms the difference in engagement in presentation of results amongst the organisation. <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref> Leaders of the company, though explained, that such plans and solutions were to be executed, but where simply not finished at the time of the evaluation of the PMMM.
Moreover, the evaluation of the experiences of the responders’ also showed very little enthusiasm and engagement in answering the survey.

Of the organisations within the studies of Backlund et al <ref name="BACK"> [''Project Management Maturity Models – A Critical Review''] '' Backlund, F.; Chronéer, D.; Sundqvist, E.. 2014'' </ref>, none of them where using maturity models in PM at the time of the studies. One argument was that the application of the model has a very high demand on time and resources. It might not be the execution of the survey as it is simply done electronic, but the preparation and the following result presentation. That maybe makes the models of most relevance for larger PM based organisations.

== Reflections ==
The fact, that approximately 30 different project management maturity models exist, illustrates the common need for improvements in project management in organisations. Though, the study

Literature research and case studies indicates, that PMMM’s are not a simple tool to apply. Challenges in engaging participants combined with risk of misunderstood questions in the survey clarifies the need for particularly preparation before applying a PMMM. Firstly, the models are based on people’s engagement, thus the quality of the results are dependent on the participants. Thus it is extremely important to make sure, the participants know the relevance of the assessment and their participation i.e. the answers to the questions; Why are we doing this assessment? Why should I spent time to participate? What is the outcome? Etc. If they are able to answer these questions and the answers are positive and make the assessment appear relevant it might be easier for the participants to put a little more effort into their answers as opposed to if the surveys were just giving as extra workload without any further information. If the results reveals big difference between the department, there can be a risk of people only looking out for themselves and their results. That is why it also important to create a common goal by using the PMMMs. If the facilitators of the assessment (or the leaders of the organisation) are able to motivate the participants, they will probably see the survey as an opportunity to express their view on the PM processes.
Simple supporting tools can help this. XXX

Furthermore, it is important for the organisation to keep working with the maturity after the execution of the survey. The case study shows, that it is far from enough to just show the results of the assessment in numbers. It is very important to know what they want to achieve within PM. This will help reaching a higher level of maturity by setting direction by prioritising actions and starting the change of culture in the organisation [F. Backlund et al, 2014]. Last but not least, organisations using PMMMs should keep making assessments to ensure that the plan is on track and that the organisation keeps improving in terms of project management. In that way it should be possible to benefit from using the Project Management Maturity Models and improve performance by setting targets and changing culture.

== Annotated bibliography ==

== References ==

<references />

Project Management Maturity Models

2016-09-26T20:14:21Z

S104809:

== Abstract ==
In being able to make improvements in an organisation, it is key to know both strengths and weaknesses. This also applies to project management which is seen as an extremely important factor in achieving success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness in the market. Project Management Maturity Models (PMMM’s) is a tool for exactly that. The model helps the organisation learn about itself and makes it aware of current strengths and weaknesses. The result is an assessment of which level of maturity the project management in an organisation is currently at. In extend to that, the model provides the basis for a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as a result of run to failure strategy in project management. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management. The key elements of the article are as follows;
* Big idea
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** Reactive or proactive? – the optimal way of using the model
** Workload versus results
* Limitations
* Reflections

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Today, project management is an important factor in being able to succeed and well performed project management is accounted as a competitive advantage on the market. Typically, the PMMMs consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows <ref name="BRO"> ''Using Maturity Models to Improve Project Management Practice'' '' Brooks, N.; Clark, R. 2009'' </ref>. ;
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the project management execution in the given organisation with standards (e.g. PMBOK Guide). The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in its strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, <ref name="GR"> ''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?'' '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

==== Concept ====
The above is a generic description of the idea behind the PMMMs. Firstly, the models did not just appear out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence [Judgev & Thomas 2002] <ref name="Jud"> ''Project Management Maturity Models: The Silver Bullets of Competitive Advantage'' '' Judgev, K.; Thomas, J. 2002'' </ref>. This was the beginning of development of maturity models. Today, app. 30 PMMMs exist. The models can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ [Grobler 2006]. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of model also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” [Grobler 2006]. The five levels in this model are;

;Level 1, common language :the organisation does not recognize the benefits of project management - there is knowledge about project management terms but not necessarily the correct meaning of them – there is a lack of framework for decision making. [Grobler 2006].

;Level 2, common processes :the

;Level 3, singular methodology :bla bla

;Level 4, Benchmarking :bla bla

;Level 5, continuous improvement :bla bla

As illustrated in figure XX, level 3-5 are..

The last type is the organisational models. As mentioned above, this type of model is the newest type of maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” [Grobler 2006]. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management [Grobler 2006]. Now, all of the business processes’ maturity levels are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance. This type of PMMM is more nuanced than the first two. Though, it also has a higher demand in time and resources. Whereas some types of models are applicable by the organisation itself, the organisational models might need assistance of consultancy company. [[File:sofpic1.jpg|600px|thumb|center|Figure 1. Result of assessment illustrated in a radar chart]]

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change [REF: Kotter’s eight steps]. The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. In situations like that, it can be accounted as a reactive action. … As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, one might say that the maturity level of an organisations project management performance and processes, should be assessed continuously to ensure improvements. This raises the question; how? –how to actually improve. For now, the result of the assessment is only the problems, but what about the solutions? This will be dealt with later on in this article.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper.

=== The LKAB Case Study ===
Backlund et al [F. Backlund et al, 2014] presents a case study in application of PMMM’s. One of the companies in the study is the Swedish mining company, LKAB, primarily working in mining, refining and logistics. The company is 100 percent state owned, has a net turnover of approximately 31 billion SEK and also operates in Norway [F. Backlund et al, 2014]. The company consists of approximately 4200 employees of which around 100 are employed in the project department, carries out hundreds of project every single year with the assistance of- and corporation with experts from other departments of the company. In 2012 LKAB initiated a maturity assessment of project management within the organisation [F. Backlund et al, 2014]. The assessment was executed by a consultancy company, using a model inspired by the P3M3, which is also described in the Big Idea section in this article. The assessment was based on seven PM processes; Management Control, Benefits Management, Financial Management, Stakeholder Engagement, Risk Management, Organisational Governance and Resource Management [F. Backlund et al, 2014]. XXX
In practice, the assessment was executed by an electronic app. 20 minutes’ survey, which was send to the participants by email. The confidential survey was a questionnaire questions for each PM process including one open question for each of the seven processes. 73 % of the responders answers the questions within the two weeks that was given as a time limit [F. Backlund et al, 2014].
Open questions XXX. The results were presented in the noget med afdelinger. The results ..

== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve level of maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. A lot of elements could be customized for a given organisation, as for instance industry. An example is the XXX company, which operates within construction in Sweden.

Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems.

All in all, there are still some limitations to this tool, but with the support of other tools, like for instance RBV (will be described), combined with a customisation for the specific organisation, this type of model could be a step in changing culture…

The application of the maturity model in the XXX case study, was also evaluated by participants afterwards. Some respondents expressed their frustration of the use of the model. They criticized the following use of the assessment, as they pointed out that the results were primarily presented to the employees without any further plan to improve and solve the assessed problems. Also, there was dissatisfaction in terms the difference in engagement in presentation of results amongst the organisation. [F. Backlund et al, 2014] Leaders of the company, though explained, that such plans and solutions were to be executed, but where simply not finished at the time of the evaluation of the PMMM.
Moreover, the evaluation of the experiences of the responders’ also showed very little enthusiasm and engagement in answering the survey.

Of the organisations within the studies of Backlund et al [F. Backlund et al, 2014], none of them where using maturity models in PM at the time of the studies. One argument was that the application of the model has a very high demand on time and resources. It might not be the execution of the survey as it is simply done electronic, but the preparation and the following result presentation. That maybe makes the models of most relevance for larger PM based organisations.

== Reflections ==
The fact, that approximately 30 different project management maturity models exist, illustrates the common need for improvements in project management in organisations. Though, the study

Literature research and case studies indicates, that PMMM’s are not a simple tool to apply. Challenges in engaging participants combined with risk of misunderstood questions in the survey clarifies the need for particularly preparation before applying a PMMM. Firstly, the models are based on people’s engagement, thus the quality of the results are dependent on the participants. Thus it is extremely important to make sure, the participants know the relevance of the assessment and their participation i.e. the answers to the questions; Why are we doing this assessment? Why should I spent time to participate? What is the outcome? Etc. If they are able to answer these questions and the answers are positive and make the assessment appear relevant it might be easier for the participants to put a little more effort into their answers as opposed to if the surveys were just giving as extra workload without any further information. If the results reveals big difference between the department, there can be a risk of people only looking out for themselves and their results. That is why it also important to create a common goal by using the PMMMs. If the facilitators of the assessment (or the leaders of the organisation) are able to motivate the participants, they will probably see the survey as an opportunity to express their view on the PM processes.
Simple supporting tools can help this. XXX

Furthermore, it is important for the organisation to keep working with the maturity after the execution of the survey. The case study shows, that it is far from enough to just show the results of the assessment in numbers. It is very important to know what they want to achieve within PM. This will help reaching a higher level of maturity by setting direction by prioritising actions and starting the change of culture in the organisation [F. Backlund et al, 2014]. Last but not least, organisations using PMMMs should keep making assessments to ensure that the plan is on track and that the organisation keeps improving in terms of project management. In that way it should be possible to benefit from using the Project Management Maturity Models and improve performance by setting targets and changing culture.

== Annotated bibliography ==

== References ==

<references />

Project Management Maturity Models

2016-09-26T20:10:08Z

S104809:

== Abstract ==
In being able to make improvements in an organisation, it is key to know both strengths and weaknesses. This also applies to project management which is seen as an extremely important factor in achieving success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness in the market. Project Management Maturity Models (PMMM’s) is a tool for exactly that. The model helps the organisation learn about itself and makes it aware of current strengths and weaknesses. The result is an assessment of which level of maturity the project management in an organisation is currently at. In extend to that, the model provides the basis for a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as a result of run to failure strategy in project management. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management. The key elements of the article are as follows;
* Big idea
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** Reactive or proactive? – the optimal way of using the model
** Workload versus results
* Limitations
* Reflections

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Today, project management is an important factor in being able to succeed and well performed project management is accounted as a competitive advantage on the market. Typically, the PMMMs consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows <ref name="GR"> ''Using Maturity Models to Improve Project Management Practice'' '' Brooks, N.; Clark, R. 2009'' </ref>. ;
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the project management execution in the given organisation with standards (e.g. PMBOK Guide). The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in its strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, <ref name="GR"> ''PROJECT MANAGEMENT MATURITY MODELS: DOES ONE SIZE FIT ALL?'' '' Grobler, P.J.; Steyn, H. 2006'' </ref>.

==== Concept ====
The above is a generic description of the idea behind the PMMMs. Firstly, the models did not just appear out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence [Judgev & Thomas 2002]. This was the beginning of development of maturity models. Today, app. 30 PMMMs exist. The models can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ [Grobler 2006]. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of model also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” [Grobler 2006]. The five levels in this model are;

;Level 1, common language :the organisation does not recognize the benefits of project management - there is knowledge about project management terms but not necessarily the correct meaning of them – there is a lack of framework for decision making. [Grobler 2006].

;Level 2, common processes :the

;Level 3, singular methodology :bla bla

;Level 4, Benchmarking :bla bla

;Level 5, continuous improvement :bla bla

As illustrated in figure XX, level 3-5 are..

The last type is the organisational models. As mentioned above, this type of model is the newest type of maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” [Grobler 2006]. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management [Grobler 2006]. Now, all of the business processes’ maturity levels are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance. This type of PMMM is more nuanced than the first two. Though, it also has a higher demand in time and resources. Whereas some types of models are applicable by the organisation itself, the organisational models might need assistance of consultancy company. [[File:sofpic1.jpg|600px|thumb|center|Figure 1. Result of assessment illustrated in a radar chart]]

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change [REF: Kotter’s eight steps]. The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. In situations like that, it can be accounted as a reactive action. … As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, one might say that the maturity level of an organisations project management performance and processes, should be assessed continuously to ensure improvements. This raises the question; how? –how to actually improve. For now, the result of the assessment is only the problems, but what about the solutions? This will be dealt with later on in this article.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper.

=== The LKAB Case Study ===
Backlund et al [F. Backlund et al, 2014] presents a case study in application of PMMM’s. One of the companies in the study is the Swedish mining company, LKAB, primarily working in mining, refining and logistics. The company is 100 percent state owned, has a net turnover of approximately 31 billion SEK and also operates in Norway [F. Backlund et al, 2014]. The company consists of approximately 4200 employees of which around 100 are employed in the project department, carries out hundreds of project every single year with the assistance of- and corporation with experts from other departments of the company. In 2012 LKAB initiated a maturity assessment of project management within the organisation [F. Backlund et al, 2014]. The assessment was executed by a consultancy company, using a model inspired by the P3M3, which is also described in the Big Idea section in this article. The assessment was based on seven PM processes; Management Control, Benefits Management, Financial Management, Stakeholder Engagement, Risk Management, Organisational Governance and Resource Management [F. Backlund et al, 2014]. XXX
In practice, the assessment was executed by an electronic app. 20 minutes’ survey, which was send to the participants by email. The confidential survey was a questionnaire questions for each PM process including one open question for each of the seven processes. 73 % of the responders answers the questions within the two weeks that was given as a time limit [F. Backlund et al, 2014].
Open questions XXX. The results were presented in the noget med afdelinger. The results ..

== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve level of maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. A lot of elements could be customized for a given organisation, as for instance industry. An example is the XXX company, which operates within construction in Sweden.

Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems.

All in all, there are still some limitations to this tool, but with the support of other tools, like for instance RBV (will be described), combined with a customisation for the specific organisation, this type of model could be a step in changing culture…

The application of the maturity model in the XXX case study, was also evaluated by participants afterwards. Some respondents expressed their frustration of the use of the model. They criticized the following use of the assessment, as they pointed out that the results were primarily presented to the employees without any further plan to improve and solve the assessed problems. Also, there was dissatisfaction in terms the difference in engagement in presentation of results amongst the organisation. [F. Backlund et al, 2014] Leaders of the company, though explained, that such plans and solutions were to be executed, but where simply not finished at the time of the evaluation of the PMMM.
Moreover, the evaluation of the experiences of the responders’ also showed very little enthusiasm and engagement in answering the survey.

Of the organisations within the studies of Backlund et al [F. Backlund et al, 2014], none of them where using maturity models in PM at the time of the studies. One argument was that the application of the model has a very high demand on time and resources. It might not be the execution of the survey as it is simply done electronic, but the preparation and the following result presentation. That maybe makes the models of most relevance for larger PM based organisations.

== Reflections ==
The fact, that approximately 30 different project management maturity models exist, illustrates the common need for improvements in project management in organisations. Though, the study

Literature research and case studies indicates, that PMMM’s are not a simple tool to apply. Challenges in engaging participants combined with risk of misunderstood questions in the survey clarifies the need for particularly preparation before applying a PMMM. Firstly, the models are based on people’s engagement, thus the quality of the results are dependent on the participants. Thus it is extremely important to make sure, the participants know the relevance of the assessment and their participation i.e. the answers to the questions; Why are we doing this assessment? Why should I spent time to participate? What is the outcome? Etc. If they are able to answer these questions and the answers are positive and make the assessment appear relevant it might be easier for the participants to put a little more effort into their answers as opposed to if the surveys were just giving as extra workload without any further information. If the results reveals big difference between the department, there can be a risk of people only looking out for themselves and their results. That is why it also important to create a common goal by using the PMMMs. If the facilitators of the assessment (or the leaders of the organisation) are able to motivate the participants, they will probably see the survey as an opportunity to express their view on the PM processes.
Simple supporting tools can help this. XXX

Furthermore, it is important for the organisation to keep working with the maturity after the execution of the survey. The case study shows, that it is far from enough to just show the results of the assessment in numbers. It is very important to know what they want to achieve within PM. This will help reaching a higher level of maturity by setting direction by prioritising actions and starting the change of culture in the organisation [F. Backlund et al, 2014]. Last but not least, organisations using PMMMs should keep making assessments to ensure that the plan is on track and that the organisation keeps improving in terms of project management. In that way it should be possible to benefit from using the Project Management Maturity Models and improve performance by setting targets and changing culture.

== Annotated bibliography ==

== References ==

<references />

Project Management Maturity Models

2016-09-26T20:02:23Z

S104809:

== Abstract ==
In being able to make improvements in an organisation, it is key to know both strengths and weaknesses. This also applies to project management which is seen as an extremely important factor in achieving success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness in the market. Project Management Maturity Models (PMMM’s) is a tool for exactly that. The model helps the organisation learn about itself and makes it aware of current strengths and weaknesses. The result is an assessment of which level of maturity the project management in an organisation is currently at. In extend to that, the model provides the basis for a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as a result of run to failure strategy in project management. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management. The key elements of the article are as follows;
* Big idea
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** Reactive or proactive? – the optimal way of using the model
** Workload versus results
* Limitations
* Reflections

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Today, project management is an important factor in being able to succeed and well performed project management is accounted as a competitive advantage on the market. Typically, the PMMMs consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows [Brookes & Clark 2009];
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the project management execution in the given organisation with standards (e.g. PMBOK Guide). The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in its strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, [Grobler 2006].

==== Concept ====
The above is a generic description of the idea behind the PMMMs. Firstly, the models did not just appear out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence [Judgev & Thomas 2002]. This was the beginning of development of maturity models. Today, app. 30 PMMMs exist. The models can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ [Grobler 2006]. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of model also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” [Grobler 2006]. The five levels in this model are;

;Level 1, common language :the organisation does not recognize the benefits of project management - there is knowledge about project management terms but not necessarily the correct meaning of them – there is a lack of framework for decision making. [Grobler 2006].

;Level 2, common processes :the

;Level 3, singular methodology :bla bla

;Level 4, Benchmarking :bla bla

;Level 5, continuous improvement :bla bla

As illustrated in figure XX, level 3-5 are..

The last type is the organisational models. As mentioned above, this type of model is the newest type of maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” [Grobler 2006]. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management [Grobler 2006]. Now, all of the business processes’ maturity levels are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance. This type of PMMM is more nuanced than the first two. Though, it also has a higher demand in time and resources. Whereas some types of models are applicable by the organisation itself, the organisational models might need assistance of consultancy company. [[File:sofpic1.jpg|600px|thumb|center|Figure 1. Result of assessment illustrated in a radar chart]]

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change [REF: Kotter’s eight steps]. The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. In situations like that, it can be accounted as a reactive action. … As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, one might say that the maturity level of an organisations project management performance and processes, should be assessed continuously to ensure improvements. This raises the question; how? –how to actually improve. For now, the result of the assessment is only the problems, but what about the solutions? This will be dealt with later on in this article.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper.

=== The LKAB Case Study ===
Backlund et al [F. Backlund et al, 2014] presents a case study in application of PMMM’s. One of the companies in the study is the Swedish mining company, LKAB, primarily working in mining, refining and logistics. The company is 100 percent state owned, has a net turnover of approximately 31 billion SEK and also operates in Norway [F. Backlund et al, 2014]. The company consists of approximately 4200 employees of which around 100 are employed in the project department, carries out hundreds of project every single year with the assistance of- and corporation with experts from other departments of the company. In 2012 LKAB initiated a maturity assessment of project management within the organisation [F. Backlund et al, 2014]. The assessment was executed by a consultancy company, using a model inspired by the P3M3, which is also described in the Big Idea section in this article. The assessment was based on seven PM processes; Management Control, Benefits Management, Financial Management, Stakeholder Engagement, Risk Management, Organisational Governance and Resource Management [F. Backlund et al, 2014]. XXX
In practice, the assessment was executed by an electronic app. 20 minutes’ survey, which was send to the participants by email. The confidential survey was a questionnaire questions for each PM process including one open question for each of the seven processes. 73 % of the responders answers the questions within the two weeks that was given as a time limit [F. Backlund et al, 2014].
Open questions XXX. The results were presented in the noget med afdelinger. The results ..

== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve level of maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. A lot of elements could be customized for a given organisation, as for instance industry. An example is the XXX company, which operates within construction in Sweden.

Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems.

All in all, there are still some limitations to this tool, but with the support of other tools, like for instance RBV (will be described), combined with a customisation for the specific organisation, this type of model could be a step in changing culture…

The application of the maturity model in the XXX case study, was also evaluated by participants afterwards. Some respondents expressed their frustration of the use of the model. They criticized the following use of the assessment, as they pointed out that the results were primarily presented to the employees without any further plan to improve and solve the assessed problems. Also, there was dissatisfaction in terms the difference in engagement in presentation of results amongst the organisation. [F. Backlund et al, 2014] Leaders of the company, though explained, that such plans and solutions were to be executed, but where simply not finished at the time of the evaluation of the PMMM.
Moreover, the evaluation of the experiences of the responders’ also showed very little enthusiasm and engagement in answering the survey.

Of the organisations within the studies of Backlund et al [F. Backlund et al, 2014], none of them where using maturity models in PM at the time of the studies. One argument was that the application of the model has a very high demand on time and resources. It might not be the execution of the survey as it is simply done electronic, but the preparation and the following result presentation. That maybe makes the models of most relevance for larger PM based organisations.

== Reflections ==

== Annotated bibliography ==

== References ==

<references />

File:Sofpic1.jpg

2016-09-26T19:57:07Z

S104809:

Project Management Maturity Models

2016-09-26T19:36:54Z

S104809:

Project Management Maturity Models

2016-09-26T16:01:35Z

S104809:

== Abstract ==
For an organisation to know its own strengths and weaknesses is key in being able to make improvements. This also applies to project management and project management is key to success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness. Project management maturity models (PMMM’s) is a tool for exactly that. The model helps the organisation to learn about itself and making it aware of strengths and weaknesses. The result of the model is the assessment of which of five maturity levels the project management in an organisation is currently at, as well as creating a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as the strategy for project management often is run to failure. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management. The key elements of the article are as follows;
* Purpose and potential (big idea)
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** Reactive or proactive? – the optimal way of using the model
** Workload versus results
* Limitations
** Tailoring the model for a specific organisation

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Typically, the models consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows [Brookes & Clark 2009];
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the reality with standards. The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in their strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, [Grobler 2006].

==== Concept ====
However, the above is a significant generic description of the idea behind the PMMMs. Firstly, the models did not just arise out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence [Judgev & Thomas 2002]. This was the beginning of development of maturity models. Today, app. 30 PMMM’s exist, which can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ [Grobler 2006]. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of mode also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” [Grobler 2006]. The five levels in this model are;

;Level 1, common language :the organisation does not recognize the benefits of project management - there is knowledge about project management terms but not necessarily the correct meaning of them – there is a lack of framework for decision making. [Grobler 2006].

;Level 2, common processes :the

;Level 3, singular methodology :bla bla

;Level 4, Benchmarking :bla bla

;Level 5, continuous improvement :bla bla

As illustrated in figure XX, level 3-5 are..

The last type is the organisational models. As mentioned above, this type of model is the latest bid of a maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” [Grobler 2006]. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management [Grobler 2006]. Now, all of the business processes’ maturity level are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance.

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change [REF: Kotter’s eight steps]. The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. In situations like that, it can be accounted as a reactive action. … As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, one might say that the maturity level of an organisations project management performance and processes, should be assessed continuously to ensure improvements. This raises the question; how? –how to actually improve. For now, the result of the assessment is only the problems, but what about the solutions? This will be dealt with later on in this article.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper…

==== Reactive vs. proactive ====
''Here I want to, write something about when the model should be used.''
==== Workload vs. results ====
"Here I want to write, how an organisation can benefit from the use of maturity models. The question is, if it is too generic to actually get a clear and sure roadmap to improvements."
== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve in maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. There is a lot of things that could be customized for a given organisation, as for instance industry. Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems. More limitations are to be described…

All in all, there are still some limitations to this tool, but with the support of other tools, like for instance RBV (will be described), combined with a customisation for the specific organisation, this type of model could be a step in changing culture…

==== Tailoring the model for a specific organisation ====
== Annotated bibliography ==

Project Management Maturity Models

2016-09-16T19:34:42Z

S104809:

Dear reader: my article is clearly not finished :) My next step is to include an example of an applied PMMM!
-and of course finish the other sections and add references :)

== Abstract ==
For an organisation to know its own strengths and weaknesses is key in being able to make improvements. This also applies to project management and project management is key to success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness. Project management maturity models (PMMM’s) is a tool for exactly that. The model helps the organisation to learn about itself and making it aware of strengths and weaknesses. The result of the model is the assessment of which of five maturity levels the project management in an organisation is currently at, as well as creating a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as the strategy for project management often is run to failure. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management. The key elements of the article are as follows;
* Purpose and potential (big idea)
** Concept
** PMMM as first step in changing culture
* Application of a PMMM
** Reactive or proactive? – the optimal way of using the model
** Workload versus results
* Limitations
** Tailoring the model for a specific organisation

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Typically, the models consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows [Brookes & Clark 2009];
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the reality with standards. The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in their strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, [Grobler 2006].

==== Concept ====
However, the above is a significant generic description of the idea behind the PMMMs. Firstly, the models did not just arise out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence [Judgev & Thomas 2002]. This was the beginning of development of maturity models. Today, app. 30 PMMM’s exist, which can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ [Grobler 2006]. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of mode also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” [Grobler 2006]. The five levels in this model are;

;Level 1, common language :the organisation does not recognize the benefits of project management - there is knowledge about project management terms but not necessarily the correct meaning of them – there is a lack of framework for decision making. [Grobler 2006].

;Level 2, common processes :the

;Level 3, singular methodology :bla bla

;Level 4, Benchmarking :bla bla

;Level 5, continuous improvement :bla bla

As illustrated in figure XX, level 3-5 are..

The last type is the organisational models. As mentioned above, this type of model is the latest bid of a maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” [Grobler 2006]. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management [Grobler 2006]. Now, all of the business processes’ maturity level are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance.

==== PMMM as first step in changing culture in an organisation ====
Looking back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. The aim is to make the maturity model the first step in changing culture in an organisation. To be able to change, it is key to know the current situation in details. Kotter suggest eight steps in successful change [REF: Kotter’s eight steps]. The first step is to establish a sense of urgency. The step is also known as the burning platform, claiming that if there is no need for change, a change will not be executed, but if the floor beneath you is burning, you will for sure move. However, sometimes, though the need for change is present, the need for it is just not realised. Realising the need for change is key, in being able to make improvements. In many cases, this tool is taken into use, when problems are rising and projects are failing. In situations like that, it can be accounted as a reactive action. … As project management becomes a more and more important business process to any organisation, and as it is – by some – seen as a way of gaining competitive advantage, one might say that the maturity level of an organisations project management performance and processes, should be assessed continuously to ensure improvements. This raises the question; how? –how to actually improve. For now, the result of the assessment is only the problems, but what about the solutions? This will be dealt with later on in this article.

== Application ==
An organisation decides to use a maturity model and the first step is to choose the right one, that fits the organisation in different parameters such as industry, strategic goals etc. Though, there is not yet a knowledge based guideline for choosing the right model. Often, the execution of the assessment is done be external consultants, though, dependent on the extent of the assessment, it is possible for the organisation to perform it themselves. The assessment simply consists of questions regarding the organisation’s knowledge around the topic, project management. As mentioned earlier, the structure of the models varies and therefore the exact process of assessment also does so. The questions can simply be asked and answered electronic or on paper…

==== Reactive vs. proactive ====
''Here I want to, write something about when the model should be used.''
==== Workload vs. results ====
"Here I want to write, how an organisation can benefit from the use of maturity models. The question is, if it is too generic to actually get a clear and sure roadmap to improvements."
== Limitations ==
The idea and concept of this tool gives a lot of opportunities for organisation to improve in maturity in terms of project management as well as other business processes. For now, the models are still very generic, however, there is not a model, which fits every organisation, and not all models fit one organisation. There is a lot of things that could be customized for a given organisation, as for instance industry. Despite the claim of the models being generic, there are still some limitations. These can be divided into practical and theoretical ones. One of the practical ones is that there is a big gap in between the levels of maturity. This makes it very difficult to use the model to measure minor improvements. Also, some sees the model as a fine way of identifying problems, but not given the solutions to the problems. More limitations are to be described…

All in all, there are still some limitations to this tool, but with the support of other tools, like for instance RBV (will be described), combined with a customisation for the specific organisation, this type of model could be a step in changing culture…

==== Tailoring the model for a specific organisation ====
== Annotated bibliography ==

Project Management Maturity Models

2016-09-16T09:20:56Z

S104809:

== Abstract ==
For an organisation to know its own strengths and weaknesses is key in being able to change and make improvements. This also applies to project management and project management is key to success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness. Project management maturity models (PMMM’s) is a tool for exactly that. The model helps the organisation to learn about itself and making it aware of strengths and weaknesses. The result of the model is the assessment of which of five maturity levels the project management in an organisation is currently at, as well as creating a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as the strategy for project management often is run to failure. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management.

- Purpose and potential

- PMMM as first step in changing culture

- Reactive or proactive? – the optimal way of using the model

- Workload versus results

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Typically, the models consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows [Brookes & Clark 2009];
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the reality with standards. The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in their strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, [Grobler 2006].

==== Concept ====
However, the above is a significant generic description of the idea behind the PMMMs. Firstly, the models did not just arise out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence [Judgev & Thomas 2002]. This was the beginning of development of maturity models. Today, app. 30 PMMM’s exist, which can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ [Grobler 2006]. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of mode also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” [Grobler 2006]. The five levels in this model are;

;Level 1, common language :the organisation does not recognize the benefits of project management - there is knowledge about project management terms but not necessarily the correct meaning of them – there is a lack of framework for decision making. [Grobler 2006].

;Level 2, common processes :the

;Level 3, singular methodology :bla bla

;Level 4, Benchmarking :bla bla

;Level 5, continuous improvement :bla bla

As illustrated in figure XX, level 3-5 are..

The last type is the organisational models. As mentioned above, this type of model is the latest bid of a maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” [Grobler 2006]. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management [Grobler 2006]. Now, all of the business processes’ maturity level are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance.

==== PMMM as first step in changing culture in an organisation ====
As we look back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. This raises the question; how? This will be dealt with later on in this article.

== Application ==
==== Reactive vs. proactive ====
== Limitations ==
==== Tailoring the model for a specific organisation ====
== Annotated bibliography ==

Project Management Maturity Models

2016-09-15T17:42:15Z

S104809: /* Big Idea */

== Abstract ==
For an organisation to know its own strengths and weaknesses is key in being able to change and make improvements. This also applies to project management and project management is key to success for any organisation. As projects becomes more and more complex, it is necessary for any organisation to keep improving the competencies in project management in order to maintain competitiveness. Project management maturity models (PMMM’s) is a tool for exactly that. The model helps the organisation to learn about itself and making it aware of strengths and weaknesses. The result of the model is the assessment of which of five maturity levels the project management in an organisation is currently at, as well as creating a plan to achieve continuous improvements and higher levels of maturity. The tool is often used reactive as the strategy for project management often is run to failure. Often because the strategy for project management is not even considered, it is simply done. This raises the question if the model is used optimally? and if there is even more potential in using the model proactive? This article analyses the use and relevance of maturity models in project management.

- Purpose and potential

- PMMM as first step in changing culture

- Reactive or proactive? – the optimal way of using the model

- Workload versus results

== Big Idea ==
The basic idea behind PMMM’s is for an organisation to assess their current level of maturity of the project management performance. Typically, the models consist of five levels, where level 1 represents the lowest level of maturity and level 5 represents the highest reachable level of maturity. The definition and naming of the levels varies from model to model, though many use the original Carnegie Mellon maturity level definitions, which are as follows [Brookes & Clark 2009];
# Performed/Awareness/ad hoc
# Managed/ Repeatable
# Defined
# Quantitative managed/managed
# Optimised
The level of maturity is appointed by comparing the reality with standards. The result of the assessment is then used to set a roadmap for the organisation to reach higher levels of maturity in their strive for success. The idea is, that the highest level of maturity, optimized, is setting the stage to continuous improvement. Whereas, the first 4 level are based on comparison to standards, and best performance with existing processes, level 5 focus on optimising the processes in project management, [Grobler 2006].

However, the above is a significant generic description of the idea behind the PMMMs. Firstly, the models did not just arise out of blue air. PMMMs have their origins in the Capability Maturity Model, developed by Software Engineering Institute (thus the abbreviation SEI-CMM). The SEI-CMM take base in the same five levels as listed above and was originally developed to use in software implementation projects. The need for maturity models in project management arose as a result of the eighties’ tendency for project failure and budget overrun as a consequence [Judgev & Thomas 2002]. This was the beginning of development of maturity models. Today, app. 30 PMMM’s exist, which can be divided into three types of models, which all erupts from the SEI-CMM. The first two both take base in the five levels of maturity. Whereas the third one, which is also the latest, is more complex and holistic.

The first type of model is named technical delivery process model. This type is the SE-CMM. As said, this model consists of five levels of maturity, which indicates the organisations current state. The level of maturity is appointed an organisation as the result of a thorough assessment of the organisation’s project management processes. The description of the level indicates the end state of the given level. When an organisation is appointed a given level, they have not yet reached the end state of the level, but are at the beginning state of the maturity level. As an example level 3 is described as “Base practices of the process are performed, but not rigorously planned and executed. Reactive response dominates the actions of the process managers. Performance of the organization is dependent on individual knowledge and effort.“ [Grobler 2006]. This means that if an organisation is at this given stage, they will create the roadmap to reach that description. The roadmap for instance will help the organisation move from acting reactive to being proactive. When being proactive you prevent firefighting (Danish term!?) and short term planning, which can both often be very costly for the organisation. A lot of other arguments to being proactive can be listed, however that is not part of the scope of this article and therefore it will not be discussed into details.

The second type of PMMM is named project management process model. This type of mode also uses the five level of maturity level, though it does so a little differently from the first one. The project management process models take base in project management standards and their processes and knowledge areas within the processes. An example of a project management process model is the one developed by Kerzner in 2001, who describes project management maturity as “a gradual progress from a basic knowledge of the nine knowledge areas and a single process of project management to a singular methodology across the company.” [Grobler 2006]. The five levels in this model are;

;Level 1, common language :the organisation does not recognize the benefits of project management - there is knowledge about project management terms but not necessarily the correct meaning of them – there is a lack of framework for decision making. [Grobler 2006].

;Level 2, common processes :the

;Level 3, singular methodology :bla bla

;Level 4, Benchmarking :bla bla

;Level 5, continuous improvement :bla bla

As illustrated in figure XX, level 3-5 are..

The last type is the organisational models. As mentioned above, this type of model is the latest bid of a maturity model for use in project management and is a more holistic one, that the two types described before. The reason is, that this type of models does not only consider project management but all of the organisation. One of the models within this type is the Organisational Project Management Maturity Model, abbreviated to OPM3, which states itself as “a mechanism to advance your organization’s strategic interests through the efficient and successful execution of projects” [Grobler 2006]. The idea is, that it is not adequate to improve the project management process, if the rest of the organisation is falling behind as they are as important together in being able to reach the organisation’s strategic goals. To be able to look at all of the organisation, this type of model includes eight business processes, where the first of them is project management. The others are as follows 2) programme management, 3) assurance of the management quality in project programme management, 4) assignment of a project or programme, 5) project portfolio coordination and networking, 6) organisational design, 7) personnel management and 8) business process management [Grobler 2006]. Now, all of the business processes’ maturity level are assessed and they are appointed a level from 1 to 5. The result can easily be illustrated with a radar chart where all of the business processes and their appointed maturity levels will be inserted. The radar chart will give a visual look of the organisation’s maturity level and point out where to act to improve the organisation’s overall performance.

As we look back at all the mentioned types of maturity models for use in project management, it is clear that the idea of using the models in order to assess why some projects currently fail is possible to realise with these models. One might fear, that this tool would only be used as an assessment and that the improvements would be hard to realise. Though, the models give an explanation of what needs to be done to reach a higher level of maturity. This raises the question; how? This will be dealt with later on in this article.

== Application ==

== Limitations ==

== Annotated bibliography ==

Project Management Maturity Model

2016-09-14T06:37:31Z

S104809: S104809 moved page Project Management Maturity Model to Project Management Maturity Models

#REDIRECT [[Project Management Maturity Models]]

Project Management Maturity Models

2016-09-14T06:37:31Z

S104809: S104809 moved page Project Management Maturity Model to Project Management Maturity Models

Project Management Maturity Models

2016-09-11T21:45:42Z

S104809:

Project Management Maturity Models

2016-09-11T21:43:08Z

S104809:

Project Management Maturity Models

2016-09-11T21:40:28Z

S104809:

Project Management Maturity Models

2016-09-11T21:39:43Z

S104809:

Project Management Maturity Models

2016-09-11T20:06:41Z

S104809:

== Abstract ==
...

== Big Idea ==

== Application ==

== Limitations ==

== Annotated bibliography ==

Project Management Maturity Models

2016-09-11T20:03:22Z

S104809:

== Abstract ==
...

Project Management Maturity Models

2016-09-11T17:17:54Z

S104809: Created page with "..."

...

Articles Fall Term 2016

2016-09-11T17:15:53Z

S104809:

{| class="wikitable"
|+ '''Disclaimer!
|-
|''The requirements for the articles written during Fall Term 2015 were not the same as for Fall Term 2016. Please make sure you read the requirements for your own fall term carefully before starting your wiki article.''
|}

Please complete this table with your group number, full name, username and the title of your article.

To create more lines in the table click '''Edit''' and use the following code to create more lines in the table and replace the example text with your own information:

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
|-
|Group Number
|First Name
|Last Name
|Username
|Link to Article
|-
</pre>
Create a direct link by making square brackets ([[ ]]) around the title such as [[Title]]

The straight lines ( | ) create columns and the straight line with a dash ( |- ) creates a new row in the table.

( |} ) is only used at the very end to finish the coding for the table.

=Overview of 2016 Wiki articles=

{| class="wikitable sortable"
|+Fall 2016 Wiki Articles
|-
!Group Number
!First Name
!Last Name
!Wiki User Name
!Link to Wiki article
|-
|
|Aitor
|Altuna
|aitor.altuna
|[[Knowledge management in projects and organizations]]
|-|
| 06
|Alexander Daniel
|Marcussen
|Alm92
|[[Understand best practices based on network mapping]]
|-
|15
|Alexander
|Michel
|Alexm
|[[Portfolio Management using the BCG-Matrix]]

|-
|
|Amedeo
|Mocchiutti
|
|
|-
|
|Anastasia
|Stella
|
|
|-
|
|Andrzej
|Stanek
|
|
|-
|13
|Anika Zandra
|Alcoat
|zaac
||[[Risk and Opportunities Management]]
|-
|
|Anna
|Paparizou
|
|
|-
|
|Anne
|Folkvard Petersen
|
|
|-
|
|Apostolos
|Bougas
|
|
|-
|
|Arjun Abraham
|Punnen
|
|
|-
|
|Arnaldo
|Landivar Taborga
|
|
|-
|
|Aromi
|Salot
|
|
|-
|
|Artem
|Chernyshev
|
|
|-
|
|Arvin
|Fattah
|
|
|-
|
|Astrid
|Greve Rokne
|
|
|-
|4
|Birthe
|Wohlenberg
|BWO
|[[Myers-Briggs Type Indicator]]
|-
|7
|Bjarni Jakob
|Gunnarsson
|Bjarni Jakob
|[[Risk management process]]
|-|
|
|Camilla Engstrøm
|Jensen
|
|
|-
|14
|Camille
|Bortot
|Camille.Bortot
|[[International Project Management ]]
|-
|8
|Carl Johan Fokdal
|Christensen
|CJ
|[[Lean Design Management]]
|-
|
|Carlos
|Sanchez Garcia
|
|
|-
|
|Chalida
|Jaidee
|Chalidaj
|[[The Critical Path Method in project planning]]
|-
|
|Charlotte Cecilie
|Søgaard
|
|
|-
|
|Christian Haim
|Raben
|Christian
|[[Managing Portfolio Complexity]]
|-
|5
|Christian Lolk
|Thomsen
|
|[[Multi-criteria decision making (MCDM) for Project selection]]
|-
|3
|Christian Vindegaard
|Grønberg
|Vindegaard
|[[AHP as a Decision Making Tool in Projects, Programs and Portfolios]]
|-|
|2
|Christiane Steenbergh
|Myrup
|Chrisitane
|[[Last Planner System as a project management tool]]
|-
|
|Christoffer Koza
|Hansen
|Christoffer Koza
|[[Total Quality Management]]
|-|
|
|Clement Victor Emile
|Hammel
|
|
|-
|
|Davide
|Paganini
|
|
|-
|
|Edvinas
|Zamaratskis
|
|
|-
|8
|Erika
|di Pietro
|s155375
|[[Sustainability, a competitive advantage]]
|-
|
|Evdoxia
|Pertsinidou
|S151128
|[[Reporting of projects]]
|-
|
|Evgeniya Ventsislavova
|Garkova
|s160807
|[[The Kaizen – Toyota KATA method]]
|-
|
|Ewa Joanna
|Kunkel
|
|
|-
|
|Fabricio Gasparin
|Lucchesi
|
|
|-
|
|Federico
|Riccardo
|
|
|-
|
|Filip Møller Knudsen
|Knudsen
|Fmk
|[[Risk Management In Construction Projects]]
|-
|
|Filippo
|Gioanina
|
|
|-
|
|Franziska
|Schorr
|
|
|-
|
|Frederik
|Skjoldborg
|
|
|-
|
|Georg Maximilian Ruven
|Schriewersmann
|Mschriew
|[[Reference class forecasting and the corresponding limitations]]
|
|-
|
|Georgios
|Nikou
|
|
|-
|
|Gudjon
|Arngrimsson
|
|
|-
|7
|Gudrún Thóra
|Reynisdóttir
|s124692
|[[Critical-Chain Approach]]
|-
|
|Gunnar Thorlakur
|Thorsson
|
|
|-
|12
|Iðunn Tara
|Ásgrímsdóttir
|IdunnTara
|[[Theory of Constraints in Software Development]]
|-
|
|Igor
|Juko
|
|
|-
|
|Ingrid
|Berg
|
|
|-
|
|Ioannis
|Milakas-Tsamouras
|
|
|-
|01
|Jeanette Garst
|Johansen
|JeanetteGJ
|[[The use of Gantt chart in project management]]
|-
|
|Jens Dines Obel
|Jepsen
|DinesObelJepsen
|[[Value Maximization, Strategy Alignment and Balancing in Portfolios]]
|-
|
|João Pedro
|Castro
|
|
|-
|
|Johan Knudegaard
|Engesgaard
|
|
|-
|
|Jorge Horacio
|Ramirez Basurto
|
|
|-
|
|Jose de Jesus
|Cruz Contreras
|
|
|-
|
|Joseph
|Kurian
|
|
|-
|15
|Kai-Sören Sokolowski
|Sokolowski
|Kai
|[[Scrum in the context of lean and agile project management]]
|-
|4
|Katrine Bager
|Olesen
|S113525
|[[The Decision Matrix]]
|-
|10
|Line Hye Sun
|Elmshøj
|s123449
|[[Knowledge sharing in project management]]
|-
|
|Magnus
|Schulz
|MSchulz
|[[Earned Value Analysis]]
|-
|
|Marco
|Carloni
|
|
|-
|13
|Marco
|Ronzoni
|Marcoronzoni
|[[The Delphi Technique in Project Management]]
|-
|8
|Maria Vittoria
|Onori
|M vittoria
|[[Theory and Practice of Earned Value Management]]
|-
|
|Maria
|Saridaki
|SaridakiM
|[[BIM uses in project management]]
|-
|
|Marit Moberg
|Vossgård
|MAVO
|[[Kanban in Project Management]]
|-
|11
|Marouana Oulfat
|Afroukh
|S152191
|[[Managing Group Development using the Johari Window]]
|-
|
|Matilde Nygaard
|Pedersen
|
|
|-
|
|Mehmet Cagri
|Hekim
|
|
|-
|2
|Mie Louise Elsborg
|Drejer
|Mie Drejer
| [[VDC as a project management tool on construction projects ]]
|-
|
|Miguel Martínez
|Montaña
|
|
|-
|13
|Natacha
|Leduc
|natacha
|[[How to successfully go through the Five Stages of Team Development]]
|-
|
|Nicklas
|Risager
|
|
|-
|
|Niels Aksel
|Madsen
|
|
|-
|6
|Niels Christian
|Kirk
|Kirk1993
|[[Leading the group]]
|-
|
|Nikolaj Friis
|Hansen
|
|
|-
|
|Nikolaos
|Gavriilidis
|Nikolaos
|[[Cost Estimation Techniques for Projects]]
|-
|7
|Olöf Run
|Sigurjonsdottir
|s150964
|[[Critical Path Methods]]
|-
|
|Pablo Jose Guerra
|Guerra
|
|
|-
|
|Phillip
|Hasselbalch
|
|
|-
|7
|Ragna
|Helgadóttir
|S155273
|[[Lean Management and use of the Last Planner System in Construction Projects]]
|-
|
|Raivo
|Kalderauskis
|Raivo Kalderauskis
|[[Advantages of BIM for management of building projects ]]
|-
|14
|Raphaël
|Lassaux
|Lassauxr
|[[Management of remote project]]
|-
|
|Riccardo
|Ferranti
|
|
|-
|
|Rikke Klavstrup
|Wittendorff
|
|
|-
|
|Robin
|Hertenberger
|RobinH
|[[Stakeholder Management in Wind Power Projects]]
|-
|
|Romain
|Clouzeau
|Romain Clouzeau
|[[Including Risk Management in Construction Projects]]
|-
|
|Rosa Elisabeth
|Lindqvist
|
|
|-
|
|Sanka Chrishan
|Hettiarachchi Gunawardena
|
|
|-
|16
|Sean
|O'Regan
|OReganS
|[[Stakeholder Expectations Management]]
|-
|16
|Sebastian
|Bauer
|Sebastian Bauer
|[[Roadmapping in Program Management]]
|-
|10
|Selma Lind
|Jonsdottir
|S151176
|[[The Critical Path Method (CPM) in Project Management]]
|-
|
|Sheren
|Agbarie
|
|
|-
|
|Signe Skovmand
|Jakobsen
|SSJ
|
|-
|
|Siri
|Lassen-Urdahl
|
|
|-
|16
|Sofia
|Griggio
|SofiaGriggio
|[[The Agile methodology and its frameworks]]
|-
|4
|Sofie
|Olesen
|s104809
|[[Project Management Maturity Model]]
|-
|
|Somar Faraj
|Hassan
|
|
|-
|
|Stefan
|Schenk
|
|
|-
|5
|Stefan Borch
|Bilfeldt
|Stefan
|[[Risk-Reward Bubble Diagrams in Project Portfolio Prioritization]]
|-
|
|Stefán Geir
|Sigfússon
|
|
|-
|
|Sveinn
|Isleifsson
|
|
|-
|
|Swaroop Kumar
|Sahu
|
|
|-
|
|Thorgeir
|Sveinsson
|thorgeir11
|[[Earned Value Management (EVM) in construction projects]]
|-
|
|Tim
|Jonas
|
|
|-
|
|Timea-Denisa
|Merca
|
|
|-
|
|Timokleia
|Orfanidou
|
|
|-
|6
|Tobias Lyck Bjært
| Sørensen
|Tobias Sørensen
|[[Stakeholder Network]]
|-
|2
|Trine
|Marquardsen
|Trinemarquardsen
|[[Managing Stakeholders in Construction]]
|-
|
|Vittorio
|Albertazzi
|
|
|-
|16
|Wilfried
|Genier
|Wilfried_Genier
|[[Valuation methods in Project Portfolio Optimization - Focus on Real Options]]
|-
|
|Yann Mamy
|Randrianarison
|
|
|-
|
|Yin
|Jia
|
|
|-
|11
|Zsofia Dora
|Helmeczi
|s155698
|[[The use of Last Planner System in highly specialised construction projects]]
|-
|12
|Jakob
|Rolfsson
|s150892
|[[Scrum method]]
|-
|-
|8
|Tabea
|Ramirez Hernandez
|s152377
|[[Project Management in the Fuzzy Front End]]
|-
|-
|12
|Fridrik
|Karlsson
|s150948
|[[Scrum an Agile Framework]]
|-
</pre>