Successful Project Management

Revision as of 12:51, 27 February 2020

Building 310

Abstract

Value Proposition Canvas

Classically the value proposition canvas has two sides. The customer profile you clarify in which way you understand your customers needs. While the value proposition describes your intention to create value for your customers. The optimal starting position for each company is the fit between these two requests.

value proposition canvas

Customer Profile

• Gains: the benefits which the customer expects and needs, what would delight customers and the things which may increase likelihood of adopting a value proposition.
• Pains: the negative experiences, emotions and risks that the customer experiences in the process of getting the job done.
• Customer jobs: the functional, social and emotional tasks customers are trying to perform, problems they are trying to solve and needs they wish to satisfy.

Value Proposition

• Gain creators: how the product or service creates customer gains and how it offers added value to the customer.
• Pain relievers: a description of exactly how the product or service alleviates customer pains.
• Products and services: the products and services which create gain and relieve pain, and which underpin the creation of value for the customer Cite error: Invalid <ref> tag;

invalid names, e.g. too many.

Project Business Case

In order to successfully create a project charter as the basis of a project, it is necessary to sum up the information and data in so called business documents. These documents are “sources of information about the project's objectives” throughout out the project life cycle and should be reviewed periodically by the project managers (Managing Successful Projects with PRINCE2). The business case is one of these documents drawn up in the beginning of the project. In general it describes the “necessary information from a business standpoint to determine whether the expected outcomes of the project justify the required investment”. Managers are using it as a source of an easier decision making as well as to create a better overview over the key facts of the project. The process of defining the business need, analysing the situation and making recommendations of the future tasks is the main part of the business case. Therefore the purpose of the business case is to establish a mechanism that shows in which way the project is “desirable, visible and achievable” in its investment and serves therefore as a business justification ^[1].

Typically the project business case contains:

• a cost-benefit analysis;
• situational statement documenting the business problem or opportunity to be addressed including the value to be delivered to the organization;
• Identification of stakeholders affected and the needed scope;
• Identification of organizational strategies, goals, and objectives;
• Milestones, dependencies and roles and responsibilities.

All in all the business case provides an overview over the necessary cost, benefits but also expected dis-benefits and appropriate risk management and a valuable timescale ref name="Managing successful projects with PRINCE2®>AXELOS Limited(2017). Managing successful projects with PRINCE2® </ref>.

Meeting Strategies

A meeting can be defined in many ways, one of which is: “a focused interaction of cognitive attention, planned or chance, where people agree to come together for a common purpose, whether at the same time and the same place, or at different times in different places” ^[2]. Or as Kayser defines: “A meeting is a gathering where people speak up, say nothing, and then all disagree” Cite error: Invalid <ref> tag; refs with no content must have a name . The last definition indicates how unproductive and unconstructive meetings can be. In fact, research shows that even though managers spend more than 50% of his/her official work time in meetings, many meetings fail and cause great and unnecessary costs on wasted working time.

However, meetings can be very essential for larger groups of people working together, in order to agree upon key project management activities such as scheduling, cost, and quality. For this reason good meeting strategies can be helpful and in some cases necessary. There are many tools which can be applied in order to make meetings more efficient, and in this article some of the most common ones are explained.

Making meetings time efficient
Meetings will run throughout the whole project, but according to when the meeting is held there are different things to take into account. The project manager is responsible for facilitating the meetings and for identifying which challenges will be, or can be, met in different phases in order to achieve the overall goal of the project. One useful method is to make a model of the project phases and to identify possible challenges in each phase. One example of such a model can be seen in the figure to the right.

Example of project phases PMBOK® Guide Cite error: Invalid <ref> tag; refs with no content must have a name.

The project phase model is unique for every project, but usually the project goes through four phases: (1) Initiation (2) Planning (3) Execution (4) Closing. Each phase has different associated management activities ^[3].

Another tool which can be used together with the project phase model is to identify the costs throughout the whole project’s life cycle. In most projects the costs will be low in the beginning (Initiation) and will start to increase from the end of the planning phase (REferer til PMI her). It is important to make the meetings as efficient as possible when the costs are high, which such a model can help you identify.

A collection of tools for meeting strategies
Avoid unnecessary meetings
First of all it is important to avoid unnecessary meetings. This is especially important when the costs are high and the time is scarce, since people are not fond of wasting their time and this will cause higher costs. A good method is therefore to set up some guidelines for when it is acceptable to call a meeting in order to avoid unnecessary meetings. There are a couple of things that indicates when a meeting is needed ^[4] which are listed below:

• When unresolved issues are inhibiting the progress of a project or interdependent projects
• Decision making
• Idea generation
• Distribution of a compelling agenda prior to the meeting
• Celebration of reaching a milestone

Sometimes there is a need for communication, but a meeting is not necessary. In many cases this concerns the type of communication where only one person needs to speak (often the project manager). Examples of this type of communication are updates, delivery of information and presentations.

Plan the meeting in advance
Another important tool is to plan the meeting in advance. This both concerns the aspect of when and where the meeting should be held, but also which specific topics should be discussed at the meeting. These two aspects should be announced in good time to all attending the meeting, so that they are able to prepare.

Meeting minutes
Another good tool is meeting minutes. These contains important information from the meetings and are saved in the project management plan Referer til PMI her. It is a good idea to agree on a structure of the minute so that it takes the same structure for each meeting. The meeting minute is useful for people who could not attend the meeting to see what was discussed, to be able to go back in time and see what was discussed and agreed upon, but also to help keep a structure of the meeting..

The tools mentioned above are just a few among many. Other useful tools could be looking at you create valuable meetings and encourage the participation in meetings

Roles & Responsibilities in the Team

In order to create a functioning & successful working environment, the roles and responsibilities in the team have to be clarified. These roles and responsibilities are mostly defined in the so-called benefits management plan, which is the baseline document that guides the delivery of benefits during the program’s performance. The benefits management plan also identifies the associated activities, processes, and systems needed for the change driven by the realization of benefits; the required changes to existing processes and systems; and how and when the transition to an operational state will occur (The Standard for Program Management — Fourth Edition). All in all the project manager is maintaining the most role and has multiple responsibilities. He/ she is assigned to be the lead of the team and responsible for achieving the projects objectives. Generally his/ her reporting relationships are based on the organizational structure and the project governance. Apart from the specific technical knowledge and the duty to report the ongoing processes to several stakeholders, the project manager also has responsibilities regarding the team. Leaders should be motivating the team members, have a political and cultural awareness, manage conflicts and coaching when ever needed. New and not validated studies from Researcher R. Meredith Belbin show that each team has a number of different approaches to contribute to the group effort: · The Shaper In a team, the shaper role is performed by people who are dynamic and relish challenges. Rather than quit when faced with challenges, shapers maintain a positive mental attitude and strive to find the best ways to overcome challenges facing the team. · The Implementer People who play the implementer role in a team are those who actually get things done in the team. They are practical, efficient and well-organized. · The Completer/ Finisher Finishers have an eye for detail. In a team, they're regarded as perfectionists because they're the ones who detect errors or omissions and strive to ensure that the team adheres to deadlines. · The Coordinator Coordinators are seen as possessing the traditional team role. They're mature and confident in nature and possess great listening skill. · The Team Worker Team workers are the people who ensure the team remains united. They work toward resolving conflict or issues affecting the team’s dynamics. Team workers are very supportive of other team members and are thus popular within the team. · The Resource Investigator Resource investigators are inquisitive and enthusiastic in nature and possess great negotiating and networking skills. They are extroverts, which makes it easy for others to relate to them. · The Monitor-Evaluator These are the critical thinkers in a team. They're serious minded and cautious in nature. Rather than rush into decision making, they prefer to critically analyse information before making any conclusions. Monitor-evaluators lack the energy to motivate other team members and are deemed to be slow in decision making. · The Specialist Workers with expert knowledge in a particular area comprise the specialist role. Their contribution to the team is limited only to their area of expertise. Their priority is in maintaining their professional standards. Though they show great pride in their area of expertise, they show little or no interest in the expertise of others. · The Plants Plants are innovative members of the team. They come up with original approaches and ideas that help the team in solving problems or overcoming challenges.

Team development

Team development is part of what is called project resource management, which includes the processes to identify, acquire, and manage the resources needed for the successful completion of the specific project Cite error: Invalid <ref> tag; refs with no content must have a name . These processes consist of (1) Plan Resource Management (2) Estimate Activity Resources (3) Acquire Resources (4) Develop Team (5) Manage Team (6) Control Resources. All these processes help to ensure that the right resources will be available at the right time and place Cite error: Invalid <ref> tag; refs with no content must have a name .

The fourth process, Team Development is about improving the competencies, the interaction between team members and the overall environment of the team to enhance project performance Cite error: Invalid <ref> tag; refs with no content must have a name. Different sources ^[5] and Cite error: Invalid <ref> tag; refs with no content must have a name agree that teams are developed through four stages - called the FSNP model: Forming - Storming - Norming - Performing. First of all the team members meet and learn about the project and their formal roles and responsibilities. In the second stage the team begins to address the project work, technical work and the management approach. It is important that the team members are open to different ideas and perspectives at this point, otherwise the environment can become counterproductive. In the third stage the team starts to work together and they adjust their behaviors to support the team. Not all teams reach the last stage, since this requires a well-functioning unit. In this stage the team is independent and works through issues smoothly and effectively Cite error: Invalid <ref> tag; refs with no content must have a name.

Teamwork is a critical but important factor for project success which is why developing effective and dynamic teams is one of the primary responsibilities for the project manager. Six behaviors have been noticed to affect a high team performance:

• Using open and effective communication,
• Creating team-building opportunities,
• Developing trust among team members,
• Managing conflicts in a constructive manner,
• Encouraging collaborative problem solving, and
• Encouraging collaborative decision making.

Furthermore, it improves the performance if the team members get to know each other

A clear result of this is that it improves teamwork which in most cases leads to an improved completion of the project. Furthermore it strengthens personal skills and motivates the employees.

Project Stakeholder Management

Stakeholders can be defined as people, groups or organizations which could impact or be impacted by the considered project Cite error: Invalid <ref> tag; refs with no content must have a name . In a project the stakeholders could for instance be the owners, client and purchaser, but may as well be the project team, architect or a local community. These are just a few examples.

Stakeholder management deals with analyzes of the stakeholders expectations and their impacts on the project/program/portfolio. Furthermore it is about developing an appropriate strategy for effectively engaging stakeholders in project decisions, and the planning and execution of the work Cite error: Invalid <ref> tag; refs with no content must have a name. It is an important and useful tool for reducing complications and altercations. Some would even state that “The ability of the project manager to correctly identify and manage these stakeholders in an appropriate manner can mean the difference between success and failure” Cite error: Invalid <ref> tag; refs with no content must have a name. The Project Stakeholder Management can be divided into four processes:

1. Identifying Stakeholders
2. Plan Stakeholder Management
3. Manage Stakeholder Engagement
4. Monitor Stakeholder Engagement

Before engaging any stakeholders in your project, you need to identify and analyze them in order to place them in appropriate groups. This is the first process and will help you develop the right plan for communicating with the different types of stakeholders throughout the project ^[6]. The analysis of the stakeholders means placing them in categories according to their interests and their power. A possible division could be as illustrated in the Power/Interest Matrix to the right.

Power/Interest Matrix for grouping and prioritizing important stakeholders. Inspiration from MacDonald Cite error: Invalid <ref> tag; refs with no content must have a name

As illustrated in the Power/Interest Matrix each stakeholder category requires different treatments in order to keep them engaged in the project.

The next process is to plan the stakeholder engagement which is the process of developing approaches to involve stakeholders based on their needs, expectations, interests and potential impacts on the project Cite error: Invalid <ref> tag; refs with no content must have a name. This is important in order to interact effectively with stakeholders. The plan can be developed in the beginning of a project, but should be reviewed and corrected throughout the project. This plan should at least consist of a resource management plan, communication management plan and a risk management plan.

The third process of the Project Stakeholder Management is the process of communicating and working with the stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement Cite error: Invalid <ref> tag; refs with no content must have a name. Working with the stakeholders allows the project manager to increase the support and minimize the resistance from stakeholders. This requires different tools and techniques such as communication skills, conflict management, political awareness, negotiation skills and many more.

The final process is the monitoring of stakeholder engagement in which the project stakeholder relationships are monitored and strategies are tailored for engaging stakeholders through modification of engagement strategies and plans Cite error: Invalid <ref> tag; refs with no content must have a name. The purpose of this process is to either maintain or increase the efficiency and effectiveness of the stakeholder engagement activities as the project evolves and possibly changes. This process should be performed throughout the whole project. Also this process requires different tools such as decision making tools, data analysis and interpersonal and team skills.

The Triple Constraint in Project Management

The Iron Triangle of Project Management

The triple constraint in Project Management is often referred to as the Iron Triangle, where the three corners represent the triple constraints: time, cost and scope.

It is important to establish the goals and requirements (the scope) in the beginning of the project. By defining the scope of the project, you ensure that everybody is working towards the same goal and knows how the final deliverable should turn out. If a clear scope for the project is not defined - and documented - a lot of minor add-ons can end up turning the final deliverable into a completely different project than intended. Additional features can also result in changes in the budget and time constraints as you have to increase the project cost by e.g. assigning more people to the project or extending the project time frame. Constant awareness of changes in the project scope gives you the possibility to discuss the trade-offs within the triple constraints and thereby adjust the changes and thereby keeping the project on track ^[7].

A detailed description of the project scope can be a good foundation for the overall understanding of the time constraint, as an estimate of the project can be made. If you want the project to be done before time it will probably cost you if you are not willing to lack on the project requirements established in the scope, as a short deadline requires extra resources in order to get the wanted work done in the wanted quality. The establishment of the project time frame can thereby form the basis for the project costs.

The triple constraint in project management is focusing on the output in the management expressed by operating within a set of boundaries consisting of the project time cost and scope. This means that changes in one of the factors will affect the outcome of the two other factors. The triple constraints therefore need to be balanced, as it all depends on trade-offs, in order to achieve a successful project.

Key Performance Indicators

In order to determine if the project is on track Key Performance Indicators (KPI’s) can be used. KPI’s makes the performance of the project measurable by providing a value, that indicates how effectively the project is at the given moment compared to the project scope. In order to get a measurable performance indicator, the person in charge of the project (project manager) typically chooses some key points (about 2-5) concerning the project objectives, effort and cost and/or the project performance^[8].

Scope Control

Scope Control Processes - 4 Steps

In order to control a project scope control must be handled. Scope Control processes makes it possible to identify possible conflicts in connection with the approved Project Scope Statement and thereby to manage these conflicts. In order to manage Scope control implemented changes of the scope must be identified, evaluated, proposed and then authorised. Always ensuring the scope of the projects is considered very important when managing project changes throughout the project life cycle, as changes may cause changes in the deliverables and thereby the functionality, resources needed and overall completion of the project.

Earned Value Analysis

In order to ensure the project progress Earned Value Management can be used to indicate the overall performance of the project. An Earned Value Analysis is based on the comparison of the work performed and the work planned and can thus be used as cost (CPI) and schedule (SPI) control in project forecasting. By the use of EVM decision making can be simplified, as it provides quantitative data, that can easily be communicated^[9].

Scenario analysis

In order to identify the risks in a project different tools, such as Scenario Analysis, can be used. The Scenario Analysis is used to analyze future events with different outcomes in order to present several developments from the given project. This analysis does not rely on any past data or observations but should take all scenarios to be plausible. By making a scenario analysis at the beginning of the project the risk can be easily identified and thereby managed throughout the project phases^[10].

Risk Matrix

Risk Matrix

A risk matrix can be used for assessing the risks of the project by defining the level of the risks by its impact and likelihood.

Value Proposition Canvas

Classically the value proposition canvas has two sides. The customer profile you clarify in which way you understand your customers' needs. While the value proposition describes your intention to create value for your customers. The optimal starting position for each company is the fit between these two requests (Value Proposition Design: How to Create Products and Services Customers Want).

Customer Profile

• Gains: the benefits which the customer expects and needs, what would delight customers and the things which may increase the likelihood of adopting a value proposition.
• Pains: the negative experiences, emotions, and risks that the customer experiences in the process of getting the job done.
• Customer jobs: the functional, social and emotional tasks customers are trying to perform, problems they are trying to solve and needs they wish to satisfy.

Value Proposition

• Gain creators: how the product or service creates customer gains and how it offers added value to the customer.
• Pain relievers: a description of exactly how the product or service alleviates customer pains.
• Products and services: the products and services which create gain and relieve pain, and which underpin the creation of value for the customer.

SWOT Analysis ^{[11] [12]}

SWOT Analysis

The SWOT analysis tool is a decision-support tool that consists of four main sectors that go as “Strengths”, “Weaknesses”, “Opportunities” and “Threats”. Through the process of this analysis the steps are:

• The stakeholders identify the factors inside an organization, increasing (strengths) or decreasing (weaknesses) its performance.
• The stakeholders further investigate the factors outside an organization’s structure, growing (opportunities) or reducing (threats) its performance.

When all the information about the four aforementioned factors are gathered, the analysis procedure begins, to determine the effects all the factors have on the net value of the organization and the ways they can control it. In order to eliminate the negative effects of weaknesses and threats, not only presently but in the future as well, in many cases, scenario planning is implemented. Finally, based on the results of these procedures, future plans and actions are established. More specifically, different strategies are being followed, based on the missions and goals the organization has set. Those strategies should have as their main focus to evolve strengths, eliminate weaknesses, use the opportunities wisely and respond effectively to threats.

Design Thinking ^[13]

Design Thinking Stages and Interactions

Design thinking is a tool that processes the potential issues an organization has and redefines them in order to differentiate the strategies and simplify them, evolving around who the design of the product or service is for. The main aim of this tool is the solution itself by combining thinking and brainstorming with hands-on procedures. Design thinking is extremely useful when it comes to avoiding faults since its main goal is to redefine problems based on humans and the way they are thinking. Some of the most commonly used techniques in order to implement a design-oriented way of thinking is sketching and conceptualization, as well as testing those to analyze the derived outcomes and the effect they have on the people they are made for.

The steps followed when using "Design Thinking" as a tool are:

• "Empathise", meaning that the person who is trying to solve the problem understands it deeply. A thorough investigation of the area of concern is vital in order to reach the root of the problem and its causes. Since design thinking is a human-centered procedure, empathy is a key to it.
• "Define", meaning that the clear problem has to be defined and established in order for the next steps to be implemented. The more clarity in the problem definition, the more helpful it is for the following steps.
• "Ideate", is the part when the generation of ideas and brainstorming is taking place. At this stage, it is not a matter of the quality of the ideas, but more about the quantity.
• "Prototype", where a maquette is created in order for the people to be able to implement some of the most ambitious ideas from the previous step and see the effects on the scaled-down product.
• "Test" the completed program using the best solution deriving from the previous phase. Alterations may occur after this step since all the faults will be identified.

As can be seen in the figure above, during the design thinking the interaction of all the stages is not linear and the stages may take place in a different order than shown.

Gantt Chart ^[14]

Gantt Chart Example

A Gantt chart is a project management tool created in 1917 by Henry Gantt that can be used simply on a paper, or in Excel for more complex projects. It is a horizontal bar chart and its main advantage is that it provides a full insight on all the tasks and the clear schedule. The horizontal axis represents the time span, while the vertical axis the tasks. The horizontal rectangles are showing the time span or the deadline for each one of the tasks. When the rectangle is solid, it indicates that the task is completed, and when it is blank the task is ongoing and finally, when the rectangles are overlapping it means that two tasks that require less time, can be completed at the same time. A vertical dotted line is added when a report date is established.

The advantages deriving from the Gantt Chart are:

• It is an easy and clear way to showcase all the tasks and milestones of a project.
• Enables efficient time management by offering access to all the different dates and deadlines and adjusting to any time span.
• Offers a clear picture of every team member's tasks.
• Provides an insight into the percentage of the tasks and the amount and status of tasks that are nearly or entirely completed.
• Makes it easier and more sufficient to manage and coordinate the team by having everything illustrated in one place.

Dealing with conflict in project management^{[15] [16]}

Conflict Management Styles

It is of big importance to identify a conflict at an early stage and being able to dissolve it before it gets dangerous, not only to the team responsible for the project but also to the project itself. An organization should thus understand the importance of the well-managed conflicts to the projects because if failed to be resolved conflicts can in extreme conditions lead to the failure of the project. Some of the most common types of conflict are the background, personal beliefs, and background of the individuals, as well as bad communication.

When it comes to conflict management, five styles have been established so far as the most effective ways to eliminate it, based on the level of cooperativeness and assertiveness that people involved are willing to consume on solving the conflict.

• "Accommodating": One side of the conflict does not care about his or her personal needs, and sets a priority to please the others
• "Collaborating": Assuming that people are understanding and trusting each other, used when the level of conflict is not very high
• "Compromising": Offering fast solutions, but one all the people have the same power so they have to come to a decision together
• "Competing": Offering fast solutions, but one person is having more power and thus has the final call on the problem
• "Avoidance": A person involved in the conflict abandons or delays the solution of the conflict

How to wiki

How to add a reference? Do it in the text like this: write ^[17] Refer to the same reference again by writing: Cite error: Invalid <ref> tag; refs with no content must have a name

It automaticly print it under References :-)

How to add a picture: Click on the botton "Upload file" on the left. Give the file a name you can remember Go into the wikipage to edit. write: [File:name.jpg|300px|thumb|right|picture text]

Application

Limitations

Annotated Bibliography

References

1. ↑ AXELOS Limited(2017). Managing successful projects with PRINCE2®
2. ↑ Romanco, N. and Nunamaker, J. (2001) Meeting Analysis - Findings from Research and Practice. Proceedings of the 34th Annual Hawaii International Conference on System Science, http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.570.6650&rep=rep1&type=pdf
3. ↑ Project Management Institute, Inc. (2017). Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th Edition), https://app.knovel.com/hotlink/toc/id:kpGPMBKP02/guide-project-management/guide-project-management
4. ↑ Rogelberg, S. & Scott, C. & Kello, J. (2007) The Science and Fiction of Meetings - MIT Sloan Management Review - Volume 48(2), https://orgscience.uncc.edu/sites/orgscience.uncc.edu/files/media/Rogelberg%20et%20al.%20-%202007%20-%20The%20science%20and%20fiction%20of%20meetings.pdf
5. ↑ Stott, K. & Walker, A. (1995) Teams Teamwork & Teambuilding
6. ↑ MacDonald, J., Business2Community (2016) Stakeholder Identification and Analysis Made Easy for Project Managers, https://www.business2community.com/strategy/stakeholder-identification-analysis-made-easy-project-managers-01440041
7. ↑ Van Wyngaard, C.J., Pretorius, J. H. C., Pretorius, L. (2012). Theory of the triple constraint – a conceptual review, IEEE International Conference on Industrial Engineering and Engineering Management
8. ↑ Klipfolio Inc. (2020). What is a KPI? Measure your performance against key business objectives, https://www.klipfolio.com/resources/articles/what-is-a-key-performance-indicator//
9. ↑ Warburton, Roger David Hand (2008). The practical calculation of schedule variance in terms of schedule, https://www.pmi.org/learning/library/practical-calculation-schedule-variance-7028//
10. ↑ Wikipedia (2019). Scenario analysis, https://en.wikipedia.org/wiki/Scenario_analysis//
11. ↑ Jones, G. & George, J. (2012) Essentials of Contemporary Management (7th edition), McGraw-Hill Education
12. ↑ Watkins, R. & Leigh, D. (2009) Handbook of Improving Performance in the Workplace, https://onlinelibrary-wiley-com.proxy.findit.dtu.dk/doi/pdf/10.1002/9780470592663.ch24
13. ↑ Friis, R. & Siang, Y. (2019) 5 Stages in the Design Thinking Process, https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process
14. ↑ Rouse, M. (2019) The Gantt chart, https://searchsoftwarequality.techtarget.com/definition/Gantt-chart
15. ↑ Yusuf, A. & Pretorius, J. (2017), Conflict Management in Projects, https://ieeexplore-ieee-org.proxy.findit.dtu.dk/stamp/stamp.jsp?tp=&arnumber=8095588&tag=1
16. ↑ Moriaty, T. (2018), The 5 styles of conflict management, https://www.plantservices.com/articles/2018/human-capital-5-styles-of-conflict-management/
17. ↑ Author (year) title, link