Project Management Maturity Models - Revision history

Tkokotas at 14:08, 18 December 2018

2018-12-18T14:08:03Z

← Older revision		Revision as of 14:08, 18 December 2018
Line 1:		Line 1:
			''Developed by Sofie Olesen''


	== Abstract ==		== 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;		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;

S104809 at 21:54, 26 September 2016

2016-09-26T21:54:20Z

← Older revision		Revision as of 21:54, 26 September 2016
Line 28:		Line 28:


	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>]]		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 ====		==== PMMM as first step in changing culture in an organisation ====

S104809 at 21:52, 26 September 2016

2016-09-26T21:52:49Z

Show changes

S104809 at 21:04, 26 September 2016

2016-09-26T21:04:52Z

← Older revision		Revision as of 21:04, 26 September 2016
Line 67:		Line 67:
	== Annotated bibliography ==		== Annotated bibliography ==
	Brooks, N.; Clark, R. 2009: Using Maturity Models to Improve Project Management Practice		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?		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 ..		* 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		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		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'		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.

S104809 at 20:51, 26 September 2016

2016-09-26T20:51:34Z

← Older revision		Revision as of 20:51, 26 September 2016
Line 24:		Line 24:
	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 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>.		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.

	~~As illustrated in figure XX~~, ~~level 3-5 are~~..		[[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 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>]]
			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 ====		==== PMMM as first step in changing culture in an organisation ====
Line 53:		Line 54:

	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.		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 ==		== Reflections ==
Line 63:		Line 66:

	== Annotated bibliography ==		== 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 ==

	<references />		<references />

S104809 at 20:39, 26 September 2016

2016-09-26T20:39:11Z

← Older revision		Revision as of 20:39, 26 September 2016
Line 24:		Line 24:
	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 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;		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>.

	~~;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..		As illustrated in figure XX, level 3-5 are..

S104809 at 20:30, 26 September 2016

2016-09-26T20:30:37Z

Show changes

S104809 at 20:14, 26 September 2016

2016-09-26T20:14:21Z

← Older revision		Revision as of 20:14, 26 September 2016
Line 11:		Line 11:

	== Big Idea ==		== 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>. ;		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		# Performed/Awareness/ad hoc
	# Managed/ Repeatable		# Managed/ Repeatable
Line 20:		Line 20:

	==== Concept ====		==== 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 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 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.

S104809 at 20:10, 26 September 2016

2016-09-26T20:10:08Z

← Older revision		Revision as of 20:10, 26 September 2016
Line 11:		Line 11:

	== Big Idea ==		== 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];		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		# Performed/Awareness/ad hoc
	# Managed/ Repeatable		# Managed/ Repeatable
Line 17:		Line 17:
	# Quantitative managed/managed		# Quantitative managed/managed
	# Optimised		# 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].		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 ====		==== Concept ====
Line 65:		Line 65:

	== Reflections ==		== 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 ==		== Annotated bibliography ==

S104809 at 20:02, 26 September 2016

2016-09-26T20:02:23Z

← Older revision		Revision as of 20:02, 26 September 2016
Line 38:		Line 38:
	As illustrated in figure XX, level 3-5 are..		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.		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 ====		==== PMMM as first step in changing culture in an organisation ====
Line 53:		Line 53:

	== Limitations ==		== 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…~~		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…		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~~ ====		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 ==		== Annotated bibliography ==

			== References ==

			<references />