Project Management: Why It is So Important? Elevate Your Career by Realising the Characters, Elements, Types, Methods and Recent Trends!

Abstract 
Project management is a process that allows project managers to plan, execute, track and complete projects with the help of a project team. To do so, they must use project management principles, skills, methodologies and tools to lead team members through each of the project management steps which are known as the project lifecycle.

However, project management can’t be defined in one paragraph. Project management: what it is and why it is important
For the past two years, you have been driving around the roadworks on your way to work. Every day you wonder why there are always delays because the site just won't get done. Does this sound familiar?

For such tasks there is project management, whose job it is to plan and monitor the implementation from start to finish. But what exactly is project management and what strategies should be used to avoid such delays?

Keywords 
Project Management, PM Tools and Techniques, PERT, CPM
Early Start Time, Early Finish Time, Late Start Time, Delays 

Learning Outcomes 
After undergoing this article you will be able to understand the following:
1. Project Management What's exactly: An Introduction
2. Why project management is important
3. What are the basic concepts of project management
4. How many types of project management ?
5. What are the methods of project management ?
6. What's the role of the project manager
7. What are Common tools and technologies in project management 
8. What strategies are essential for Success of project management?
9. Conclusion
10. FAQs
References 
1. Project Management: What's exactly: An Introduction?

Project management is a process that allows project managers to plan, execute, track and complete projects with the help of a project team. To do so, they must use project management principles, skills, methodologies and tools to lead team members through each of the project management steps which are known as the project lifecycle.

However, project management can’t be defined in one paragraph. In this guide, we’ll cover the basic concepts you need to know to understand what project management is, the stages of the project management process, different types of project management approaches and the tools you can use for managing projects.

In addition, you’ll need project management software to plan, execute and track projects. ProjectManager, for example, has the project planning, scheduling and tracking features you need to manage timelines, resources, costs and teams in one online tool. Use our Gantt charts, kanban boards, and calendars to create project schedules and assign work with real-time resource availability. 

2. Why project management is important?
Project management unites clients & teams, creates a plan for on time & on budget delivery, and gets stakeholders on the same page. But the importance of project management goes beyond that. Discover 12 benefits & how project management delivers incredible value & ROI on projects.

Here are top benefits and outcomes that strong project management and good project managers can deliver for projects and stakeholders:

More Impactful Project Outcomes

Improved Project Team

Better Alignment & Control

Better Productivity

On Time Completion

Within Budget Delivery

Consistent High Quality

Deliverables at least and optimised

Effective Resolution Of Project Risks

Efficient Resource Management

Detailed Project Tracking 

Reporting of projects on time 

Effective Decision-Making

Effective Problem-Solving

Continuous Improvement 

Learning From Past Projects

Enhanced Remote Work 

Dynamic Management 

Collaborations for effective governance 

Satisfied Clients

 Stakeholders benefit 
3. What are the basic concepts of project management?

Project management focuses on planning and organizing a project and its resources. This includes identifying and managing the lifecycle to be used, applying it to the user-centered design process, formulating the project team, and efficiently guiding the team through all phases until project completion.

Value of Project Management

Through proper project management, you can assure that the purpose/vision and goals of the project are maintained, all while supporting the audiences’ tasks and objectives.  Additionally, you avoid risks and effectively and efficiently use your available resources.  It also helps the team members to understand their responsibilities, the deliverables expected, and the schedule everyone needs to follow to complete the project on time and within budget.

Areas within Project Management

The Project Management Institute (PMI) has identified nine areas of knowledge within project management:

  1. integration management
  2. scope management
  3. time management
  4. cost management
  5. quality management
  6. human resource management
  7. communication management
  8. risk management and
  9. procurement management

Building a Team and Encouraging

Keep in mind that members on your team may fulfill one role or may fulfill many. 

Regardless of the size of the team, it’s important to identify how the team will communicate and collaborate with one another.  This includes discussing upfront:

  • Planned/ regular meetings
  • How formal they will be
  • Whether meetings will be held in-person, virtually, or both
  • How the team will share and collaborate on documents
  • Where documents will be stored and how they will be version controlled
  • Workflow for decisions and approval

Project Phases, Life Cycles, and Incorporating User-Centered Design Principles

Projects are typically broken down into phases.  Each phase outlines the work that needs to be done and who is involved.  Generally, in order for a phase to be considered complete, specific deliverables need to have been completed and handed off.  Some project teams, however, do choose to implement fast tracking, which is when phases are overlapped. 

A lifecycle defines the beginning and end of the project; it represents all of the phases together.  When defining the project’s life cycle, the first phase is noted as Step 0.  It usually captures the visioning and conceptualizing of the project.  According to the Project Management Institute, most life cycles have four or five phases but some may have more. 

The most common lifecycle approaches are Waterfall and Agile., Regardless of the approach you choose, you will need to incorporate user-centered design (UCD) best practices and methods.  

Project Plan and Charter Agreement

Make sure when outlining your plan, that throughout it you note how you plan to include user-centered design best practices and methodologies. 

Most project plans outline:

  • Objectives
  • Scope, which correlates to the requirements
  • Resources, including technology, budget, and 
  • Schedule 
  • Team roles and responsibilities
  • Assumptions and Limitations 
  • Dependencies and Contingency 
  • Risk assessment 
  • Management plan
  • Change control plan

At the end of the project plan, depending on your team’s needs, you may choose to include a charter agreement. A charter agreement is typically a one page document that has the sponsor of the project sign off that they agree to the work to be done as outlined by the team in the project plan. Remember, however, that successful teams understand upfront that things happen and that they’ll need to adapt. The project plan establishes the baseline for how you assume the project will happen and then provides information about the process for taking changes into account, should they arise.

Creating a Schedule

Schedules are an important part of project management because they help you measure your progress as the project moves along.  They also help to outline how each team member’s part fits into the overall picture and demonstrate the dependencies.

Schedules reflect the life cycle broken down into specific deliverables and touch points.  It defines what needs to be done and who is the point of contact responsible for the work. 

4. How many types of project management ?
Many types of project management have been developed to meet the specific needs of certain industries or types of projects. Three of those types are waterfall, agile, and lean.

Waterfall

Waterfall is often called the “traditional” project management approach. In traditional approaches, projects are completed one stage at a time and in sequential order—like a waterfall would flow down a collection of rocks.

When to use waterfall

The waterfall model is effective for projects that involve several steps to production. For projects where one task can't be completed without one being done before it, this is the most efficient outline system to incorporate.

2. Agile

Agile is an approach to project management that is built on small, incremental steps. It is designed to be able to pivot and incorporate changes smoothly, making it popular among projects where unknowns and new developments are common.

Agile’s 12 principles are enshrined in the Agile Manifesto, which was written in 2001 by project managers in software development.

When to use Agile: 

Agile is best used in projects in industries that expect a certain amount of volatility, or in projects where you will not be able to know every detail from the outset. Agile project management is very popular in software development, where changes are almost constant. You might also use an Agile approach when you are launching a new product and are not fully aware of where pain points might lie until closer to the end of the project.

3. Lean

Lean is a project management style with roots in the manufacturing industry (Toyota’s cars, to be exact). It aims to cut down on waste and increase efficiency. Key Lean principles include emphasising value from the customer’s perspective and mapping out your entire project in the initial stages to see where to generate value and cut waste.

When to use Lean:

Lean can be a useful project management approach to adopt when you’re looking to reduce costs, shorten timelines and improve customer satisfaction. It is best used for projects that anticipate some flexibility and change.


5. What are the methods of project management accross the industry?

The project manager is a staple role in many different industries. Though the fundamentals of what they do are the same—lead projects to fulfill goals while staying on schedule and within budget—the details of what they do can differ.

  • Construction: A construction project manager organises people and resources to oversee the process of building structures like houses and office buildings. The project manager generally works closely with architects and engineers.

  • IT: A project manager in IT works with teams to solve IT-related problems in a company. They can, for example, carry out a project to install new software across a company, update networks or help roll out cloud computing services.

  • Software development: Software project managers orchestrate project teams to develop new software and software updates. They may have professional experience in developing software themselves.

  • Health care: A project manager in health care leads projects in hospitals and other health care facilities. Health-care project managers often have to have a good understanding of health care legislation.

  • Energy: In energy, project managers carry out projects that develop new energy infrastructure or improve existing ones. They might also work to roll out energy-efficient practices at individual organisations.

  • Marketing: A project manager in marketing might work at a tech company, advertising firm, large retailer, or any number of other organisations that have marketing arms. Projects can include marketing campaigns, research efforts, and new product launches.


6. What's the role of the project manager?

As the name suggests, project managers are responsible for projects from initiation to close, making sure the work gets done efficiently and satisfactorily. As team leaders with day-to-day schedules that are constantly changing, a static project manager job description would be hard to come by. Days can be filled with planning the project process, creating a budget, managing a team or communicating with clients.

Project managers play the lead role in planning, executing, monitoring, controlling, and closing out projects

They are accountable for the entire project scope, the project team and resources, the project budget, and the success or failure of the project.

The top skills you need to succeed as a project manager are
  • Planning and forecasting. It goes without saying, but proper project management requires skilled planning. 
  • Risk management. 
  • Budgeting. 
  • Tracking and monitoring. 
  • Project management methodologies.
  • Meeting facilitation. 
  • Subject matter expertise. 
  • Quality management.

7. What are Common tools and technologies in project management ?

The common tools and techniques used in project management are given below :
  1. Process Modeling and Management tools : Process modeling simply means to model software processes. At first, developers need to fully understand process and work of software, then only they can be able to model process. This tool represents key elements of process that are important. So, it makes it easier to perform work tasks in efficient and proper manner.
  2. Project Planning tools : Project planning simply means to plan and set up project for successful development within timeframe. It includes defined stages or steps to define objectives of project with designated resources, clarify scope of what should be done, and then develop list of tasks that are needed to be done to complete it. Tools used for project planning can be CPM (Critical Path Method) and PERT (Program Evaluation and Review Technique). Both of them are used for finding parallelism, eliminating bottlenecks in projects, and scheduling activities of project. Some tools that make planning of project in efficient way are Trello, Nifty, Asana, TeamGantt, etc.
  3. Risk Analysis tools : Risk analysis simply means to identify and analyze errors or defects or any issue that can cause negative impact and result in the changed outcome and objectives of project. The analysis is done so that organization can fix issue or remove error to avoid effect caused by them. These tools help in identifying risks and are useful for binding risk table. These provide detailed guidance in the identification and analysis of risks. The risks identified can be categorized into catastrophic, critical, marginal, or negligible. A cost is associated with each risk which can be calculated at each stage of development. Some tools and techniques are Delphi technique, Information gathering technique, Checklist analysis, etc.
  4. Project Management tools : Project management simply means to track or control progress and tasks of project. These tools are extension of project planning tools. These tools are generally used to update pans if require and schedule project. These tools make Project Management more effective and efficient. Some tools are Gantt chart, mind map, WBS chart (Work Breakdown Structure), etc.
  5. Metrics and Management tools : Metric management tools are very good for software as they provide very quick and easy way to track software development, set goals, and measure performance. These tools help in capturing and finding out specific metrics that are useful and provide overall measure of quality. These tools focus more on process and product characteristics. For example, “defects per function point”, “Line Of Code/person-month”.
  6. Quality Assurance tools : Quality assurance in software engineering simply means to maintain level of quality of software product by focusing on each step of process of development or production and delivery. It prevents mistakes and any defects or errors in manufactured products. These are actually metrics tools that audit source code to ensure compliance with language standards. Some tools that are used for both Quality management plan and to control quality process are Pareto Diagrams, control charts, histograms and scatter diagrams, etc.
  7. Database Management tools : Database management simply means to organize, store, and retrieve data from computer in efficient manner. It provides consistent interfaces for project for all data, in particular, configuration objects are primary repository elements. Some best database management tools are MySQL workbench, SolarWinds Database Performance Analyzer, TablePlus, TeamDesk, etc.
8. What strategies are essential for Success of project management?

Project managers bring projects of all sizes to completion, on time and within budget. There are many reasons a project can derail; however, skilled project managers are able to organize the various elements involved and keep a project on course from start to finish.

By taking necessary precautions and having a detailed plan in place, project managers can ensure success. What can team leaders and project managers do to help keep projects on track when problems arise? The following strategies for successful project management offer both solutions and best practices.

Finalize Project Details

Before you begin a project, make sure that you’ve laid the foundation for success. This means getting buy-in from all stakeholders and understanding the expectations involved. You should clearly define the scope of the project itself, including the various roles and responsibilities of team members. Develop a detailed plan and define goals, then create measurable criteria for success. Factor in deliverable dates and create your timeline. Of course, certain elements will likely change along the way. But if your initial plan has enough detail, your team will be able to adapt.

Set Clear Expectations

Another key part of successful project management is being clear about which team members are responsible for all the components of a project. This makes it easier to create accountability. Once you’ve set expectations, make sure everyone is on the same page and knows when their deliverables are due and how their work contributes to the project as a whole. While it is important for the internal team to be clear on expectations, don’t forget to keep stakeholders informed as well.

Choose the Right Team and System

When your plan is in place and expectations are clear, you will be able to assign tasks to team members. It is the role of a project manager to put together a winning combination of skills, talent and personalities that are right for each particular project. Keep in mind that skill sets should align with specific project requirements. “In order for a project to be successful, you need to have the right project team in place.

Define Milestones

It is important to define key milestones throughout the lifecycle of the project. A good way to get started is by including four main phases: initiation, planning, execution, and closure. Then you can perform an evaluation after each phase and know how your team is doing by examining deliverables. This process keeps you informed about any problems that arise while ensuring that each phase of the project is completed successfully.

Establish Clear Communication

Another element that can make or break a project is communication. You’ll need to create a communication plan featuring how often the team will check in with stakeholders, when status meetings will be held, and more. It is the responsibility of project managers to create status reports, so you should also plan how often you will be sending those out and who needs to receive them.

Manage Project Risks

There are always risks involved in projects. When you are aware of them at the start, however, you can manage them and ensure that potential problems don’t arise. Skilled project managers are able to have contingency plans in place, take preventive action, or even step in with corrective measures.

Avoid Scope Creep

One of the most important roles a project manager plays is keeping a project on track. Although change will always happen, it is important to know how much change can occur before affecting deadlines and deliverables. Scope creep generally takes place when there are additions to a project, which is not revised accordingly.

Evaluate the Project After Completion

Each project provides information that you can utilize in the future. This is why reviewing the project as a whole is such a valuable practice. Note wins as well as areas for improvement, and be sure to consider the planned return on investment in comparison to the actual ROI. When project managers know what went right, what went wrong, and how to make adjustments next time, they are able to develop best practices for future work.

The project management team may select 6 Steps To Ensure Successful Project Completion
  • Step 1: Study the project thoroughly. 
  • Step 2: Prepare a concrete project plan. 
  • Step 3: Daily monitoring of work assigned after project begins. 
  • Step 4: Keep the client informed on a predetermined basis. 
  • Step 5: Perform testing at regular intervals. 
  • Step 6: Final project delivery.
Effective project tracking strategies to keep the project on course and optimize the team's performance and efficiency are:
  • Determine Goals and Milestones. ...
  • Allocate Resources Appropriately. ...
  • Develop a Risk Management Strategy. ...
  • Maintain Effective Communication. ...
  • Monitor Progress. ...
  • Reward Achievements. ...
  • Review and Adjust the Strategy.
The top 5 project management tips for the manager and teams are
  • Foster clear and effective communication.
  • Set clear goals for your project.
  • Choose & use the right tools to monitor progress.
  • Work with a flexible team whose skills combine well.
  • Keep your project team members motivated as best you can.
9. Conclusion

In order to establish the right project management strategy, it’s necessary for the project manager to know the body of knowledge of project management, the value of each piece, its intended use, and how to use it,” Emerson says. 

This knowledge includes 10 key areas, including:

  • Scope: Processes required to ensure all the work—and only the work necessary to complete the project successfully—is included in the project plan
  • Time: Processes required to manage timely completion of the project
  • Cost: Processes involved to plan, manage, and control costs so that the project is within its approved budget
  • Risk: Processes to identify, analyze, plan for, and manage risk on a project
  • Human Resources: Processes that organize, manage, and lead the project team
  • Stakeholder Management: Processes required to identify, analyze, and effectively manage stakeholders and their expectations in project decisions and execution
  • Communications: Processes required to ensure timely and appropriate communication of project information
  • Quality: Processes and activities to ensure the project satisfies the needs for why it was undertaken
  • Procurement: Processes needed to acquire products, services, and results from outside the project team and organization
  • Integration: Processes and activities to coordinate across the nine other knowledge areas
10. FAQs

What Is Cost-Benefit Analysis in Project Management?

A cost-benefit analysis (CBA), sometimes referred to as benefit-cost analysis (BCA), makes it clear what projects or investments are most viable, possible, and beneficial for an organization at any given time. 

In a CBA, costs may include the following: 

  • Direct costs: These are costs that are directly related to the proposed project or investment, e.g., materials, labor, and equipment.
  • Indirect costs: These are related fixed costs that contribute to bringing the project or investment to life, e.g., overhead, administrative, or training expenses.
  • Opportunity costs: These are the benefits or opportunities foregone when a business chooses one project or opportunity over others. To quantify opportunity costs, you must weigh the potential benefits of the available alternatives.
  • Future costs: These are costs that may come up later in the project. These costs depend on certain factors happening, e.g., costs of mitigating potential risks.

Why is conducting a cost-benefit analysis important?

Conducting a project cost-benefit analysis helps to:

  • Identify project costs and benefits: A project cost-benefit analysis ensures all costs and benefits associated with a project are identified and quantified. This reduces cases of hidden expenses and future hurdles or losses, which may only be apparent with a closer look at the project. 
  • Provide a framework for analysis: A CBA provides a structured framework for analyzing the costs and benefits of a potential project. This helps ensure all factors are considered and the most optimal decision is made from a business perspective.
  • Make better-informed decisions: A cost-benefit analysis helps decision-makers determine whether a proposed project or investment is worthwhile. By comparing the costs and benefits of the project, decision-makers make better-informed decisions and allocate organizational resources effectively.
  • Promote transparency: A CBA promotes transparency by making the costs and benefits of any potential project visible and quantifiable. This can help ensure that decision-making is objective and all stakeholders have a clear understanding of the project’s potential impacts.
  • Facilitate communication: A cost-benefit analysis in project management facilitates trust and a foundation for communication between various stakeholders by providing a common language and framework for analyzing a potential project. This helps ensure all parties are on the same page and decisions are made collaboratively and aligned with business goals and objectives.

References 

Aaltonen, K. , & Kujala, J. (2016). Towards an improved understanding of project stakeholder landscapes. International Journal of Project Management, 34, 1537–1552.

Ackerman Anderson, L. , & Anderson, D. (2001). The change leaders roadmap. San Francisco: Pfeiffer.

Adizes, I. (1985). How to solve the mismanagement crisis. Carpinteria, CA: Adizes Institute.

American Society for Quality . (2016). Continuous improvement. Retrieved from http://www.asq.org

Andersen, E. S. (2008). Rethinking project management – An organizational perspective. Harlow, Essex: Prentice Hall.

Andersen, E. S. (2014). Value creation using the mission breakdown structure. International Journal of Project Management, 32, 885–892.

Andersen, E. S. , Grude, K. , & Haug, T. (1995). Goal directed project management. London: Kogan Page.

Argyris, C. (1992). On organizational learning. Oxford: Blackwell.

Artto, K. , Ahola, T. , & Vartiainen, V. (2016). From the front end of projects to the back end of operations: Managing projects for value creation throughout the system lifecycle. International Journal of Project Management, 34, 258–270.

Ashley, D. B. , & Avots, I. (1984). Influence diagramming for analysis of project risks. Project Management Journal, March, 56–62.

Atkinson, R. (1999). Project management: Cost, time and quality, two best guesses and a phenomenon, it’s time to accept other success criteria. International Journal of Project Management, 17, 337–342.

Bech, N. (1990). Competency borders in the project – Peace or quarrels? (in Danish). Symposiet Projektledelse 90.

Beck, K. (2000). Extreme programming explained. Addison-Wesley.

Bejder, E. , & Olsen, W. (2017). Construction engineering – Managing the building process (in Danish). Anlægsteknikforeningen (4th ed.). Lyngby, DK: Polyteknisk Forlag.

Belbin, R. M. (1981). Management teams - Why they succeed or fail. Oxford: Butterworth-Heinemann.

Bennis, W. , Spreitzer, G. M. , & Cummings, T. G. (Eds.), (2001). The future of leadership – Today’s top leadership thinkers speak to tomorrow’s leaders. San Francisco, CA: Jossey-Bass.

Bicheno, J. (2000). The lean toolbox. Buckingham, UK: Piscie Books.

Blake, R. R. , & Mouton, J. (1962). The managerial grid. Austin, TX: Scientific Methods.

Blichfeldt, B. S. , & Eskerod, P. (2008). Project portfolio management – There’s more to it than what management enacts. International Journal of Project Management, 26, 357–365.

Borum, F. (2013). Strategies for organizational change (in Danish). (2nd ed.). Copenhagen: Handelshøjskolens Forlag.

Brandi, S. (2010). The practice of change (in Danish). Copenhagen, DK: L&R Business.

Briner, W. , Hastings, C. , & Geddes, M. (1990). Project leadership. UK: Gower.

Burns, T. , & Stalker, G. M. (1961). The management of innovation. London: Tavistock.

Chapman, C. , & Ward, S. (1997). Project risk management. West Sussex: Wiley.

Charette, R. N. (2003). Challenging the Fundamental Notions of Software Development. Cutter Consortium, Executive report, Vol. 4, No. 6.

Chin, G. (2004). Agile project management. New York, NY: Amacom.

Chittenden, J. , van Bon, J. , & Polter, S. (2006). Programme management: A management guide. NL: van Haren Publishing.

Christensen, S. , & Kreiner, K. (1991). Project management in loosely couple systems (in Danish). Copenhagen, DK: Jurist- og Økonomforbundets Forlag.

Cicmil, C. , Williams, T. , Thomas, J. , & Hodgson, D. (2006). Rethinking project management: Researching the actuality of projects. International Journal of Project Management, 24(8), 675–698.

Cockburn, A. (2005). Crystal clear. Upper Saddle River, NJ: Addison-Wesley.

Cohen, M. D. , & March, J. G. (1974). Leadership and ambiguity. New York, NY: McGraw-Hill.

Crawford, L. , Hobbs, J. B. , & Turner, J. R. (2002). Investigation of potential classification systems for projects. PMI research conference, Seattle, Washington.

Crawford, L. , Morris, P. , Thomas, J. , & Winter, M. (2006). Practitioner development: From trained technicians to reflective practitioners. International Journal of Project Management, 24(8), 722–733.

Cusumano, M. A. , & Selby, R. W. (1996). Microsoft secrets. New York, NY: Harper Collins Publishers.

Cyert, R. M. , & March, J. G. (1963). A behavioral theory of the firm. Upper Saddle River, NJ: Prentice-Hall.

D’Herbemont, O. , & César, B. (1998). Managing sensitive project. New York, NY: Routledge.

Davis, S. M. , & Lawrence, P. R. (1977). Matrix. Indianapolis, IN: Addison-Wesley.

Delp, P. (1977). Systems tools for project planning. New York, NY: International Development Institute.

Dobson, M. S. (2001). Project management for the technical professional. Newtown Square, PA: Project Management Institute.

Drejer, A. , & Riis, J. O. (2000). Competency strategy (in Danish). Copenhagen, DK: Børsens Forlag.

Dreyfus, H. L. , & Dreyfus, S. L. (1986). Mind over machine: The power of human intuition and expertise in the ear of the computer. Oxford: Basil Blackwell Ltd.

Dulewitz, V. , & Higgs, M. J. (2003). Design of a new instrument to assess leadership dimensions and styles. Henley-on-the-Thames: Henley Management College.

Eskerod, P. , & Jepsen, A. L. (2013). Project stakeholder management. Surrey: Gower.

European Commission (1995). Value management handbook. Brussels, Belgium.

Fine, C. (1999). Clockspeed: Winning industry control in the age of temporary advantage. New York, NY: Perseus.

Freeman, R. E. (1984). Strategic Management, A Stakeholder Approach. Pitman Series in Business and Public Policy.

Fritty, P. (2006). Project Management 2.0. PM Network.

Gaber, A. H. , & Krames, J. A. (Eds.) (1996). The Paradox Principles. The Price Waterhouse Change Integration Team. Irwin.

Gareis, R. (1991). Management by projects: the management strategy of the ‘new’ project-oriented company. Project Management, 9(2), 71–76.

Goldratt, E. M. (1997). Critical chain. USA: The North River Press.

Gray, C. F. , & Larson, E. (2003). Project management: The managerial process. New York, NY: McGraw-Hill.

Hauser, J. R. , & Clausing, D. (1988). The house of quality. Harvard Business Review, May.

Hein, L. , & Andreasen, M. M. (1985). Integrated Product Development (in Danish). The Confederation of Danish Industries. An English and later version: Andreasen, M.M. & Hein, L. (2000) Integrated Product Development, IPU, The Technical University of Denmark.

Hersey, P. , Blanchard, K. H. , & Johnson, D. H. (2013). Management of organizational behavior: Leading human resources (10th Ed.). Upper Saddle River, NJ: Pearson.

Highsmith, J. (2004). Agile Project Management – Creating Innovative Products. London: Pearson Education.

Hillson, D. (2002). The risk breakdown structure (RBS) as an aid to effective risk management. Proceedings of the 5th European Project Management Conference (PMI Europe 2002), Cannes, France.

Hofstede, G. (1991). Cultures and organizations. Maidenhead: Mc Graw Hill.

Hornstrup, C. , & Loehr-Petersen, J. (2007). Appreciative inquiry – A constructive method for positive changes (in Danish). Copenhagen, DK: DJØF Forlag.

Imai, M. (1986). Kaizen: The key to Japan’s competitive success. New York, NY: Random House.

Jacobowsky, B. (1991). Project economy in reality (in Swedish). Konsultförlaget AB: Uppsala.

Jensen, A. F. (2012). The project society. Aarhus, DK: Aarhus University Press.

Johansen, J. , & Mitens, L. (1986). Analysis and diagnosis (in Danish). Aalborg, DK: VIPS, Aalborg University, Dept. of Production.

Kelley, R. , & Caplan, J. (1993). How Bell Labs creates star performers. Harvard Business Review, July-August, 128–139.

Killing, P. , & Malnight, T. (2005). Must-win-battles. UK: Prentice Hall.

Kohlbacher, M. (2010). The effects of process orientation: a literature review. Business Process Management Journal, 16(1), 135–152.

Kolb, D. A. (1984). Experiential learning, experience as the source of learning and development. Englewood Cliffs, NJ: Prentice-Hall, Inc.

Kotter, J. P. (2008). A sense of urgency. Boston, MA: Harvard Business Press.

Kotter, J. P. (2012). Leading change. Boston, MA: Harvard Business Review Press.

Kræmmergaard, P. , & Mikkelsen, H. (2007). Complex projects (in Danish). Copenhagen: Børsens Ledelseshåndbøger.

Krebs, J. (2008). Agile portfolio management. Redmond, WA: Microsoft Press.

LaPorte, T. R. (1994). A Strawman speaks up: Comments on the limits of safety. Journal of Contingencies and Crisis Management, 2(4), 207–211.

Larman, C. (2004). Agile & iterative development. Addison-Wesley.

Larsen, J. H. (2002). Teams: Understanding team performance in terms of coordination policy, coordination quality and team roles. Ph.D. Dissertation. Department of Production, Aalborg University.

Larson, S. G. , & Wenell, T. (1985). Dirigibility (in Swedish). Göteborg: C&L Förlag.

Laursen, M. , & Svejvig, P. (2016). Taking stock of project value creation: A structured literature review with future directions for research and practice. International Journal of Project Management, 34, 736–747.

Levine, H. A. (2005). Project portfolio management. UK: John Wiley & Sons Inc.

Levitt, B. , & March, J. G. (1988). Organizational learning. Annual Review of Sociology, 14, 319–340.

Lichtenberg, S. (2000). Proactive Management of uncertainty using the successive principle. Lyngby, DK: Polyteknisk Press.

Lindblom, C. E. (1959). The science of ‘muddling through’. Public Administrative Review, 19(2), 79–88.

Loch, C. , & Kavadias, S. (2011). Implementing strategy through projects. Chapter 9. In P. W. G. Morris , J. K. Pinto , & J. Söderlund (Eds.), The Oxford Handbook of Project Management. Oxford: Oxford University Press.

Madsen, S. , & Pries-Heje, J. (2013). Conceptualizing perceived uncertainty in project work. Chapter 7. In J. Pries-Heje (Ed.), Project Management Multiplicity – Current Trends. Copenhagen: Samfundslitteratur.

Manifesto for Agile Software Development (2001). Retrieved from http://agilemanifesto.org

March, J. G. (1994). A primer on decision making, How decisions happen. New York, NY: The Free Press.

March, J. G. , & Levitt, B. (1988). Organizational learning. Annual Review of Sociology, 14, 319–340.

March, J. G. , & Olsen, J. P. (1986). Garbage can models of decision making in organizations. In J. G. March & R. Weissinger-Baylon (Eds.), Ambiguity and command (pp. 11–36). Cambridge, MA: Ballinger.

Mascitelli, R. (2002). Building a project-driven enterprise. California: Technology Perspectives.

Maylor, H. , Brady, T. , Cooke-Davies, T. , & Hodgson, D. (2006). From projectification to programmification. International Journal of Project Management, 24(8), 663–674.

MBTI Basics (2014). Myers & Briggs Foundation. Retrieved from http://www.myersbriggs.org

Mikkelsen, H. (Ed.), (1982). Organizing export projects. Foreningen Projektplan. Teknisk Forlag.

Mikkelsen, H. (2005). Management of the Myriad of Projects (in Danish). Børsen Publishing. An English synthesis in Mikkelsen, H. & Riis, J.O. (2013). Projects and Company Development – Effectiveness and Productivity. Chapter 4 in Project Management Multiplicity – Current Trends, edited by Jan Pries-Heje. Samfundslitteratur, Copenhagen.

Mikkelsen, H. , Olsen, W. , & Riis, J. O. (1991). Management of internal projects. International Journal of Project Management, 9(2), 77–81.

Mikkelsen, H. , & Riis, J. O. (1981). Foundations of project management (in Danish). (1st Ed.). Rungsted Kyst, DK: Promet.

Mikkelsen, H. , & Riis, J. O. (2006). Agile company development (in Danish). Aalborg, DK: Center for Industrial Production. Aalborg University.

Mikkelsen, H. , & Riis, J. O. (2013). 40 years of Danish project management: From engineering manager to business developer. Chapter 2 In J. Pries-Heje (Ed.), Project Management Multiplicity – Current trends (pp. 21–38). Copenhagen: Samfundslitteratur.

Mintzberg, H. (1973). The nature of managerial work. New York, NY: Harper & Row.

Mintzberg, H. , Ahlstrand, B. , & Lampel, J. (1998). Strategy Safari, A guided tour through the wilds of strategic management. New York, NY: Prentice Hall and The Free Press.

Morgan, G. (1986). Images of organization. London: Sage Publications.

Morgan, J. , & Liker, J. K. (2006). The Toyota product development system. New York, NY: Productivity Press.

Morris, P. W. G. (2013). Reconstructing project management. Chichester, West Sussex: Wiley-Blackwell.

Morsing, M. , & Nickelsen, N. C. (1999). Migration of knowledge (in Danish). Copenhagen, DK: CO-Industri & Dansk Industri.

Morton, C. H. A. (1983). Become a project champion. International Journal of Project Management, 1(4), November.

Müller, R. , & Turner, R. (2010). Leadership competency profiles of successful project managers. International Journal of Project Management, 28(5), 437–448.

Nonaka, I. , & Takeuchi, H. (1995). The knowledge creating company – How Japanese Companies create the Dynamics of Innovation. New York: Oxford University Press.

Osterwalder, A. , Pigneur, Y. , Bernarda, G. , & Smith, A. (2014). Value proposition design. Hoboken, NJ: Wiley.

Padalkar, M. , & Gopinath, S. (2016). Six decades of project management research: Thematic trends and future opportunities. International Journal of Project Management, 34, 1305–1321.

Pinto, J. K. (2016). Project management – Achieving competitive advantage. (4th Ed.). Harlow, Essex: Pearson Education Limited.

PMBOK (Project Management Body of Knowledge), 5th ed. (2017). Retrieved from http://www.pmi.org

Poppendieck, M. , & Poppendieck, T. (2006). Implementing lean software development. Boston, MA: Addison-Wesley and Pearson Education.

Rentzhog, O. (2000). Process orientation – A foundation for modern management (in Danish). Copenhagen: Akademisk Forlag.

Riis, J. O. (2004). Key competencies and conditions for learning in the knowledge society’s companies (in Danish). Copenhagen, DK: Danmarks ErhvervsrÃ¥d.

Riis, J. O. (2008). Gaming in production management. In L. de Caluwé , G. J. Hofstede , & V. Peters (Eds.), Why do games work? (pp. 133–141). Deventer, NL: Kluwer.

Riis, J. O. (2009). Models for company development – A participatory approach taking manufacturing as point of departure. Aalborg, DK: Center for Industrial Production, Aalborg University.

Riis, J. O. , Hildebrandt, S. , Andreasen, M. M. , & Johansen, J. (1997). Renewal in companies (in Danish). Børsen, Copenhagen.

Riis, J. O. , & Johansen, J. (2003). Developing a Manufacturing Vision. Production Planning & Control, 14(4), 327–337.

Riis, J. O. , & Mikkelsen, H. (1997). Capturing the nature of a project in the initial phase: Early identification of focal areas. Project Management, 3(1), 18–22.

Riis, J. O. , Smeds, R. , & Van Landeghem, R. (Eds.) (2000). Games in operations management. Dordrecht, NL: Kluwer Academic Publishers.

Schwaber, K. , & Sutherland, J. (2016). The Scrum Guide. Retrieved from http://www.scrumguides.org

Senge, P. (1990). The Fifth Discipline – The art and practice of the learning organization. UK: Century Business.

Serrador, P. , & Pinto, J. K. (2015). Does Agile Work? – A quantitative analysis of agile project success. International Journal of Project Management, 33, 1040–1051.

Smith, P. G. , & Reinertsen, D. G. (1998). Developing products in half the time. New York, NY: John Wiley.

Söderlund, J. (2011). Theoretical foundations of project management – Suggestions for a pluralistic understanding. Chapter 2 In P. W. G. Morris , J. K. Pinto , & J. Söderlund (Eds.), The Oxford Handbook of Project Management (pp. 37–64). Oxford: Oxford University Press.

Stettina, C. J. , & Hörz, J. (2015). Agile portfolio management: An empirical perspective on the practice in use. International Journal of Project Management, 33, 140–152.

Sullivan, J. , & Beach, R. (2009). Improving project outcomes through operational reliability. A conceptual model. International Journal of Project Management, 27(8), 765–775.

Svejvig, P. , & Andersen, P. (2015). Rethinking project management: A structured literature review with a critical look at the brave new world. International Journal of Project Management, 33(2), 278–290.

The Danish Project Management Association . (2008). Competencies in project management - National competence baseline for Scandinavia. Version 3.0. The Danish Project Management Association.

Thiry, M. (2004). Value management. Chapter 36 In P. W. G. Morris & J. K. Pinto (Eds.), The Wiley guide to managing projects. Hoboken, NJ: Wiley.

Toor, S. , & Ogunlana, S. O. (2010). Beyond the “Iron Triangle”: Stakeholder perception of key performance indicators (KPIs) for large-scale public sector development project. International Journal of Project Management, 28(3), 228–236.

Tuckman, B. W. , & Jensen, M. A. C. (1977). Stages of small group development revisited. Group and Organizational Studies, 2, 419–427.

Turner, J. R. , & Müller, R. (2003). On the nature of the project as a temporary organization. International Journal of Project Management, 21, 1–8.

Vagnby, B. (1999). Manual for logical framework approach: A participatory planning tool. Aalborg, DK: Institut for Samfundsudvikling og Planlægning, Aalborg University.

Weick, K. E. (2001). Leadership as the Legitimation of Doubt. Chapter 8 In W. Bennis , G. M. Spreitzer , & T. G. Cummings (Eds.), The future of leadership. San Francisco, CA: Jossey-Bass.

Wenger, E. (1998). Communities of practice, learning, meaning, and identity. Cambridge: Cambridge University Press.

Wheelwright, S. , & Clark, K. B. (1992). Revolutionizing product development. New York, NY: The Free Press.

Wilemon, D. L. , & Thamhain, H. J. (1979). Team Building in Project Management. Proceedings, PMI Symposium, Atlanta.

Winter, M. , Andersen, E. S. , Elvin, R. , & Levene, R. (2006). Focusing on business projects as an area for future research: An exploratory discussion of four different perspectives. International Journal of Project Management, 24, 699–709.

Winter, M. , Smith, C. , Morris, P. , & Cicmil, S. (2006). Directions for future research in project management: the main findings of a UK government-funded research network. International Journal of Project Management, 24(8), 638–649.

Winter, M. , & Szczepanek, T. (2008). Projects and programmes as value creation processes: A new perspective and some practical implications. International Journal of Project Management, 26, 95–103.

Womack, L. , & Jones, D. (1996). Lean thinking. New York, NY: Simon and Schuster.

Youker, R. (1977). Organizational Alternatives for Project Management. Project Management Quarterly, VIII(1), (March).

Comments