Effective Tools for Multiple Project Management
Manas Dalvi (Talk | contribs) |
Manas Dalvi (Talk | contribs) |
||
| (84 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
== Abstract == | == Abstract == | ||
| Line 6: | Line 5: | ||
This article gives an insight of Multiple Project Management (MPM), its necessity, classifications and causes for ineffective MPM. Moreover, it further explains the methodologies that one must consider while resolving these causes. In the view of limited empirical research on MPM, this article puts in a comprehensive overview of tools and its application in effective management of multi-projects. | This article gives an insight of Multiple Project Management (MPM), its necessity, classifications and causes for ineffective MPM. Moreover, it further explains the methodologies that one must consider while resolving these causes. In the view of limited empirical research on MPM, this article puts in a comprehensive overview of tools and its application in effective management of multi-projects. | ||
| − | |||
== Multiple Project Management (MPM)== | == Multiple Project Management (MPM)== | ||
| − | Multiple Project Management as the name suggests is the management of multiple projects operated simultaneously. These projects can be sub-projects of a big project, various projects in a program or similar projects across different portfolios. Projects are managed parallelly irrespective of their current | + | Multiple Project Management as the name suggests is the management of multiple projects operated simultaneously. These projects can be sub-projects of a big project, various projects in a program or similar projects across different portfolios. Projects are managed parallelly irrespective of their current status in their project life cycle. It has become more common in organizations and for project managers to handle several projects running simultaneously, known as multi-project management<ref name="MPM5"/> |
| − | Organizations exercise simultaneous management of projects on a daily basis to meet markets demands. It has also been suggested that up to 90%, by value, of all projects occur in the multi-project context. | + | Organizations exercise simultaneous management of projects on a daily basis to meet markets demands. It has also been suggested that up to 90%, by value, of all projects occur in the multi-project context<ref name="MPM2"/>. |
| − | With the lack of experienced professionals in every sector, project managers are now made to handle multiple projects in order to meet the accelerating demands of industry. Project Managers are tasked to lead more than one project because of resource limitation, these managers are referred to as multiple project management and such condition can also be referred to as management of a group of multiple projects. | + | With the lack of experienced professionals in every sector, project managers are now made to handle multiple projects in order to meet the accelerating demands of industry. Project Managers are tasked to lead more than one project because of resource limitation, these managers are referred to as multiple project management and such condition can also be referred to as management of a group of multiple projects<ref name="MPM4"/>. |
A Project Manager has to devout his majority of time for switching things between various projects that are undertaken, this may include planning, administrative and execution related input with different stakeholders at the same time. There can be a major time investment in menial jobs such a tracing project schedule, managing and communicating teams, setup and follow-up for reaching deadlines and many more. | A Project Manager has to devout his majority of time for switching things between various projects that are undertaken, this may include planning, administrative and execution related input with different stakeholders at the same time. There can be a major time investment in menial jobs such a tracing project schedule, managing and communicating teams, setup and follow-up for reaching deadlines and many more. | ||
These things are difficult even while handling a single project, whereas in MPM the degree of complexity rises exponentially with the increasing number of projects that are handled. | These things are difficult even while handling a single project, whereas in MPM the degree of complexity rises exponentially with the increasing number of projects that are handled. | ||
| − | In the view of MPM’s requirement, the potential for improvement is significant in management of simultaneous process | + | In the view of MPM’s requirement, the potential for improvement is significant in management of simultaneous process<ref name="MPM2"/> However, there is no universal tool that addresses every concern in MPM. So far, the MPM settings has limited empirical foundation, most contributions are either based on practical experiences or a research finding from one particular industry. There is little knowledge concerning which factors are context specific or universal<ref name="MPM6"/>Even though take into all these considerations in account, there are some generalized issues that have been encountered in a multi project managing environment. This article highlights the tools effective for tackling these issues, with their limitation as a generalized tool. |
| + | |||
===Project vs Program vs Portfolio vs Multiple Projects in Project Management=== | ===Project vs Program vs Portfolio vs Multiple Projects in Project Management=== | ||
| − | * Project: It is a task that has a certain delivery time, cost and quality. A project should ideally have a start date and an end date, generally goal oriented projects. These are short terms tasks undertaken as per business requirements. For | + | * Project: It is a task that has a certain delivery time, cost and quality. A project should ideally have a start date and an end date, generally goal oriented projects. These are short terms tasks undertaken as per business requirements. For e.g.: manufacturing of screens for cell phone. |
| − | * Program: A program is an array of multiple projects. It may consist of similar projects that contribute to a common goal. All the projects consisting in a program are usually interdependent and should be executed considering its effects in mind. For | + | * Program: A program is an array of multiple projects. It may consist of similar projects that contribute to a common goal. All the projects consisting in a program are usually interdependent and should be executed considering its effects in mind. For e.g.: Manufacturing cell phone. |
* Portfolio: Portfolio is a generalized profile of consisting of various programs or projects. For example, Manufacturing of mobile, earphones, camera, etc. | * Portfolio: Portfolio is a generalized profile of consisting of various programs or projects. For example, Manufacturing of mobile, earphones, camera, etc. | ||
* Multiple Project Management: A group of projects assigned to a particular manager with similar, dependent or unique characteristics. These projects can be from various programs or portfolios. | * Multiple Project Management: A group of projects assigned to a particular manager with similar, dependent or unique characteristics. These projects can be from various programs or portfolios. | ||
| Line 28: | Line 27: | ||
These differentiations can be better understood when referred to Fig 1. as it gives an overview of how each of these are unique. | These differentiations can be better understood when referred to Fig 1. as it gives an overview of how each of these are unique. | ||
| − | [[File:Fig1MPM.PNG|center|thumb|Fig1:Multiple Project Management Setting|500px]] | + | [[File:Fig1MPM.PNG|center|thumb|Fig1:Multiple Project Management Setting <ref name="MPM7"/>|500px]] |
Generally, MPM is compared to Portfolio Management since both of the cases requires interdisciplinary management to achieve diverse goals. However, Fig 2 gives an overview on how MPM differs from Portfolio Management. | Generally, MPM is compared to Portfolio Management since both of the cases requires interdisciplinary management to achieve diverse goals. However, Fig 2 gives an overview on how MPM differs from Portfolio Management. | ||
| − | [[File:Fig2MPM.PNG|center|thumb|Fig2:Comparison of Project Portfolio Management and Multiple Project Management|400px]] | + | [[File:Fig2MPM.PNG|center|thumb|Fig2:Comparison of Project Portfolio Management and Multiple Project Management <ref name="MPM3"/>|400px]] |
| − | ===Challenges with | + | |
| + | ===Challenges with MPM=== | ||
Considering the diversity of the projects handled in MPM, managers tackle challenges on a frequent basis. Looking at the prior art it is very difficult to tabulate these standards into a standard list as projects are unique and challenges associated with the can be uncertain at times. These challenges can vary as the nature of project varies from time to time and these natures of project can affect the efficiency of MPM. For instance, explained by J. Payne in his work of reviewing MPM, he gives three key differences a project because of which managing them would get complicated. The key differences between projects in a portfolio are in terms of size, required skills and urgency. | Considering the diversity of the projects handled in MPM, managers tackle challenges on a frequent basis. Looking at the prior art it is very difficult to tabulate these standards into a standard list as projects are unique and challenges associated with the can be uncertain at times. These challenges can vary as the nature of project varies from time to time and these natures of project can affect the efficiency of MPM. For instance, explained by J. Payne in his work of reviewing MPM, he gives three key differences a project because of which managing them would get complicated. The key differences between projects in a portfolio are in terms of size, required skills and urgency. | ||
| − | There are also some challenges that are specifically highlighted related to managing multiple projects | + | There are also some challenges that are specifically highlighted related to managing multiple projects <ref name="MPM1"/>. Daily interfaces with other projects, prior negotiation for resources and delivery related objectives are the ones mentioned. |
| − | Managing such project requires can also generate challenges for managers in their management and leadership roles. While managing, the manager can probably face challenges like switch between projects while planning, budgeting, monitoring and controlling. Whereas while leadership challenges can be bringing coordination and motivation of different project teams, since the level of attention to be allocated may differ from team to team. | + | Managing such project requires can also generate challenges for managers in their management and leadership roles. While managing, the manager can probably face challenges like switch between projects while planning, budgeting, monitoring and controlling. Whereas while leadership challenges can be bringing coordination and motivation of different project teams, since the level of attention to be allocated may differ from team to team<ref name="MPM4"/>. |
| − | Another research show hat with managing several smaller projects, the senior management has to invest their majority of time in control and monitoring as the chances of errors and accidents that can affect the chain are larger to that of one large project | + | Another research show hat with managing several smaller projects, the senior management has to invest their majority of time in control and monitoring as the chances of errors and accidents that can affect the chain are larger to that of one large project<ref name="MPM5"/> |
To summarize, there are no listed issues that can be found through previous researches. Every research addresses its unique problem. Manager assignment, dependencies, competencies between teams, resource allocation, complexities, etc. are to name few of the challenges. This article focuses on 3 key challenges that have been encountered, analyzed and resolved using some effective tools. These challenges are, | To summarize, there are no listed issues that can be found through previous researches. Every research addresses its unique problem. Manager assignment, dependencies, competencies between teams, resource allocation, complexities, etc. are to name few of the challenges. This article focuses on 3 key challenges that have been encountered, analyzed and resolved using some effective tools. These challenges are, | ||
| − | + | ||
| − | + | ====Project Alignment==== | |
| − | + | Generally, projects are considered as small tasks with an objective and a deadline. But while considering managing of multiple projects managers shall not look at it as independent entities. It can be beneficial if every project is executed in possibly the best way but as it offers a higher degree of flexibility, however in multiple project management this can lead to diverging far from overall objective if considered from an organization’s perspective. | |
| + | |||
| + | The process of aligning companies approaches towards achieving its objectives in definite period with a strategic methodology is commonly referred to as Project Alignment Process. One can get a better understanding of what project alignment means by referring to Fig 3. | ||
| + | |||
| + | [[File:Fig3MPM.PNG|center|thumb|Fig3:Project Alignment Management <ref name="MPM1"/>|400px]] | ||
| + | It can be seen from the figure that lack of strategic planning may miss align projects and its outcomes may differ from the required objectives. However strategic planning can effectively keep all projects synchronized. Since output of every project is directly related to company’s revenue, alignment in MPM can directly contribute in company’s favor. It can also lead in significant increase in project management efficiency leading to increase organization’s performance. | ||
| + | |||
| + | |||
| + | ====Control and Communication==== | ||
| + | In a cross functional project management, it is very important to monitor and control each project since they directly affect company’s performance. Every organization working in individual projects or a portfolio find it difficult to control and communicate with their teams on a daily basis. It becomes complicate especially when there are different teams working in different phases simultaneous. This leads to create disorder in the organization if communication is not carried effectively. Every manager finds it difficult to process the daily information about who in their team is responsible for what task. A paper has related communication to impact on the project throughout its life. It can be found out from Fig 6 that how improper communication can pile up and affect the project in its later part of cycle. | ||
| + | |||
| + | [[File:Fig6MPM.PNG|center|thumb|Fig6:Price of Poor Communication<ref name="MPM9"/>|400px]] There are numerous challenges faced by the manager considering control and communication is considered in managing Projects. Lack of focus, inability to cope with diversified projects, confusion, reduced motivation, confusion and conflicts over roles are some of the challenges that can be considered. Out of the mentioned challenges everything except roles and responsibilities is every individual’s concern and managers can work on their teams to ensure they feel motivated throughout. However, confusion and conflict over roles and responsibilities is something that the managers need to keep centralized so that each of their team members can refer and review their role in that particular project. Unclear responsibilities can further lead to ineffective collaboration and hence the project may lack of beneficial outcomes. | ||
| + | |||
| + | |||
| + | ====Learning and Knowledge Management==== | ||
| + | |||
| + | One of the major factors that lead to effective management of multiple projects is their reference from previous executions. Previous reference has proven to increase the efficiency of project deliverable as well as growth of the individuals. It has been found to be one of the core problems while managing multiple process that organization find it difficult to optimize as they fail at learning and storing information from their past errors <ref name="MPM1"/>. | ||
| + | |||
| + | This works well while tacking the known unknowns and unknown-unknowns that have occurred while execution of multiple projects. Just encountering these issues won’t benefit the organization if they are not documented. For instance, if a project has been executed 5 years ago and the manager is no more an employee of the company. In this case the complication occurred during the execution will be only restricted till the manager, who is no more a part of the organization. So, if the company has to execute a similar project, all the knowledge that was gathered is not accessible since it has not been documented. This will only lead in investing more time resolving the same issues again with additional resources. In multiple projects management, such cases will only affect individual projects which would further affect the combined outcome of that particular project portfolio. | ||
This article will further emphasis on the above stated problems and their solutions respectively. | This article will further emphasis on the above stated problems and their solutions respectively. | ||
| − | == Tools for | + | ==Tools for MPM== |
| + | |||
| + | ====Tools for effective Project Alignment==== | ||
| + | |||
| + | The tools that we would focus here in the multiple project alignment, construction of Project Alignment Matrix with later integration into Strategic Coverage Matrix is suggested <ref name="MPM10"/>. The Project Alignment Matrix refers to a set of strategies which would help achieve goals set for a particular project. These strategies are project specific and have been documented with achievements. Every objective of the project is assigned to a particular strategy from previous references, if there were no similar executions then there is no strategy assigned, however one that would be executed will be stored for future references. The implementation of project alignment and strategic coverage matrix can be seen in Fig 4 and Fig 5 respectively. | ||
| + | |||
| + | [[File:Fig4MPM.PNG|left|thumb|Fig4:Project Alignment Matrix<ref name="MPM10"/>|400px]] [[File:Fig5MPM.PNG|center|thumb|Fig5:Strategy Coverage Matrix<ref name="MPM10"/>|300px]] In project alignment matrix each of the project specific goals are listed along with their reference strategies which are derived from the project catalogues. For handling multiple projects each of these individual alignment matrixes are tabulated along with their reference strategies. This two-dimensional matrix gives an overview of the projects that are proposed in an organization with their respective strategies. These matrixes can also help us analyze which strategies are common for project specific goals as well as for individual projects in that portfolios. Using these matrixes managers can help optimize their projects to meet their outcomes with their objectives. The only drawbacks of these matrixes are that they are based on previous project data, which means it is difficult to categorize new goals or projects in these matrixes. | ||
| + | |||
| + | |||
| + | ====Tools for effective Control and Communication==== | ||
| + | |||
| + | Considering that the lack of understanding in roles and responsibilities can create a turbulence in the team, for e.g. team members would not have a clarity on whom to report or refer regarding that particular project. To bridge this gap internally a responsibility matrix is introduced to address this need and clarify repot structure with both operational and development authorities <ref name="MPM1"/>.[[File:Fig7MPM.PNG|right|thumb|Fig7:Responsibility Matrix <ref name="MPM1"/>|4500px]]The responsibility matrix illustrates a relationship between team members and their roles in the projects they are part of. This matrix will bring a clarity to everyone involved about the limitations of role they have for each particular project. Fig 7 shows a typical responsibility matrix proposed in a research paper. | ||
| + | This matrix illustrates the role of each employee from their respective departments in the projects that they are working on. In the above picture it can be seen that various departments collaboratively work on projects where L stands for the leader and M stand for the member. This matrix is a detailed overview of the projects, their status, teams associated, roles and responsibilities of each team members and the strategies that needs to be implemented on every project. This matrix becomes a centralized document of roles and responsibilities to enhance effective communication. However, the approach of each manager and the pressure that comes along for deliverable is totally dependent on the project as well as the manager’s management approach. | ||
| + | |||
| + | [[File:Fig8MPM.PNG|left|thumb|Fig8:RACI Matrix (This is demonstrational matrix created for reference and is not adopted from any of the online literatures)|450px]] This matrix describes the projects, their respective leaders and members, however it does not define the responsibilities of each individuals. An improvised version of responsibility matrix can be used where clear responsibility of each individual can be clearly defined. This matrix is generally referred to as Responsibility Assessment Matrix or RACI Matrix. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | RACI is a derived abbreviation for Responsibilities, Accountability, Consult and Informed, which are key responsibilities for achieving project objectives. However, this matrix offers managers freedom to modify the matrix as per their requirement. This can be addition to the four key responsibilities or it can be an altogether different responsibility. Following are the some of the alternatives to RACI matrix for responsibility assessment. | ||
| + | *RASIC (Responsibility-Accountability-Support-Informed-Consult) | ||
| + | *RACIQ (Responsibility-Accountability-Consult-Informed-Quality Review) | ||
| + | *DACI (Driver-Approver-Contributors-Informed) | ||
| + | *RAPID (Recommend-Agree-Perform-Input-Decide) ''RAPID is a responsibility assessment tool created by a Bain & Company for which a trademark has been registered.'' | ||
| + | *RATSI (Responsibility-Authority-Task-Support-Informed)<ref name="MPM8"/> | ||
| + | As you would be able to refer from Fig 8, projects and teams/person responsible are tabulated in rows and columns respectively. It can be seen that every team or individual has a certain responsibility to a particular project, there are cases where it can be seen that some teams are responsible and accountable for one project whereas some have only single responsibility towards the projects. | ||
| + | The above representation is a mere creation for demonstrating how a RACI matrix can be utilized in resolving conflicts for roles and responsibilities. It helps to extend clarity among team members about their contribution in the organization, however this is only limited to size of projects and length of organizations. Creating a RACI matrix for a complex project with longer duration, interchangeability in roles, etc. can make the process complicated as well as time consuming. | ||
| + | |||
| + | |||
| + | |||
| + | ====Tools for effective Learning and Knowledge Management==== | ||
| + | |||
| + | [[File:Fig9MPM.PNG|left|thumb|Fig9:Project Record Sheets <ref name="MPM1"/>|250px]] To resolve this issue Project Record Sheets should be used while implementing any project. This sheet can be restricted to a project or a project-specific goal. The purpose of these record sheets is usually addressing the problem faced in a project and define how it was resolved. It proves to be a strong assistance for managers who face similar problems during the execution. Fig 9 gives an overview of the Project Record Sheets that were described in one of the listed references. | ||
| + | |||
| + | As it can be seen from the Fig 9, the project record sheet are simple documents that are formed during an execution, which can act as a reference for future projects. Another implementation can be seen in these sheets by introducing ‘traffic light system’ structure. This system can be used to assign the review of management during the learning process. For example, it was used in a way that the green signal meant that there was no interference require from the senior management whereas red/amber signal stated the management interfered at varying levels. Moreover, every record sheet can have comments, wherein manager/individuals can list down the factors considered while resolving similar problem. These sheets can help managers and their organization to learn from previous mistake and enhance multiple project management in order to avoid reoccurrence of mistakes, adding up to unnecessary expenses <ref name="MPM1"/>. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Conclusion == | == Conclusion == | ||
| + | There are numerous problems faced by managers during handling multiple projects simultaneously. These problems can vary depending on a lot of variables which cannot be listed down a common one across every industry. This article emphasizes on three key problems that are faced by almost every organization but special focus is given on Small and Medium Enterprises as their limitation of resource can be higher when compared to larger organization. With the mentioned tools managers handling multiple projects can optimize the process, create clarity with teams and increase the quality of deliverables. Every tool has some limitation; however, it creates an opportunity for researchers to evaluate and come up with an advanced iteration. From the reader’s perspective this article can help in detecting these core challenges and implementing these specific tools for effective multiple project management. | ||
| + | |||
| + | As mentioned earlier that due to limitation in implementation of these methodologies is restricted to group of smaller projects. However, their practice can give a substantial increase in the output of companies running multiple projects simultaneously. The reader is also encouraged to use these methodologies while facing these issues and offer data that may extend opportunities in research across MPM domain. | ||
| + | |||
| + | |||
| + | ==Annotated Bibliography== | ||
| + | |||
| + | * '''Hedlberg, M and Höglander, A. (2013), Handling multi-projects: An empirical study of challenges faced in management.''' | ||
| + | Handling multi-projects: An empirical study of challenges faced in management, is a master thesis which is based on qualitative analysis carried out amongst five project managers working in different sectors and managing multiple projects. More emphasis is put upon four keys factors that have a considerable influence on effective MPM. These factors are mainly project phases, composing teams, MPM systems and choice of project methods. The thesis provides more of a practical insight on what are the concerns the managers while MPM. With this qualitative analysis, this would act as a reference for exploring more in the field of multi-project management considering its advancements. | ||
| + | |||
| + | *'''Payne, JH. (1995), Management of multiple simultaneous projects: a state-of-the art review.''' | ||
| + | Management of multiple simultaneous projects: a state-of-the art review illustrates challenges faced during multiple project management. The article gives a classification method for MPM problems known as 5C's (Capacity, Complexity, Conflict, Commitment and Context). It also clarifies the differences between projects handled in MPM based on the interfaces of integration, controls and the nature of projects, depending on its size, urgency and required skills. The article is a classic reference and has been used for evaluation of major prior art related to Multiple Project Management. | ||
| + | |||
| + | *'''Dooley, L., Lupton, G., O’Sullivan, D. (2004), Multiple project management: A modern competitive necessity.''' | ||
| + | Multiple project management: A modern competitive necessity, from which has been the key inspiration behind the article. The paper is a comprehensive structure which aids in effective management of multiple projects in a portfolio. The research carried out has an additional implementation of the theory proposed in small and medium enterprises in order to validate their efficiency. | ||
| + | |||
| + | |||
| + | ==References== | ||
| − | == Key | + | <references> |
| + | <ref name="MPM1">Dooley, L., Lupton, G., O’Sullivan, D. (2004), Multiple project management: A modern competitive necessity.</ref> | ||
| + | <ref name="MPM2">Payne, JH. (1995), Management of multiple simultaneous projects: a state-of-the art review.</ref> | ||
| + | <ref name="MPM3">Dye, L. and Pennypacker, J. (2000), Project Portfolio Management and Managing Multiple Projects: Two Sides of the Same Coin?</ref> | ||
| + | <ref name="MPM4">Patankaut, P. (2013), Key Drivers of Effectiveness in Managing a Group of Multiple Projects.</ref> | ||
| + | <ref name="MPM5">Hedlberg, M and Höglander, A. (2013), Handling multi-projects: An empirical study of challenges faced in management.</ref> | ||
| + | <ref name="MPM6">Engwall, M. and Jerbrant, A. (2002), The resource allocation syndrome: the prime challenge of multi-project management?</ref> | ||
| + | <ref name="MPM7">Patanakul, P. and Milosevic, D. (2008), The effectiveness in managing a group of multiple projects: Factors of influence and measurement criteria. </ref> | ||
| + | <ref name="MPM8">[https://en.wikipedia.org/wiki/Responsibility_assignment_matrix Responsibility Assignment Matrix] </ref> | ||
| + | <ref name="MPM9">Rajkumar, S. (2010) Art of communication in project management.</ref> | ||
| + | <ref name="MPM10">1Trendowicz, A., Shintani, K., Heidrich, J. (2011), Aligning Software Projects with Busniess Objectives.</ref> | ||
Latest revision as of 12:35, 28 February 2021
Contents |
[edit] Abstract
Due to exponential advancements across various sectors, project management professionals are expected to manage a portfolio of projects in their respective organizations due to limitation for resources. These portfolios can be interdisciplinary at times and their individual status in the cycle would differ. During such times it becomes difficult for these professionals to run parallel with these updates. Losing focus may lead to build an ineffective strategy, non-optimized resource management, lack in control and communication, etc. which would further affect the performance of the individual and also of the organization as a whole.
This article gives an insight of Multiple Project Management (MPM), its necessity, classifications and causes for ineffective MPM. Moreover, it further explains the methodologies that one must consider while resolving these causes. In the view of limited empirical research on MPM, this article puts in a comprehensive overview of tools and its application in effective management of multi-projects.
[edit] Multiple Project Management (MPM)
Multiple Project Management as the name suggests is the management of multiple projects operated simultaneously. These projects can be sub-projects of a big project, various projects in a program or similar projects across different portfolios. Projects are managed parallelly irrespective of their current status in their project life cycle. It has become more common in organizations and for project managers to handle several projects running simultaneously, known as multi-project management[1] Organizations exercise simultaneous management of projects on a daily basis to meet markets demands. It has also been suggested that up to 90%, by value, of all projects occur in the multi-project context[2].
With the lack of experienced professionals in every sector, project managers are now made to handle multiple projects in order to meet the accelerating demands of industry. Project Managers are tasked to lead more than one project because of resource limitation, these managers are referred to as multiple project management and such condition can also be referred to as management of a group of multiple projects[3].
A Project Manager has to devout his majority of time for switching things between various projects that are undertaken, this may include planning, administrative and execution related input with different stakeholders at the same time. There can be a major time investment in menial jobs such a tracing project schedule, managing and communicating teams, setup and follow-up for reaching deadlines and many more.
These things are difficult even while handling a single project, whereas in MPM the degree of complexity rises exponentially with the increasing number of projects that are handled. In the view of MPM’s requirement, the potential for improvement is significant in management of simultaneous process[2] However, there is no universal tool that addresses every concern in MPM. So far, the MPM settings has limited empirical foundation, most contributions are either based on practical experiences or a research finding from one particular industry. There is little knowledge concerning which factors are context specific or universal[4]Even though take into all these considerations in account, there are some generalized issues that have been encountered in a multi project managing environment. This article highlights the tools effective for tackling these issues, with their limitation as a generalized tool.
[edit] Project vs Program vs Portfolio vs Multiple Projects in Project Management
- Project: It is a task that has a certain delivery time, cost and quality. A project should ideally have a start date and an end date, generally goal oriented projects. These are short terms tasks undertaken as per business requirements. For e.g.: manufacturing of screens for cell phone.
- Program: A program is an array of multiple projects. It may consist of similar projects that contribute to a common goal. All the projects consisting in a program are usually interdependent and should be executed considering its effects in mind. For e.g.: Manufacturing cell phone.
- Portfolio: Portfolio is a generalized profile of consisting of various programs or projects. For example, Manufacturing of mobile, earphones, camera, etc.
- Multiple Project Management: A group of projects assigned to a particular manager with similar, dependent or unique characteristics. These projects can be from various programs or portfolios.
These differentiations can be better understood when referred to Fig 1. as it gives an overview of how each of these are unique.
Generally, MPM is compared to Portfolio Management since both of the cases requires interdisciplinary management to achieve diverse goals. However, Fig 2 gives an overview on how MPM differs from Portfolio Management.
[edit] Challenges with MPM
Considering the diversity of the projects handled in MPM, managers tackle challenges on a frequent basis. Looking at the prior art it is very difficult to tabulate these standards into a standard list as projects are unique and challenges associated with the can be uncertain at times. These challenges can vary as the nature of project varies from time to time and these natures of project can affect the efficiency of MPM. For instance, explained by J. Payne in his work of reviewing MPM, he gives three key differences a project because of which managing them would get complicated. The key differences between projects in a portfolio are in terms of size, required skills and urgency.
There are also some challenges that are specifically highlighted related to managing multiple projects [7]. Daily interfaces with other projects, prior negotiation for resources and delivery related objectives are the ones mentioned.
Managing such project requires can also generate challenges for managers in their management and leadership roles. While managing, the manager can probably face challenges like switch between projects while planning, budgeting, monitoring and controlling. Whereas while leadership challenges can be bringing coordination and motivation of different project teams, since the level of attention to be allocated may differ from team to team[3].
Another research show hat with managing several smaller projects, the senior management has to invest their majority of time in control and monitoring as the chances of errors and accidents that can affect the chain are larger to that of one large project[1]
To summarize, there are no listed issues that can be found through previous researches. Every research addresses its unique problem. Manager assignment, dependencies, competencies between teams, resource allocation, complexities, etc. are to name few of the challenges. This article focuses on 3 key challenges that have been encountered, analyzed and resolved using some effective tools. These challenges are,
[edit] Project Alignment
Generally, projects are considered as small tasks with an objective and a deadline. But while considering managing of multiple projects managers shall not look at it as independent entities. It can be beneficial if every project is executed in possibly the best way but as it offers a higher degree of flexibility, however in multiple project management this can lead to diverging far from overall objective if considered from an organization’s perspective.
The process of aligning companies approaches towards achieving its objectives in definite period with a strategic methodology is commonly referred to as Project Alignment Process. One can get a better understanding of what project alignment means by referring to Fig 3.
It can be seen from the figure that lack of strategic planning may miss align projects and its outcomes may differ from the required objectives. However strategic planning can effectively keep all projects synchronized. Since output of every project is directly related to company’s revenue, alignment in MPM can directly contribute in company’s favor. It can also lead in significant increase in project management efficiency leading to increase organization’s performance.
[edit] Control and Communication
In a cross functional project management, it is very important to monitor and control each project since they directly affect company’s performance. Every organization working in individual projects or a portfolio find it difficult to control and communicate with their teams on a daily basis. It becomes complicate especially when there are different teams working in different phases simultaneous. This leads to create disorder in the organization if communication is not carried effectively. Every manager finds it difficult to process the daily information about who in their team is responsible for what task. A paper has related communication to impact on the project throughout its life. It can be found out from Fig 6 that how improper communication can pile up and affect the project in its later part of cycle.
[edit] Learning and Knowledge Management
One of the major factors that lead to effective management of multiple projects is their reference from previous executions. Previous reference has proven to increase the efficiency of project deliverable as well as growth of the individuals. It has been found to be one of the core problems while managing multiple process that organization find it difficult to optimize as they fail at learning and storing information from their past errors [7].
This works well while tacking the known unknowns and unknown-unknowns that have occurred while execution of multiple projects. Just encountering these issues won’t benefit the organization if they are not documented. For instance, if a project has been executed 5 years ago and the manager is no more an employee of the company. In this case the complication occurred during the execution will be only restricted till the manager, who is no more a part of the organization. So, if the company has to execute a similar project, all the knowledge that was gathered is not accessible since it has not been documented. This will only lead in investing more time resolving the same issues again with additional resources. In multiple projects management, such cases will only affect individual projects which would further affect the combined outcome of that particular project portfolio.
This article will further emphasis on the above stated problems and their solutions respectively.
[edit] Tools for MPM
[edit] Tools for effective Project Alignment
The tools that we would focus here in the multiple project alignment, construction of Project Alignment Matrix with later integration into Strategic Coverage Matrix is suggested [9]. The Project Alignment Matrix refers to a set of strategies which would help achieve goals set for a particular project. These strategies are project specific and have been documented with achievements. Every objective of the project is assigned to a particular strategy from previous references, if there were no similar executions then there is no strategy assigned, however one that would be executed will be stored for future references. The implementation of project alignment and strategic coverage matrix can be seen in Fig 4 and Fig 5 respectively.
[edit] Tools for effective Control and Communication
Considering that the lack of understanding in roles and responsibilities can create a turbulence in the team, for e.g. team members would not have a clarity on whom to report or refer regarding that particular project. To bridge this gap internally a responsibility matrix is introduced to address this need and clarify repot structure with both operational and development authorities [7].
This matrix illustrates the role of each employee from their respective departments in the projects that they are working on. In the above picture it can be seen that various departments collaboratively work on projects where L stands for the leader and M stand for the member. This matrix is a detailed overview of the projects, their status, teams associated, roles and responsibilities of each team members and the strategies that needs to be implemented on every project. This matrix becomes a centralized document of roles and responsibilities to enhance effective communication. However, the approach of each manager and the pressure that comes along for deliverable is totally dependent on the project as well as the manager’s management approach.
RACI is a derived abbreviation for Responsibilities, Accountability, Consult and Informed, which are key responsibilities for achieving project objectives. However, this matrix offers managers freedom to modify the matrix as per their requirement. This can be addition to the four key responsibilities or it can be an altogether different responsibility. Following are the some of the alternatives to RACI matrix for responsibility assessment.
- RASIC (Responsibility-Accountability-Support-Informed-Consult)
- RACIQ (Responsibility-Accountability-Consult-Informed-Quality Review)
- DACI (Driver-Approver-Contributors-Informed)
- RAPID (Recommend-Agree-Perform-Input-Decide) RAPID is a responsibility assessment tool created by a Bain & Company for which a trademark has been registered.
- RATSI (Responsibility-Authority-Task-Support-Informed)[10]
As you would be able to refer from Fig 8, projects and teams/person responsible are tabulated in rows and columns respectively. It can be seen that every team or individual has a certain responsibility to a particular project, there are cases where it can be seen that some teams are responsible and accountable for one project whereas some have only single responsibility towards the projects. The above representation is a mere creation for demonstrating how a RACI matrix can be utilized in resolving conflicts for roles and responsibilities. It helps to extend clarity among team members about their contribution in the organization, however this is only limited to size of projects and length of organizations. Creating a RACI matrix for a complex project with longer duration, interchangeability in roles, etc. can make the process complicated as well as time consuming.
[edit] Tools for effective Learning and Knowledge Management
As it can be seen from the Fig 9, the project record sheet are simple documents that are formed during an execution, which can act as a reference for future projects. Another implementation can be seen in these sheets by introducing ‘traffic light system’ structure. This system can be used to assign the review of management during the learning process. For example, it was used in a way that the green signal meant that there was no interference require from the senior management whereas red/amber signal stated the management interfered at varying levels. Moreover, every record sheet can have comments, wherein manager/individuals can list down the factors considered while resolving similar problem. These sheets can help managers and their organization to learn from previous mistake and enhance multiple project management in order to avoid reoccurrence of mistakes, adding up to unnecessary expenses [7].
[edit] Conclusion
There are numerous problems faced by managers during handling multiple projects simultaneously. These problems can vary depending on a lot of variables which cannot be listed down a common one across every industry. This article emphasizes on three key problems that are faced by almost every organization but special focus is given on Small and Medium Enterprises as their limitation of resource can be higher when compared to larger organization. With the mentioned tools managers handling multiple projects can optimize the process, create clarity with teams and increase the quality of deliverables. Every tool has some limitation; however, it creates an opportunity for researchers to evaluate and come up with an advanced iteration. From the reader’s perspective this article can help in detecting these core challenges and implementing these specific tools for effective multiple project management.
As mentioned earlier that due to limitation in implementation of these methodologies is restricted to group of smaller projects. However, their practice can give a substantial increase in the output of companies running multiple projects simultaneously. The reader is also encouraged to use these methodologies while facing these issues and offer data that may extend opportunities in research across MPM domain.
[edit] Annotated Bibliography
- Hedlberg, M and Höglander, A. (2013), Handling multi-projects: An empirical study of challenges faced in management.
Handling multi-projects: An empirical study of challenges faced in management, is a master thesis which is based on qualitative analysis carried out amongst five project managers working in different sectors and managing multiple projects. More emphasis is put upon four keys factors that have a considerable influence on effective MPM. These factors are mainly project phases, composing teams, MPM systems and choice of project methods. The thesis provides more of a practical insight on what are the concerns the managers while MPM. With this qualitative analysis, this would act as a reference for exploring more in the field of multi-project management considering its advancements.
- Payne, JH. (1995), Management of multiple simultaneous projects: a state-of-the art review.
Management of multiple simultaneous projects: a state-of-the art review illustrates challenges faced during multiple project management. The article gives a classification method for MPM problems known as 5C's (Capacity, Complexity, Conflict, Commitment and Context). It also clarifies the differences between projects handled in MPM based on the interfaces of integration, controls and the nature of projects, depending on its size, urgency and required skills. The article is a classic reference and has been used for evaluation of major prior art related to Multiple Project Management.
- Dooley, L., Lupton, G., O’Sullivan, D. (2004), Multiple project management: A modern competitive necessity.
Multiple project management: A modern competitive necessity, from which has been the key inspiration behind the article. The paper is a comprehensive structure which aids in effective management of multiple projects in a portfolio. The research carried out has an additional implementation of the theory proposed in small and medium enterprises in order to validate their efficiency.
[edit] References
- ↑ 1.0 1.1 Hedlberg, M and Höglander, A. (2013), Handling multi-projects: An empirical study of challenges faced in management.
- ↑ 2.0 2.1 Payne, JH. (1995), Management of multiple simultaneous projects: a state-of-the art review.
- ↑ 3.0 3.1 Patankaut, P. (2013), Key Drivers of Effectiveness in Managing a Group of Multiple Projects.
- ↑ Engwall, M. and Jerbrant, A. (2002), The resource allocation syndrome: the prime challenge of multi-project management?
- ↑ Patanakul, P. and Milosevic, D. (2008), The effectiveness in managing a group of multiple projects: Factors of influence and measurement criteria.
- ↑ Dye, L. and Pennypacker, J. (2000), Project Portfolio Management and Managing Multiple Projects: Two Sides of the Same Coin?
- ↑ 7.0 7.1 7.2 7.3 7.4 7.5 7.6 Dooley, L., Lupton, G., O’Sullivan, D. (2004), Multiple project management: A modern competitive necessity.
- ↑ Rajkumar, S. (2010) Art of communication in project management.
- ↑ 9.0 9.1 9.2 1Trendowicz, A., Shintani, K., Heidrich, J. (2011), Aligning Software Projects with Busniess Objectives.
- ↑ Responsibility Assignment Matrix
