project assignment meaning

What Is Project Management? Definitions, Examples & More

Updated: May 29, 2024, 3:58pm

The goal of project management is to help a team achieve a goal or solve a problem with a set deadline. The project manager owns responsibility for the team hitting its deadline and meeting the goal. But what is project management exactly, and how does it work? Here’s a primer on everything you need to know to get your projects on track.

Featured Partners

From $8 monthly per user

Zoom, LinkedIn, Adobe, Salesforce and more

On monday.com's Website

Yes, for unlimited members

$7 per month

Slack, Microsoft Outlook, HubSpot, Salesforce, Timely, Google Drive and more

On ClickUp's Website

$9.80 per user per month

Salesforce, Adobe, Miro, Netsuite, Quickbooks, SAP

On Wrike's Website

Yes, for one user and two editors

$9 per user per month

Google Drive, Slack, Tableau, Miro, Zapier and more

On Smartsheet's Website

Related: Best Project Management Software

What Is Project Management?

Project management uses processes, skills, tools and knowledge to complete a planned project and achieve its goals. It differs from general management because of the limited scope of a project, concrete deadlines and specific deliverables.

A project exists temporarily and must balance the involved team members’ time and usually the organization’s limited financial resources—a daunting task but one that can be accomplished in a few deliberate steps that utilize special methods and tools.

Steps of Project Management

Project management begins when a manager or team initiates a project. The five phases of project management include:

• The initiation phase. The project manager will assign—or ask for team members to volunteer—to complete specific tasks.
• The planning phase. The team agrees on a schedule with the client or among themselves for the project. The team may also create a communication schedule with key stakeholders, determine the project’s standards and set a budget during this phase.
• The execution phase. This phase is where the work gets done. Employees may work independently or as a team on tasks that were determined during the previous phases.
• The monitoring phase. The project manager monitors each person or team’s progress along the way to ensure the project is on track to meet the overall deadline and achieve its goals. This phase often happens simultaneous to the execution phase.
• The closing phase. Finally, the project manager ensures the team completed the project to the agreed-upon standards and communicates that the team completed the project.

Project Management Tools and Techniques

Even though every project has its own goals and challenges, team members can utilize similar project management tools and techniques to complete their various deliverables.

For example, a deliberate communication plan can serve as one of the most valuable tools in a project manager’s toolkit. A strong project manager communicates with all stakeholders and facilitates strong communication among team members working on the project.

And during the monitoring and execution phase, well-organized project managers may also rely on software to keep themselves and their team on track.

One software program won’t meet all your needs for every project but programs like Trello , Asana or Airtable will help your team members track their and each other’s progress. The software also makes it clear who owns responsibility for which task.

In addition, project managers may use traditional tools such as the Program Evaluation Review Technique (PERT) and Gantt charts to guide their teams’ work. PERT helps define the project’s scope and helps monitor the tasks that the team needs to complete. Gantt charts show the timeline and calendar view of when assignments are due. Many project management software applications now do this digitally.

Frequently Asked Questions (FAQs)

What are the different types of project management methods, and which one is right for me.

There are dozens of project management types , and they all have different benefits and limitations that make them good for some environments, and bad for others.

What are the best project management tools and software?

To determine the best project management software , we ranked several tools based on ease of use, cost to your organization, each company’s customer support, as well as special features.

Wrike was our top choice. It earned the top spot because it works for companies and teams of all sizes. Airbnb, Google and Dell all trust Wrike to aid their project managers. Wrike also allows teams to create custom workflows, set timelines with interactive charts and reporting and build a visual representation that shows the progress of every project in real-time.

Other highly ranked project management tools include Asana, Monday and HighGear.

Who are project managers, and what do they do?

For the best chance at success, every project needs an owner who is responsible for its completion and success. Project managers exist to fill this need, keep a team on task and ensure the project meets the needs of all stakeholders. This designation could be a subset of responsibilities—or an official job title.

A diverse range of industries requires the skills of a talented project manager. You can be a project manager in construction, publishing, finance, professional services, utilities and many other industries. Despite the final result of the projects looking very different across these industries, the steps and skills to keep a team organized fluently translate across the business world.

Why is project management important?

Project management is important in business because it helps you complete projects successfully and hit goals for yourself and your clients.

Coordinating a multifaceted project for which several people owe deliverables, keeping everyone organized and ensuring the output meets expectations—all this while under the stress of a deadline—presents a challenge for even the most experienced project manager.

These challenges become more feasible through project management best practices.

• Best Project Management Software
• Best Construction Project Management Software
• Best Project Portfolio Management Software
• Best Gantt Chart Software
• Best Task Management Software
• Best Free Project Management Software
• Best Enterprise Project Management Software
• Best Kanban Software
• Best Scrum Software
• Asana Review
• Trello Review
• monday.com Review
• Smartsheet Review
• Wrike Review
• Todoist Review
• Basecamp Review
• Confluence Review
• Airtable Review
• ClickUp Review
• Monday vs. Asana
• Clickup vs. Asana
• Asana vs. Trello
• Asana vs. Jira
• Trello vs. Jira
• Monday vs. Trello
• Clickup vs. Trello
• Asana vs. Wrike
• Project Management Methodologies
• 10 Essential Project Management Skills
• SMART Goals: Ultimate Guide
• What is a Gantt Chart?
• What is a Kanban Board?
• What is a RACI Chart?
• What is Gap Analysis?
• Work Breakdown Structure Guide
• Agile vs. Waterfall Methodology
• What is a Stakeholder Analysis
• What Is An OKR?

What Is SNMP? Simple Network Management Protocol Explained

What Is A Single-Member LLC? Definition, Pros And Cons

What Is Penetration Testing? Definition & Best Practices

What Is Network Access Control (NAC)?

What Is Network Segmentation?

How To Start A Business In Louisiana (2024 Guide)

Meredith Galante is a full-time freelance writer living in New York City. She's been covering small businesses, the wine and spirits industry, and more for the last 10 years. Meredith graduated from the SI Newhouse School of Public Communications at Syracuse University with a degree in magazine journalism and political science.

Adam Hardy is a former assistant editor at Forbes Advisor, where he covered small business and tech. Previously, he was a staff writer at The Penny Hoarder, specializing in the gig economy and entrepreneurship. His work has appeared in the Asia Times, Business Insider, Creative Loafing, the Tampa Bay Times, Yahoo! Finance and other publications.

• Atlassian Guard
• Jira Service Management
• Atlassian Engineering
• Continuous Delivery
• IT Service Management
• Inside Atlassian
• Project Management
• Work Management
• Company News

How to write an effective project plan in 6 simple steps

Contributing writer

If you’re a Type A personality, project planning might sound like music to your ears. Setting deadlines, organizing tasks, and creating order out of chaos — what’s not to love?

The reality is that project planning isn’t for everyone. In one survey by Association for Project Management, 76% of project professionals said their main project was a source of stress . Poor planning, unclear responsibilities, and overallocation are often the culprits behind the stress. 

An effective project plan helps teams stay within budget, scope, and schedule, while delivering quality work. In short, it gets you to the finish line without the stress.  

What is a project plan?

A project plan, also known as a work plan, is a blueprint of your project lifecycle. It’s like a roadmap — it clearly outlines how to get from where you are now (the beginning of the project) to where you want to go (the successful completion of the project). 

“A project plan is an action plan outlining how…[to] accomplish project goals,” says Jami Yazdani , certified Project Management Professional (PMP), project coach, project management consultant, and founder of Yazdani Consulting and Facilitation . 

A comprehensive project plan includes the project schedule, project scope, due dates, and deliverables. Writing a good project plan is key for any new, complex project in the pipeline.

Why Are Project Plans Important?

Project plans allow you to visualize your entire project, from beginning to end—and develop a clear strategy to get from point A to point B. Project plans steer stakeholders in the right direction and keep team members accountable with a common baseline.  

Project plans help you stay agile

Projects are bound by what is traditionally called the “iron triangle” of project management . It means that project managers have to work within the three constraints of scope, resources (project budget and teams), and schedule. You cannot make changes to one without impacting the other two.    

Modern-day project management has shifted to a more agile approach, with a focus on quality. This means that resources and schedules remain unchanged but a fixed number of iterations (flexible scope) helps teams deliver better quality and more value. 

A project plan puts this “agile triangle” in place by mapping out resources, schedules, and the number of iterations — sprints if you’re using a Scrum framework and work in progress (WIP) limits if you’re using the Kanban methodology . 

As Yazdani points out, “Project plans help us strategize a path to project success, allowing us to consider the factors that will impact our project, from stakeholders to budget to schedule delays, and plan how to maximize or mitigate these factors.” 

Project plans provide complete visibility

A project plan, when created with a comprehensive project management software , gives you 360-degree visibility throughout the project lifecycle. 

As a project manager, you need a single source of truth on team members and their project tasks, project scope, project objectives, and project timelines. A detailed project plan gives you this visibility and helps teams stay on track.

Project plans also help to get everyone involved on the same page, setting clear expectations around what needs to be accomplished, when, and by who. 

“Project plans create a framework for measuring project progress and success,” says Yazdani. “Project plans set clear expectations for…stakeholders by outlining exactly what…will [be accomplished] and when it will be delivered.”

Project plans boost engagement and productivity

A well-written project plan clarifies how each individual team member’s contributions play into the larger scope of the project and align with company goals. When employees see how their work directly impacts organizational growth, it generates buy-in and drives engagement , which is critical to a project’s success. 

“Project plans provide…teams with purpose and direction,” says Yazdani. “Transparent project plans show team members how their individual tasks and responsibilities contribute to the overall success of the project, encouraging engagement and collaboration.”

How To Write A Project Plan in 6 Steps

Writing a project plan requires, well, planning. Ideally, the seeds for a project plan need to be sowed before internal project sign-off begins. Before that sign-off, conduct capacity planning to estimate the resources you will need and if they’re available for the duration of the project. After all, you want to set your teams up for success with realistic end dates, buffer time to recharge or catch up in case of unexpected delays, and deliver quality work without experiencing burnout .

Based on organizational capacity, you can lay down project timelines and map out scope as well as success metrics, outline tasks, and build a feedback loop into your project plan. Follow these project planning steps to create a winning plan:      

1. Establish Project Scope And Metrics

Defining your project scope is essential to protecting your iron, or agile, triangle from crumbling. Too often, projects are hit with scope creep , causing delays, budget overruns, and anxiety.

“Clearly define your project’s scope or overall purpose,” says Yazdani. “Confirm any project parameters or constraints, like budget, resource availability, and timeline,” says Yazdani.

A project purpose statement is a high-level brief that defines the what, who, and why of the project along with how and when the goal will be accomplished. But just as important as defining your project scope and purpose is defining what metrics you’re going to use to track progress.

“Establish how you will measure success,” says Yazdani. “Are there metrics, performance criteria, or quality standards you need to meet?”

Clearly defining what your project is, the project’s overall purpose, and how you’re going to measure success lays the foundation for the rest of your project plan—so make sure you take the time to define each of these elements from the get-go.

2. Identify Key Project Stakeholders 

Get clarity on the team members you need to bring the project to life. In other words, identify the key stakeholders of the project. 

“List individuals or groups who will be impacted by the project,” says Yazdani. 

In addition to identifying who needs to be involved in the project, think about how they’ll need to be involved—and at what level. Use a tool like Confluence to run a virtual session to clarify roles and responsibilities, and find gaps that need to be filled. 

Let’s say you’re managing a cross-functional project to launch a new marketing campaign that includes team members from your marketing, design, and sales departments. 

When identifying your key stakeholders, you might create different lists based on the responsibility or level of involvement with the project:

• Decision-makers (who will need to provide input at each step of the project)
• Managers (who will be overseeing employees within their department) 
• Creative talent (who will be actually creating the project deliverables for the campaign) from each department. 

Give your project plan an edge by using a Confluence template like the one below to outline roles and responsibilities.

Define roles, discuss responsibilities, and clarify which tasks fall under each teammate’s purview using this Confluence template. 

Getting clarity on who needs to be involved in the project—and how they’re going to be involved—will help guide the rest of the project plan writing process (particularly when it comes to creating and assigning tasks).

3. Outline Deliverables

Now is the time to get granular.

Each project milestone comprises a series of smaller, tangible tasks that your teams need to produce. While a big-picture view keeps teams aligned, you need signposts along the way to guide them on a day-to-day or weekly basis. Create a list of deliverables that will help you achieve the greater vision of the project. 

“What will you create, build, design, produce, accomplish or deliver?” says Yazdani. “Clearly outline your project’s concrete and tangible deliverables or outcomes.” Centralize these deliverables in a Trello board with designated cards for each one, like in the example below, so you keep work moving forward.

Each card on a board represents tasks and ideas and you can move cards across lists to show progress.

Defining the concrete items you need your project to deliver will help you reverse-engineer the things that need to happen to bring those items to life—which is a must before moving on to the next step.

4. Develop Actionable Tasks

Task management is an important component of any project plan because they help employees see what exactly they need to accomplish. Drill down those deliverables into actionable tasks to assign to your team. 

You can use either Confluence or Jira for different task management needs. If you want to track tasks alongside your work, like action items from a meeting or small team projects, it’s best to use Confluence. But if a project has multiple teams and you need insight into workflows, task history, and reporting, Jira makes it easy.      

“Let your deliverables guide the work of the project,” says Yazdani. “Break down each deliverable into smaller and smaller components until you get to an actionable task.” If a major deliverable is a set of content pieces, the smaller actionable tasks would be to create topic ideas, conduct research, and create outlines for each topic.  

Once you’ve broken down all of your deliverables into manageable, assignable subtasks, analyze how each of those tasks interacts with each other. That way, you can plan, prioritize, assign, and add deadlines accordingly.  

“Highlight any dependencies between tasks, such as tasks that can’t be started until another task is complete,” says Yazdani. “List any resources you will need to accomplish these tasks.”

When a task has multiple assignees, you need to streamline the workflow in your project plan. Say the content pieces you outlined need to be edited or peer-reviewed. A couple of articles may need an interview with a subject matter expert. Lay down a stage-by-stage process of each piece of content and pinpoint when each team member comes into play so you prevent bottlenecks and adjust timeframes.     

5. Assign Tasks And Deadlines

Assign tasks to your team and collaborate with employees to set deadlines for each task. When you involve employees in setting workloads and deadlines , you increase ownership and boost the chances of delivering quality work on time.  

After all, you want to move projects forward at a steady pace, but you also want to make sure your teams stay motivated and engaged. So, when writing your project plan, make sure to “set realistic and achievable deadlines for completing tasks and deliverables,” says Yazdani. “Highlight dates that are inflexible and factor in task dependencies. Add in milestones or checkpoints to monitor progress and celebrate successes .”

Use Jira and Confluence to create tasks that live alongside your project plan or meeting agendas.

Once you map out all of your tasks and deadlines, you should have a clear picture of how and when your project is going to come together—and the initial writing process is just about finished.

But that doesn’t mean your project plan is complete! There’s one more key step to the process.

6. Share, Gather Feedback, And Adjust The Project Plan As Necessary

While steps 1 through 5 may make up your initial writing process, if you want your project plan to be as strong and complete as it can be, it’s important to share it with your team—and get their input on how they think it can be improved.

“Share the plan with your project team and key stakeholders, gathering feedback to make adjustments and improvements,” says Yazdani. 

A tool like Confluence helps knowledge flow freely within teams and departments, leading to better teamwork, higher collaboration, and a shared understanding of priorities. Coworkers can use comments, mentions, notifications, and co-editing capabilities to provide and discuss feedback. 

After you gather your team’s feedback —and make any necessary adjustments based on that feedback—you can consider your project plan complete. Hooray! 

But as your project progresses, things may change or evolve—so it’s important to stay flexible and make changes and adjustments as needed.

“Expect to update your plan as you gather more information, encounter changing requirements and delays, and learn from feedback and mistakes,” says Yazdani. “By using your project plan to guide your activities and measure progress, you’ll be able to refine and improve your plan as you move through the project, tweaking tasks and deadlines as deliverables are developed.”

Download a  template to create your project plan and customize it based on your needs.

Example of a simple project plan 

A project plan doesn’t have to be a complicated spreadsheet with multiple tabs and drop-down menus. It’s best to use a project planning tool like Confluence — or at least a project plan template — to make sure you cover every aspect of the project. A simple project plan includes these elements:

• Project name, brief summary, and objective.
• Project players or team members who will drive the project, along with their roles and responsibilities.
• Key outcomes and due dates.
• Project elements, ideally divided into must-have, nice-to-have and not-in-scope categories.
• Milestones, milestone owners, and a project end date.
• Reference material relevant to the project.

Best Practices For Writing Effective Project Plans

A project planning process can quickly turn into a mishmash of goals and tasks that end up in chaos but these best practices can give you a framework to create a project plan that leads to success.

Use Other Project Plans For Inspiration

There’s no need to reinvent the wheel for every new project! Instead, look to other successful project plans for inspiration—and use them as a guide when writing the plan for your project.

“Review templates and plans for similar projects, or for other projects within your organization or industry, to get ideas for structuring and drafting your own plan,” says Yazdani.

To get started, use a Trello project management template and customize it for your project plan by creating unique lists and adding cards under each list.

Build your team’s ideal workflow and mark each stage of the project plan as a list, with cards for each task. 

Get Your Team Involved In The Process

You may be in charge of spearheading the project. But that doesn’t mean that you have to—or even that you should—write the project plan alone. 

“Collaborate with your project team and key stakeholders on crafting a project plan,” says Yazdani. “Input into the project plan supports buy-in to project goals and encourages continued engagement throughout the project.”

With Confluence , you can organize project details in a centralized space and build a project plan collaboratively.

Don’t Let Perfect Be The Enemy Of The Good

You may be tempted to write (and rewrite) your project plan until you’ve got every detail mapped out perfectly. But spending too much time trying to get everything “perfect” can actually hold up the project. So don’t let perfect be the enemy of the good—and instead of getting caught up in getting everything perfect from the get-go, stay willing and flexible to adjust your project plan as you move forward.

“Focus on outcomes, not plan perfection,” says Yazdani. “While it would be awesome for the first draft of our plan to require no changes while also inspiring our team and ensuring project success, our goal shouldn’t be a perfect plan. Our goal is a plan that allows us to successfully deliver on project goals. Responsiveness to changing needs and a shifting environment is more important than plan perfection.”

Use the right tools to succeed with your project plan

Writing a project plan, especially if you’re new to the process, can feel overwhelming. But now that you know the exact steps to write one, make sure you have the tools you need to create a strong, cohesive plan from the ground up—and watch your project thrive as a result. 

Atlassian Together can help with project planning and management with a powerful combination of tools that make work flow across teams.

Guide your team to project success with Atlassian Together’s suite of products.

Advice, stories, and expertise about work life today.

• Contact sales
• Start free trial

Project Planning: How to Make a Project Plan

This guide is brought to you by projectmanager, the project planning software trusted by 35,000+ users worldwide. make a project plan in minutes.

What Is a Project Plan?

How to create a project plan, project planning phase, what is project planning software, benefits of online project planning software, must-have project planning software features, project planning terms, project planning steps, how to create a project plan with projectmanager, what is the purpose of a project management plan, the elements of a project plan, how long does the project planning phase take, techniques for the project planning process, how to manage your project plan.

A project plan is a series of formal documents that define the execution and control stages of a project. The plan includes considerations for risk management, resource management and communications, while also addressing scope, cost and schedule baselines. Project planning software is used by project managers to ensure that their plans are thorough and robust.

ProjectManager allows you to make detailed project plans with online Gantt charts that have task dependencies, resource hours, labor costs, milestones, the critical path and more. Plus, your team can execute the plan in any of our five project views, while you track progress along the way with dashboards. Start today for free.

The project plan, also called project management plan, answers the who, what, where, why, how and when of the project—it’s more than a Gantt chart with tasks and due dates. The purpose of a project plan is to guide the execution and control project phases.

As mentioned above, a project plan consists of the following documents:

• Project Charter : Provides a general overview of the project. It describes the project’s reasons, goals, objectives, constraints, stakeholders, among other aspects.
• Statement of Work : A statement of work (SOW) defines the project’s scope, schedule, deliverables, milestones, and tasks.
• Work Breakdown Structure : Breaks down the project scope into the project phases, subprojects, deliverables, and work packages that lead to your final deliverable.
• Project Plan : The project plan document is divided in sections to cover the following: scope management, quality management, risk assessment, resource management, stakeholder management, schedule management and the change management plan.

This guide aims to give you all the information and resources you need to create a project plan and get it approved by your customers and stakeholders. Let’s start with the basics of writing a project plan.

Get your free

Project Plan Template

Use this free Project Plan Template for Word to manage your projects better.

Your project plan is essential to the success of any project. Without one, your project may be susceptible to common project management issues such as missed deadlines, scope creep and cost overrun. While writing a project plan is somewhat labor intensive up front, the effort will pay dividends throughout the project life cycle.

The basic outline of any project plan can be summarized in these five steps:

• Define your project’s stakeholders, scope, quality baseline, deliverables, milestones, success criteria and requirements. Create a project charter, work breakdown structure (WBS) and a statement of work (SOW) .
• Identify risks and assign deliverables to your team members, who will perform the tasks required and monitor the risks associated with them.
• Organize your project team (customers, stakeholders, teams, ad hoc members, and so on), and define their roles and responsibilities.
• List the necessary project resources , such as personnel, equipment, salaries, and materials, then estimate their cost.
• Develop change management procedures and forms.
• Create a communication plan , schedule, budget and other guiding documents for the project.

Each of the steps to write a project plan explained above correspond to the 5 project phases, which we will outline in the next section.

What Are the 5 Phases of the Project Life Cycle?

Any project , whether big or small, has the potential to be very complex. It’s much easier to break down all the necessary inclusions for a project plan by viewing your project in terms of phases. The Project Management Institute , within the Project Management Book of Knowledge (PMBOK), have identified the following 5 phases of a project:

• Initiation: The start of a project, in which goals and objectives are defined through a business case and the practicality of the project is determined by a feasibility study.
• Planning: During the project planning phase, the scope of the project is defined by a work breakdown structure (WBS) and the project methodology to manage the project is decided on. Costs, quality and resources are estimated, and a project schedule with milestones and task dependencies is identified. The main deliverable of this phase is your project plan.
• Execution: The project deliverables are completed during this phase. Usually, this phase begins with a kick-off meeting and is followed by regular team meetings and status reports while the project is being worked on.
• Monitoring & Controlling: This phase is performed in tandem with the project execution phase. Progress and performance metrics are measured to keep progress on the project aligned with the project plan.
• Closure: The project is completed when the stakeholder receives the final deliverable. Resources are released, contracts are signed off on and, ideally, there will be an evaluation of the successes and failures.

Free Project Plan Template

Address all aspects of your project plan with this free project plan template for Word . This in-depth template will guide you through every phase of the project, as well as all the elements you need to outline for a proper document. Download your template today.

We’ve created also created other project planning templates to help you create all the different documents that make up a project plan, like the project schedule, project budget or resource plan.

Now that we’ve learned how to make a project plan, and identified the stages of the project management life cycle, we need to emphasize on the importance of the project planning phase.

The project planning process is critical for any kind of project because this is where you create all the documents that will guide how you’ll execute your project plan and how you’ll control risks and any issues that might occur. These documents, which are part of the project management plan, cover all the details of your project without exception.

There are project plan templates out there that can help you organize your tasks and begin the project planning process—but we here at ProjectManager recommend the use of project planning software. The feature set is far more robust and integrated with every project phase compared to an Excel project plan template, and is a great way to ensure your actual progress stays aligned with your planned progress.

Once you write a project plan, it’s time for implementation . Watch the video below to see how project planning software helps organize a project’s tasks, resources and costs.

Project planning tools has become an invaluable tool for project managers in recent years, as it provides them the ability to maintain and automate the components we outlined above. Project planning software is a great tool to facilitate project management processes such as schedule development, team management, cost estimation, resource allocation and risk monitoring.

Beyond that, planning software also allows managers to monitor and track their plan as it moves through the execution phase of the project. These features include dashboards, for a high-level view of the project’s progress and performance, and in-depth reports that can be used to communicate with stakeholders.

Project planning software comes in all different sizes and shapes. There are some that focus on a single aspect, and others that offer a suite of planning features that can be used in each one of the project planning steps. What’s right for your project depends on your specific needs, but in general terms, project planning software is a much more powerful tool than project planning templates .

Related: 20 Must-Have Project Management Excel Templates

Online project planning software is highly flexible and adaptable to your team’s style of work. It has features that are designed to assist you throughout your project planning process.

Before the rise of planning software, project managers would typically have to keep up with a disjointed collection of documents, excel spreadsheets and so on. Savvy managers, however, make use of the project management tools available to them to automate what they can, and streamline what they can’t.

Some of the time-saving benefits of project planning software include the following.

• Organize, prioritize and assign tasks
• Plan and schedule milestones and task dependencies
• Monitor progress, costs and resources
• Collaborate with team
• Share project plans with team and stakeholders
• Generate reports on plans

Gantt Charts for Superior Planning

A Gantt chart is the most essential tool for the project planning process. Organize tasks, add their duration and they automatically populate a project timeline . Set milestones to break the larger project into manageable phases, and link task dependencies to avoid bottlenecks later in the project.

Get More Than a To-Do List

When planning a project, you need more than a to-do list. Seek out a planning software with a task list feature that lets you set priority levels, filters and collaborate. It’s a big plus if you can also make personal task lists that are private to manage your own work.

Use Kanban for Workflows

Workflows ensure proper execution of your plan, and no feature does this better than kanban boards. Customize boards to match your workflow and drag and drop cards as teams get their work done. See what work needs to be done and keep the focus on productivity with this feature.

Be Able to Track Progress

A dashboard can keep your project plan on track. Try and find a dashboard that’s synced with your planning tools, so everything updates automatically. It will make reporting easier too.

Get Transparency Into Teams

For a plan to go smoothly, you have to know what your team is working on. Find a way to balance your team’s availability with the project schedule. Workload features that map out resource allocation and holidays can be a big help here.

Be Able to Manage Multiple Projects

Rarely do you need to only focus on one project at a time. Give yourself the flexibility to manage multiple projects at once in the same tool. A roadmap feature that maps all of your projects on one timeline can be a lifesaver.

Before we dive into how to create a project plan, it helps to be familiar with some of the terms that you’ll run across. Here is a list of general terms you’ll encounter in this guide.

• Deliverable: The results of a project, such as a product, service, report, etc.
• Stakeholder: Anyone with a vested interest in the project—project manager, project sponsor, team members, customers, etc.
• Tasks: Small jobs that lead to the final deliverable.
• Milestone: The end of one project phase, and the beginning of the next.
• Resources: Anything you need to complete the project, such as personnel, supplies, materials, tools, people and more.
• Budget: Estimate of total cost related to completing a project.
• Tracking & Monitoring: Collecting project data, and making sure it reflects the results you planned for.

The project planning process is critical for the success of your project, and as a project manager, you have to think about all the elements that make up your project management plan such as work, time, resources and risks.

Now, we’re going to take you through the main project planning steps :

• Outline the business case
• Meet with key stakeholders
• Define project scope
• Assemble a project team
• Determine a project budget
• Set project goals & objectives
• Outline project deliverables
• Create a project schedule
• Assign tasks to your team members
• Do a risk analysis
• Create your project plan
• Report your progress

By following these project planning steps, you’ll clarify what you need to achieve, work out the processes you need to get there and develop an action plan for how you are going to take this project plan outline forward.

1. Outline the Business Case

If you have a project, there’s a reason for it—that’s your business case . The business case outlines reasons why the project is being initiated, its benefits and the return on investment. If there’s a problem that is being solved, then that problem is outlined here. The business case will be presented to those who make decisions at your organization, explaining what has to be done, and how, along with a feasibility study to assess the practicality of the project. If approved, you have a project.

2. Meet with Key Stakeholders

Every project has stakeholders , those who have a vested interest in the project. From the ones who profit from it, to the project team members who are responsible for its success. Therefore, any project manager must identify who these key stakeholders are during the project planning process, from customers to regulators. Meeting with them is crucial to get a better picture of what the project management plan should include and what is expected from the final deliverable.

3. Define Project Scope

It refers to the work required to accomplish the project objectives and generate the required deliverables. The project scope should be defined and organized by a work breakdown structure (WBS). Therefore, the project scope includes what you must do in the project (deliverables, sub deliverables, work packages, action items ), but also what is nonessential. The latter is important for the project plan, because knowing what isn’t high priority helps to avoid scope creep ; that is, using valuable resources for something that isn’t key to your project’s success.

4. Assemble a Project Team

You’ll need a capable project team to help you create your project plan and execute it successfully. It’s advisable to gather a diverse group of experienced professionals to build a multi-disciplinary team that sees your project management plan from different perspectives.

5. Determine a Project Budget

Once you define your project scope, you’ll have a task list that must be completed to deliver your project successfully. To do so, you’ll need resources such as equipment, materials, human capital, and of course, money. Your project budget will pay for all this. The first step to create a project budget is to estimate the costs associated with each task. Once you have those estimated costs, you can establish a cost baseline , which is the base for your project budget.

6. Set Project Goals & Objectives

Goals and objectives are different things when it comes to planning a project. Goals are the results you want to achieve, and are usually broad. Objectives , on the other hand, are more specific; measurable actions that must be taken to reach your goal. When creating a project plan, the goals and objectives naturally spring from the business case, but in this stage, you go into further detail. In a sense, you’re fine-tuning the goals set forth in the business case and creating tasks that are clearly defined. These goals and objectives are collected in a project charter , which you’ll use throughout the project life cycle.

7. Outline Project Deliverables

A project can have numerous deliverables. A deliverable can be a good, service or result that is needed to complete a task, process, phase, subproject or project. For example, the final deliverable is the reason for the project, and once this deliverable is produced, the project is completed. As defined in the project scope, a project consists of subprojects, phases, work packages, activities and tasks, and each of these components can have a deliverable. The first thing to do is determine what the final deliverable is, and how you will know that the quality meets your stakeholder’s expectations. As for the other deliverables in the project, they must also be identified and someone on the team must be accountable for their successful completion.

8. Create a Project Schedule

The project schedule is what everything hangs on. From your tasks to your budget , it’s all defined by time. Schedules are made up by collecting all the tasks needed to reach your final deliverable, and setting them on a project timeline that ends at your deadline. This can make for an unruly job ahead, which is why schedules are broken into phases, indicated by milestones , which mark the end of one project phase and the beginning of the next.

9. Assign Tasks to Your Team Members

The plan is set, but it still exists in the abstract until you take the tasks on your schedule and begin assigning them out to your team members. Their roles and responsibilities must be clearly defined, so they know what to do. Then, when you assign them tasks from your plan, they should be clear, with directions and any related documentation they will need to execute the tasks.

10. Do a Risk Analysis

Every project has some level of risk . There are several types of risk such as scope risk, technical risks and schedule risk, among others. Even if your project plan is thorough, internal and external factors can impact your project’s time, cost and scope (triple constraint). Therefore, you need to regard your planning as flexible. There are many ways to prepare for risk, such as developing a change management plan, but for now, the most important thing to do is to track your progress throughout the execution phase by using project status reports and/or project planning software to monitor risk.

11. Create your Project Plan

As discussed above, a project management plan is a document that’s made of several elements. Before we get into a detailed explanation of each of them, it’s important to understand that you should include them all to have a solid project plan. The components that you’ll need might vary depending on your project, but in general terms, you’ll need these main documents to create your project management plan:

• Project charter
• Project schedule
• Project budget
• Project scope statement
• Risk management plan
• Change management plan
• Cost management plan
• Resource management plan
• Stakeholder management plan

12. Report Your Progress

Your ultimate goal is to ensure a successful project for your stakeholders. They’re invested, and will not be satisfied twiddling their thumbs without looking at project status reports to track progress. By constructing a work breakdown structure (WBS) during the project planning phase you can break down the project for them so that they understand how your project plan will be executed. Keeping stakeholders informed is important to manage their expectations and ensure that they’re satisfied. Having regular planning meetings where you present progress reports are a great way to show them that everything is moving forward as planned and to field any questions or concerns they might have. Your stakeholder management plan will specify how you’ll engage stakeholders in the project.

Project planning software is a tool that helps to plan, organize and manage the schedule and resources needed to complete a project. ProjectManager is an award-winning project management software that organizes projects from planning to completion. Sign up for a free 30-day trial and follow along to build a thorough project plan that covers every detail.

1. List Your Tasks for the Plan

Tasks are the building blocks of any project and the start of any plan is identifying all the tasks that lead to your final deliverable.

Open the tool to add your tasks on the Gantt chart or one of the other multiple project views. You can import a task list from any spreadsheet or use one of our templates to get started.

2. Add Duration and Costs to Tasks

Every task has an estimated duration, which is the time it will take to complete it. They will also require a certain amount of funding, which needs to be collected to formulate your plan.

Add the start and end dates for each task in the Gantt and they populate a project timeline, so you can see the whole project laid out in one place. There’s also a column for task costs.

3. Link Dependent Tasks

Tasks are not always separate from one another. Often one cannot start or stop until another has started or stopped. That’s called a task dependency and needs to be noted in your plan.

Link dependent tasks by dragging one to the other. A dotted line indicates that they’re linked, so you stay aware of the fact and can avoid bottlenecks later in the project.

4. Set Milestones & Baseline

A milestone indicates the end of one phase and the beginning of another, which helps with tracking and morale. The baseline sets your plan so you can compare it to actual progress.

There is a filter on the Gantt that automatically sets the baseline, so you can use it to track your actual progress against the plan. The baseline can also be locked with a click.

5. Onboard Team & Assign

Getting the team and the tool together is how a project plan becomes actualized. The easier and seamless this transition, the faster you’ll get to work on the project.

Invite your team from the software and it generates an email with a link. Once they follow that link, they’re in and have access to the tools they need to manage their tasks.

6. Monitor Progress & Report to Stakeholders

Keeping track of your progress and then updating stakeholders is both how you stay on track and manage your stakeholders’ expectations.

See progress as it happens on our real-time dashboard, which calculates data and displays it over six project metrics. Reports can be filtered and shared for a deep dive into those numbers.

7. Adjust Plan As Needed

No plan remains the same throughout a project. Things happen and changes are demanded. Therefore, being able to edit your plan easily is key to the project planning process.

Edit your plan on the Gantt by a simple drag and drop. Move the old date to the new date and not only is that task fixed, but any impacted tasks are also updated automatically.

ProjectManager is an award-winning software that helps managers plan and helps teams get organized. Gantt charts control all aspects of your project plan from scheduling to assigning tasks and even monitoring progress. Multiple project views provide transparency into workflow and give everyone the tools they need to be at their best.

Ready to make your plan? Try ProjectManager today with this free 30-day trial.

The project manager is responsible for producing the project plan, and while you can’t make up all the content yourself, you’ll be the one banging the keys to type it all out. Use templates where you can to save time. Download our free project plan template and write your plan in double-quick time!

The purpose of a project management plan is to serve as a guide for the execution and control phases. The project plan provides all the information necessary for the execution phase such as the project’s goals, objectives, scope of work, milestones, risks and resources. Then, this information helps project managers monitor and control the progress of the project.

We plan at the beginning to save time later. A good project plan means that you don’t have to worry about whether the project participants are going to be available on the right dates—because you’ve planned for them to be. You don’t have to worry about how to pay those invoices—you’ve planned your financial process. You don’t have to worry about whether everyone agrees on what a quality outcome looks like—you’ve already planned what quality measures you are going to use.

A good project plan sets out the processes that everyone is expected to follow, so it avoids a lot of headaches later. For example, if you specify that estimates are going to be worked out by subject matter experts based on their judgement, and that’s approved, later no one can complain that they wanted you to use a different estimating technique. They’ve known the deal since the start.

Project plans are also really helpful for monitoring progress. You can go back to them and check what you said you were going to do and how, comparing it to what you are actually doing. This gives you a good reality check and enables you to change course if you need to, bringing the project back on track.

Tools like dashboards can help you make sure that your project is proceeding according to plan. ProjectManager has a real-time dashboard that updates automatically whenever tasks are updated.

The project planning process already discussed only scratches the surface of what is a deep well of practices created to control your project. They start with dialogue — speaking to stakeholders, teams, et al.

The deliverable for your planning phase is a document called the project plan. A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition says that the project plan is made up of lots of subsidiary plans. These include:

• A project scope statement to define all the tasks and deliverables that are needed to complete the project
• A risk management plan for dealing with project risk including the processes for logging and tracking risks
• A change management plan to manage any changes that will be made to the project plan
• A cost management plan for managing costs and the budgeting elements of the project including any procurements or supplier engagements you might have
• A resource management plan for managing the material resources such as equipment and the human resources on the team both in terms of availability and skills
• A stakeholder management plan setting out who is going to receive messages about the project, when and in what format
• A quality plan that specifies the quality targets for the project

That’s a lot of documentation.

In reality, it’s rare that you’ll produce these as individual documents. What you need is a project plan that talks about the important elements of each of these. There’s no point creating a big document that sets out exactly how your business works anyway. If you already have a structured risk management process , then don’t waste time writing it all down again in your project plan.

Your project management plan needs to include enough information to make sure that you know exactly what processes and procedures need to be followed and who needs to be involved. Get your project plan approved by your stakeholders, your project sponsor and your team so there are no surprises later. As explained above, project planning charts and techniques such as Gantt charts, CPM, WBS or PERT can help you create your project plan.

This is hard to answer. It’s going to take longer to plan the moon landing than a new dating app.

The best way to estimate how long your project planning phase will take is to look at similar projects that have happened before, and see how long it took them to plan. Talk to the project manager as well, if you can, because they’ll have a view on whether that length of time was enough or not!

It’s easy to see how long other projects took if you have a project management tool that archives your old project schedules and makes the data available to everyone who needs it. You can then search for similar projects and study their schedules in detail.

A project plan is all about working out what to do and how to do it, so you need to get a lot of people involved. There are several good tools and project planning techniques for getting information from other people including:

• One-to-one meetings or interviews
• Surveys or customer focus groups to gather and validate requirements.

You should also arm yourself with a task management tool , like a list or a kanban board. They are incredibly useful for noting down important things that should be in your project plan. Kanban board software can help structure your plan by writing down the key headings and then moving them around as required until you have a flow that looks right.

Finally, you’ll need an online project management system to store your project management plan in. Make sure that everyone in the team can access the latest version of the project plan.

Your project plan is not a document written in stone. You should be referring back to it and making changes to it as often as you need to. Parts of it, like your project schedule, will change almost daily. Other parts, like your procurement plans and cost management processes, won’t change at all during the life of your project.

The important thing to remember is that if your project management plan isn’t working for you, think about what you can do to change it. It’s there to guide your project management, not restrict you from doing the right thing. If you need to review how you manage work and project resources, then go back and review it. Make the changes you need, get the plan approved again and share it with the team.

How To Make a Project Plan When You Don’t Have All the Answers

Yes, this happens–most of the time! It’s rare to have all the information at the beginning of a project. Most managers want you to dive in and get started, but you might not have the luxury of knowing all the details.

That’s OK; we have techniques to help deal with uncertainty.

First is the project assumption. You use these to put caveats on your plan and to document the things that you assume to be true at this point in time. For example:

• We assume that the resources will be available.
• We assume that the required funding is available.
• We assume that the colors requested will be in line with the company brand and that Marketing sign off is not required.

You get the picture. Then, if the design team comes back and says that they want the product to be a totally new palette of colors and that Marketing has to approve that, you are justified in saying that you’ll have to change the timescales on the schedule to make that possible.

You planned based on an assumption (that everyone agreed to, because you got the document approved) and that assumption turned out not to be true.

Next Steps for Project Planning

The most important thing to remember is that you shouldn’t rush the project planning process. Done properly, project planning takes time. And it’s worth doing it properly because if you don’t, we guarantee that you will hit problems later on as people won’t understand what they are supposed to do and why.

Great planning sets you up for success. It gives you the confidence of knowing that you’ve got all your processes, tools and systems in place to deliver the perfect result.

Now that you’ve learned all about project planning, it’s time to take action. Sign up for a free 30-day trial of ProjectManager and start planning your project today!

Start My Free Trial

Project Planning Resources

• Best Project Planner Tools: Apps, Software & Templates
• Best Project Planning Software of 2024 (Free & Paid)
• 25 of the Best Planning Quotes
• 3 Best Planner Apps for Mac in 2024
• 3 Best Project Management Charts for Project Planning
• Project Management Trends
• How to Create a Project Roadmap (Example Included)
• What Is Aggregate Planning? Strategies & Tips
• What Is Rolling Wave Planning?
• How to Create a Project Execution Plan (PEP) – Free Template Included
• Sample Project Plan For Your Next Project
• Operational Planning: How to Make an Operations Plan
• Project Planning Software
• Gantt Chart Software
• Project Scheduling Software
• Work Breakdown Structure Software
• Project Timeline Software
• Resource Planning Software
• Free Project Planning Templates
• Free Project Management Templates
• Project Proposal Template
• Project Charter Template
• Project Timeline Template
• Implementation Plan Template
• Work Plan Template
• Action Plan Template

Start your free 30-day trial

Deliver faster, collaborate better, innovate more effectively — without the high prices and months-long implementation and extensive training required by other products.

We use essential cookies to make Venngage work. By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.

Manage Cookies

Cookies and similar technologies collect certain information about how you’re using our website. Some of them are essential, and without them you wouldn’t be able to use Venngage. But others are optional, and you get to choose whether we use them or not.

Strictly Necessary Cookies

These cookies are always on, as they’re essential for making Venngage work, and making it safe. Without these cookies, services you’ve asked for can’t be provided.

Show cookie providers

• Google Login

Functionality Cookies

These cookies help us provide enhanced functionality and personalisation, and remember your settings. They may be set by us or by third party providers.

Performance Cookies

These cookies help us analyze how many people are using Venngage, where they come from and how they're using it. If you opt out of these cookies, we can’t get feedback to make Venngage better for you and all our users.

• Google Analytics

Targeting Cookies

These cookies are set by our advertising partners to track your activity and show you relevant Venngage ads on other sites as you browse the internet.

• Google Tag Manager
• Infographics
• Daily Infographics
• Popular Templates
• Accessibility
• Graphic Design
• Graphs and Charts
• Data Visualization
• Human Resources
• Beginner Guides

Blog Marketing What is a Project Management Plan and How to Create One

What is a Project Management Plan and How to Create One

Written by: Midori Nediger Dec 11, 2023

Have you ever been part of a project that didn’t go as planned?

It doesn’t feel good.

Wasted time, wasted resources. It’s pretty frustrating for everyone involved.

That’s why it’s so important to create a comprehensive project management plan   before your project gets off the ground.

In this guide, we’ll explore how to create and design a successful project management plan.

We’ll also showcase easy-to-customize project plan templates you can create today with our user-friendly drag-and-drop editor. Let’s get started!

  Click to jump ahead:

What is a project management plan?

How do you write a project management plan, project management plan templates and examples, what is the importance of a project management plan, what should a project management plan include, 5 key tips for creating a project management plan, project management plan best practices, common mistakes to avoid when creating a project management plan.

A project management plan is a formal document that defines how a project is going to be carried out by outlining the scope, goals, budget, timeline and deliverables of a project. Its crucial role lies in ensuring the project stays on course.

You write a project plan  during the project planning stage of the  project life cycle , and it must be approved by stakeholders before a project can move on the execution stage.

If some of these terms are new to you, you can get up to speed with this post on project management terms . 

This means your project plan must be engaging, organized, and thorough enough to gain the support of your stakeholders.

Further Reading : New to project management? Read our blog post on the 4 stages of the project life cycle .

To write a successful project management plan, follow these 5 steps below to create an effective plan that serves as a valuable tool for project management:

1. Highlight the key elements of your project plan in an executive summary  

An executive summary is a brief description of the key contents of a project management plan .

I t’s usually the first thing stakeholders will read, and it should act like a Cliff’s-notes version of the whole plan.

It might touch on a project’s value proposition, goals, deliverables, and important milestones, but it has to be concise (it is a summary, after all). First, make sure you develop a proof of concept .

In this example, an executive summary can be broken into columns to contrast the existing problem with the project solution:

The two-column format with clear headers helps break up the information, making it extremely easy to read at a glance.

Here’s another example of a project management plan executive summary. This one visually highlights key takeaways with big fonts and helpful icons:

In this case, the highlighted facts and figures are particularly easy to scan (which is sure to make your stakeholders happy).

But your executive summary won’t always be so simple.

For larger projects, your executive summary will be longer and more detailed.

This project management plan template has a text-heavy executive summary, though the bold headers and different background colors keep it from looking overwhelming:

It’s also a good idea to divide it up into sections, with a dedicated header for each section:

Regardless of how you organize your executive summary, it should give your stakeholders a preview of what’s to come in the rest of the project management plan.

2. Plot your project schedule visually with a Gantt chart

A carefully planned project schedule is key to the success of any project. Without one, your project will likely crumble into a mess of missed deadlines, poor team management, and scope creep.

Luckily, project planning tools like Gantt charts and project timelines make creating your project schedule easy. You can visually plot each project task, add major milestones, then look for any dependencies or conflicts that you haven’t accounted for.

For example, this Gantt chart template outlines high-level project activities over the course of an entire quarter, with tasks color-coded by team:

A high-level roadmap like the one above is probably sufficient for your project management plan. Every team will be able to refer back to this timeline throughout the project to make sure they’re on track.

But before project kickoff , you’ll need to dig in and break down project responsibilities by individual team member, like in this Gantt chart example:

In the later execution and monitoring phases of the project, you’ll thank yourself for creating a detailed visual roadmap that you can track and adjust as things change.

You can also use a project management tool to keep your team organized.

Further Reading:   Our post featuring  Gantt chart examples  and more tips on how to use them for project management.

3. Clarify the structure of your project team with a team org chart

One of the hardest aspects of project planning is assembling a team and aligning them to the project vision.

And aligning your team is all about communication–communicating the project goals, communicating stakeholder requests, communicating the rationale behind big decisions…the list goes on.

This is where good project documentation is crucial! You need to create documents that your team and your stakeholders can access when they have questions or need guidance.

One easy thing to document visually is the structure of your team, with an organizational chart like this one:

In an organizational chart you should include some basic information like team hierarchy and team member contact information. That way your stakeholders have all of the information they need at their fingertips.

But in addition to that, you can indicate the high-level responsibilities of each team member and the channels of communication within the team (so your team knows exactly what they’re accountable for).

Here’s another simple organizational structure template that you can use as a starting point:

Create an organizational chart with our organizational chart maker .

4. Organize project risk factors in a risk breakdown structure

A big part of project planning is identifying the factors that are likely to derail your project, and coming up with plans and process to deal with those factors. This is generally referred to as risk management .

The first step in coming up with a risk management plan is to list all of the factors at play, which is where a risk breakdown structure comes in handy. A risk breakdown structure is a hierarchical representation of project risks, organized by category.

This risk breakdown structure template, for example, shows project risk broken down into technical risk, management risk, and external risk:

Once you’ve constructed your risk breakdown structure, you’ll be ready to do a deep dive into each risk (to assess and plan for any triggers and outcomes).

Streamline your workflow with business process management software .

5. Plan ahead: create project status reports to communicate progress to stakeholders

As I mentioned earlier, communication is fundamental in any project.

But even so, something that’s often overlooked by project managers is a communication management plan–a plan for how the project team is going to communicate with project stakeholders . Too often, project communication defaults to ad-hoc emails or last-minute meetings.

You can avoid this by planning ahead. Start with a project kickoff meeting and include a project status report template as part of your communication plan.

Here’s an example of a simple project status report that you might send to stakeholders on a weekly basis:

This type of report is invaluable for communicating updates on project progress. It shows what you’ve accomplished in a clear, consistent format, which can help flag issues before they arise, build trust with your stakeholders , and makes it easy to reflect on project performance once you’ve reached your goals.

You might also want to include a broader status report for bigger updates on a monthly or quarterly basis, like this one:

The above template allows you to inform stakeholders of more major updates like new budget requirements, revised completion dates, and project performance ratings.

You can even include visualization of up-to-date project milestones, like this example below:

Want more tips on creating visuals to enhance your communications? Read our visual communication guide for businesses . 

A project management plan is probably the most important deliverable your stakeholders will receive from you (besides the project itself).

It holds all of the information that stakeholders will use to determine whether your project moves forward or gets kicked to the curb.

That’s why it’s a good idea to start with a project management plan template. Using a template can help you organize your information logically and ensure it’s engaging enough to hold your stakeholders’ attention.

Construction project management plan template

Time is money, especially with construction projects. Having a construction plan template brings order to the chaos.

Instead of staring at a messy pile of construction stuff, you’ve got a plan that breaks everything down into bite-sized pieces.

And let’s not forget the paperwork. Construction projects have rules and regulations to follow. Your project plan helps you stay on the right side of the law with all the necessary documentation and compliance measures.

Start with a meticulous project overview, like in the second page of this template:

Though you may think this project will be similar to others you’ve done in the past, it’s important to nail the details.

This will also help you understand the scope of work so you can estimate costs properly and arrive at a quote that’s neither too high or low. Ontario Construction News has great advice on this process.

Simple project management plan template

This simple project management plan template that clearly lays out all of the information your stakeholders will need:

Simple project management communication plan template

A key part of project management is making sure everyone’s in the loop. A project communication plan ensures everyone knows how, where, who and when the team will communicate during the course of the project. Also construction scheduling is a critical aspect of the project management plan as it helps to ensure that all necessary tasks are completed within the allocated time frame and budget.

The key is to figure out what kind of communications is valuable to stakeholders and what is simply overwhelming and won’t lead to better decisions.

This template clearly outlines all of these factors to help manage expectations and eliminate confusion about what will get communicated and when:

Commercial development project plan template

The below project management plan template is simple and minimal, but still uses a unique layout and simple visuals to create an easy-to-read, scannable project overview.

This template is perfect for building or construction management , or any technical projects:

When picking a project plan template, look for one that’s flexible enough to accommodate any changes your stakeholders might request before they’ll approve the project. You never know what might change in the early planning stages of the project! You can also use  project management tools  to help you with your planning!

A well-developed project management plan sets the foundation for a successful project by providing a roadmap that guides the project team toward successful project completion. A good project management plan can ensure that:

• Project objectives and goals are clearly defined and understood
• Project scope is effectively managed
• Resources are allocated efficiently to maximize productivity and minimize waste
• Risks are identified, assessed and mitigated
• Project tasks and activities are well-organized and executed in a timely manner.
• Communication among team members , stakeholders and project sponsors is effective and transparent
• Changes to the project are properly evaluated, approved and implemented
• Lessons learned and best practices are documented for future reference and improvement
• Stakeholders are engaged and satisfied with the project outcomes
• The project is delivered within the specified timeline, budget and quality standards

Before you start assembling your own plan, you should be familiar with the main components of a typical project plan .

A project management plan should include the following sections:

• Executive summary: A short description of the contents of the report
• Project scope & deliverables: An outline of the boundaries of the project, and a description of how the project will be broken down into measurable deliverables
• Project schedule: A high-level view of project tasks and milestones ( Gantt charts are handy for this)
• Project resources: The budget, personnel, and other resources required to meet project goals
• Risk and issue management plan: A list of factors that could derail the project and a plan for how issues will be identified, addressed, and controlled
• Communication management plan: A plan for how team and stakeholder communication will be handled over the course of the project
• Cost and quality management plan: This section encompasses the project’s budget, cost estimation, and cost control mechanisms. It also includes quality assurance testing and control measures as well as any testing or verification activities to be performed.

Basically, a project plan should tell stakeholders what needs to get done, how it will get done, and when it will get done.

That said, one size doesn’t fit all. Every project management plan must be tailored to the specific industry and circumstances of the project. You can use a project management app for smoother project planning.

For example, this marketing plan looks client facing. It is tailored to sell the client on the agency:

Whereas this commercial development plan focuses on specific objectives and a detailed timeline:

With those basics out of the way, let’s get into how to write a project management plan that’s as engaging as it is professional.

Further Reading : If you’re looking to create a proposal, read our in-depth business proposal guide. Then try our job proposal templates or business proposal templates .  

Before diving into creating a project management plan, it is crucial to have a clear understanding of the project objectives and the expectations of stakeholders involved.

Without a firm grasp of these fundamental elements, your project may face significant challenges or fail to deliver the desired outcomes.

Here are key points to consider when creating a project management plan:

• Project Objectives: Clearly understand the project objectives and what you want to achieve. Identify the desired outcomes, deliverables and the purpose of the project.
• Scope of the Project: Determine the boundaries and extent of the project. Define what is included and excluded to ensure clarity and prevent scope creep .
• Stakeholders: Identify all stakeholders who will be impacted by or have an interest in the project. Understand their needs, expectations and level of involvement.
• Resources: Assess the resources required to execute the project successfully. This includes human resources, budget, equipment and materials. Determine their availability and allocation.
• Risks and Constraints: Identify potential risks, uncertainties and constraints that may affect the project. Understand the challenges, limitations and potential obstacles that need to be addressed.

Now that you have these key areas identified, let’s get started with creating your project plan.

Before you dive in, remember: a clear and adaptable plan is crucial for project success. Here are some best practices to keep your project plan on track:

• Use headers, columns and highlights to make your executive summary easy to read
• Plot your project schedule with a Gantt chart (with tasks color-coded by department or team member)
• Use visuals like organizational charts and risk breakdown structures to communicate across your team and with stakeholders
• Pick a flexible template that you can update to align with stakeholder requests

Creating a solid project management plan is crucial for setting your project up for success. Here are some common mistakes to avoid:

• Lack of clear goals: Don’t just have a vague idea of what you want to achieve. Define clear, SMART goals (Specific, Measurable, Achievable, Relevant and Time-bound) for your project. That way, everyone will be on the same page and it’ll be easier to measure progress effectively.
• Unrealistic timelines: Be optimistic, but also realistic. Don’t underestimate the time required for tasks. Factor in potential delays and buffer time when creating your project schedule.
• Scope creep: New requirements mid-project can affect deadlines and budgets. Plan the project clearly upfront, and take into consideration any changes that might come up.
• Poor communication: Communication is key throughout the project lifecycle. Regularly update stakeholders, team members and clients on progress, roadblocks and changes.
• Ignoring risks: Things don’t always go according to plan. Identify potential risks upfront and have a mitigation strategy in place for each one.
• Not involving stakeholders: Get key stakeholders involved early on. This helps manage everyone’s expectations and that you have the buy-in you need for success.
• Neglecting resource constraints: Don’t overload your team or underestimate the resources needed. Carefully consider the skills, time and budget available when planning your project.
• Micromanaging: Trust your team! Delegate tasks effectively and give them the autonomy they need to do their jobs.
• Failing to document: Keep good records. Document project decisions, plans and communication. This helps maintain transparency and ensures everyone has access to the latest information.
• Not adapting to change: Be prepared to adapt your plan as needed. Projects are rarely static, so be flexible and willing to adjust your approach based on new information or developments.

So, that’s the scoop on project management plans! I hope this piece will help you to avoid confusion, keep expectations in check and be ready to tackle any bumps for your upcoming projects.

If you ever need a revision, just follow the steps we talked about, use those best practices and you’ll have a plan that sets your project up for a win. Just remember, even the best plans need some tweaking sometimes. Be flexible and adjust as needed and you’re good to go!

Discover popular designs

Infographic maker

Brochure maker

White paper online

Newsletter creator

Flyer maker

Timeline maker

Letterhead maker

Mind map maker

Ebook maker

Get started

• Project management
• CRM and Sales
• Work management
• Product development life cycle
• Comparisons
• Construction management
• monday.com updates

What is a task? and how to get more of them done

While the word “task” might bring about feelings of despair related to chores or undesirable actions, this is usually related more so to the way you have to manage your time than the task itself.

In this article, we’ll do a deep dive into tasks, show you the best ways to break down larger projects into them, while covering efficient approaches to manage and distribute tasks.

Try monday.com

What is a task in a project?

In project management, a task is a work item or activity with a specific purpose related to the larger goal. It’s a necessary step on the road towards project completion.

For example, it could be something as complex as a mobile app bug fix.

Or it could be something as simple as photocopying the latest brochure for distribution.

Single tasks are typically assigned to a single person or team, while the larger project could be a company-wide endeavor.

The task may or may not include a start and end date or a series of subtasks—this all depends on the complexity of the project at hand, which could be related to industry.

How do you break down a project into smaller tasks?

Even long term Scrum projects that last  11.6 weeks on average make use of task management to get their work done efficiently and effectively.

Part of task management includes creating manageable workloads, considering task dependencies, and of course, communicating across teams to avoid double work or roadblocks.

To avoid these issues, you need some way to break down the high-level project deliverables and goals into tangible tasks.

In the next section, we’ll show you two of the most popular methodologies, Waterfall, and Scrum.

Work Breakdown Structure

The work breakdown structure (WBS) is the official method of breaking down projects in the PMI Guidebook.

To figure out how to break the entire project into tasks, you first need to divide it into the actual deliverables required to hand over the final product or result to the client.

For example, if you’re planning to make a mountain bike, you can break that down into the frame, handlebars, pedals, wheels, chains, and so on.

( Image Source )

You also need to work out the dependencies of the project (aka which deliverables require another one for completion).

If we were to simplify the WBS, the section on manufacturing the bike frame might look something like this.

Of course, each item contains multiple tasks such as sourcing vendors, reviewing designs, picking materials, and more.

But if you assign these tasks to teams who have the necessary skills to complete all of them, that’s what the top-level plan might look like.

If you use an Agile framework, like Scrum, you won’t bother breaking down the entire project into detailed tasks at an early stage. Avoiding this large-scale exercise in prediction is one of the primary principles of Agile.

Instead, you’ll focus on planning out a deliverable increment of your product in Scrum sprints . These are 2–4 week periods of focused work dedicated to delivering a working product version of the final deliverable.

The basis for planning out these iterations is a backlog of features or user stories (functionality from the user’s perspective). You may also have a product roadmap to outline the long-term product direction as well.

The product backlog is continually pruned and optimized before, during, and after sprints. Even if you’re not planning software projects, you can often single out elements that you can deliver in increments.

Before each Sprint, you meet with your team and stakeholders (invested parties) to discuss which user stories are the most important. You select a few items and create a dedicated sprint backlog .

Each user story is then further divided into tasks, and team members take ownership of the specific tasks they can handle.

It’s not ideal for all organizations or projects, but it’s an antidote against micromanagement in complex projects.

What size should a project task be?

So how granular should you get? What should the scope and length of the task in your project be?

It depends on the size of your project and your PM framework, but here are some rules of thumb.

The 8/80 rule for WBS

In traditional project management , a rule of thumb is that no task should be shorter than 8 hours or longer than 80 hours in the WBS.

That’s why the PMI recommends keeping tasks between 20–80 hours in the WBS.

Your individual teams can then have more granular task boards to manage their own to-do lists and/or break 2-week tasks down into daily sub-tasks.

Task length in Scrum

While user stories generally have no specified length, they’re often broken down into manageable chunks, usually one workday or less.

The official Scrum Guide doesn’t use the word tasks, but instead uses the term work unit:

“ Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less. ”

On a Scrum board , you can use story points (at monday.com, we equate 1 SP to a workday) to estimate the length of the task.

Tasks shouldn’t require more than one resource

When you break down deliverables into individual tasks, time isn’t the only consideration. The best approach is to make sure the person (or resource) who’s assigned the task can complete it from start to finish.

For example, a graphic designer could create a wireframe for an app, but wouldn’t be able to create a working prototype.

So you should split the larger deliverable of a working feature prototype into wireframe/design and development (at the very least).

For larger companies, a resource could be an entire team that includes designers, developers, and software testers. In which case, you don’t have to get as granular when planning and assigning tasks.

Accurately estimating task durations

The best way to predict the duration of tasks is to involve the actual resources who will handle the task in the planning process.

You don’t need to switch to Agile or Scrum to make this happen. You just need to involve the actual project implementers in the planning process, not just management.

Not only can they help with task durations, but they can also help with dependencies and expecting potential bottlenecks.

What is the best way to organize project tasks?

There are hundreds of different frameworks and methods for managing projects and breaking them down into tasks.

A few stand out because of their efficiency and ease of adoption and have become popular as a result.

Let’s take a closer look at these industry-leading options.

Waterfall refers to the traditional “predictive” project management approach. It’s called predictive because you plan every phase of the project from start to finish before even getting started.

The reason it’s called waterfall is that the projects are planned to follow a sequential order.

First, you start out by figuring out the requirements of the project. What deliverables do you need to deliver a finished product?

Then you move on to designing and creating (implementing) it. Finally, you verify that the product works as intended, and launch it. The last stage includes the long-term maintenance of the product.

While berating waterfall is a popular pastime among younger management professionals, it has its place.

For physical products with a lot of dependencies and high costs associated with actual production time, mapping out the entire project in detail can be the best approach.

Instead of a specific methodology, Agile outlines a core set of values and principles to apply to your projects. As a result, Agile is an umbrella term that covers many different methodologies and frameworks .

The most famous principle is to deliver working iterations of your project frequently. That’s in contrast to planning out an entire product from start to finish like with waterfall.

Lean, like Agile, is not a specific framework that details a project management approach. Instead, it refers to a management philosophy with a core set of principles.

The focus of Lean is eliminating waste in processes throughout each stage of production. The execution is what controls the outcome, after all.

Fixing bottlenecks between departments to speed up the final assembly is a good example.

Not to be confused with Agile, which is more about high-level concepts and principles, Scrum is an actual framework for project management.

It outlines clear rules, meetings (ceremonies), and deliverables (artifacts), not just values.

For example, Scrum teams should only include a maximum of 9 regular team members. Daily Scrum meetings should only last 15 minutes.

The entire process of designing and completing a sprint is laid out in detail. That’s what makes the Scrum framework so useful for teams that want to implement more Agile principles into practice.

How to use a project management platform for effective task management

Instead of slowing down your managers and teams with an inefficient process, take advantage of the latest task management software .

monday.com is a digital workspace with all the functionality a project manager could ever want, wrapped in a package that’s actually easy to learn and use.

Pick the framework or methodology you want to work with

If you want to reach a completely new target level of productivity, basic task management won’t cut it. You need to introduce a project management framework that goes beyond daily tasks.

Luckily, monday.com makes it easy to make the switch. We offer dedicated templates for everything from WBS to Scrum.

Develop the high-level project roadmap

For consistent results, you should develop a high-level project roadmap. It will help guide all decisions and priorities as the project progresses.

Get more granular with a WBS and other task boards

This is where you break the larger goals into smaller deliverables and start to establish the workload for each team or department that’s involved.

It should outline the overall process but may not specify every activity or task, depending on the scale of the project.

But it’s not the best for planning individual tasks within the involved teams or departments.

Which is why monday.com also offers more basic task boards that these teams can use to manage the day-to-day.

You can easily divide larger items into smaller subtasks and assign them as well.

Use integrations and automations to automate menial tasks

If you want to perfect your workflow , it’s not enough to create some new task boards. You also need to eliminate repetitive menial tasks.

For example, with our smart integrations, you can automatically update a card or create a new task when you receive an email or message.

It’s a useful feature for a wide variety of teams and use-cases. For example, your software team could get a new task with every bug report.

By automating menial tasks, you give your managers and team the time and space to focus on crucial high-level decisions.

Keep managers up to speed with dashboards and reports

Want to see at a glance if tasks are being completed on schedule, or which people (or teams) are available for last-minute work?

You can easily create and customize a dashboard that will give your managers instant access to all the information they need.

Master your tasks

Breaking down a project into tasks and assigning them effectively requires a bit of balance.

Finding the framework that works best for your industry and internal workflows and pairing them with the tips above can help you find the happy medium of management and autonomy that will allow your teams to thrive.

Whichever you choose, monday.com has the right templates and tools to help your projects succeed.

• Share on Twitter
• Share on LinkedIn
• Share on Facebook
• Share on Pinterest
• Share through Email

6 Steps To Create A Project Charter (+ Examples & A Template)

Sarah is a project manager and strategy consultant with 15 years of experience leading cross-functional teams to execute complex multi-million dollar projects. She excels at diagnosing, prioritizing, and solving organizational challenges and cultivating strong relationships to improve how teams do business. Sarah is passionate about productivity, leadership, building community, and her home state of New Jersey.

Expert Evidence

Galen is a digital project manager with over 10 years of experience shaping and delivering human-centered digital transformation initiatives in government, healthcare, transit, and retail. He is a digital project management nerd, a cultivator of highly collaborative teams, and an impulsive sharer of knowledge. He's also the co-founder of The Digital Project Manager and host of The DPM Podcast.

Project charters are important documents that describe the scope and objectives of a project. Find out how to get our template to speed up the process of creating one, and get the deets on what to include and best practices from the experts.

Project Can't Start Without A Charter: Projects can't officially start without a charter, and skipping this step leads to misalignment and an increased risk of project failure.

Charters Secure Alignment & Buy-In: A project charter outlines the scope and business case, so all stakeholders are aligned on project purpose and deliverables before the project actually kicks off.

Blueprint for Project Success: A project charter defines roles, responsibilities, and project objectives, and empowers the project manager to execute project work and spend the project budget.

Keep It Simple & Big Picture: Your charter should provide a high-level overview, avoid unnecessary details, and keep things simple so that anyone involved in the project can understand what's going on.

Use a Template: Instead of creating a charter from scratch for each new project, use a template (such as ours!) to save you time.

Project charters outline the scope and objectives of your project. If you’re looking to kick off your new project on the right foot, a comprehensive charter is the way to start, and it saves you time down the line.

Without one, your project can't actually officially start, and there's no guarantee that all your stakeholders will be aligned on the project purpose and deliverables. This sets you up for scope creep, miscommunications, and ultimately, project failure.

I’ll describe what a project charter is and how a well-crafted one keeps us on track throughout the project management life cycle. You’ll also find project charter samples, a project charter template, and a list of software tools to help you develop and manage your charter.

What is a Project Charter?

A project charter is a formal document that outlines the shared understanding of a project’s scope , development, and project objectives , while also defining the roles and responsibilities of each party involved. It’s generally a fairly short document.

Project charters give the green light for a project to begin. Similar to the legal definition of the word “charter,” a charter in project management authorizes a project to exist and empowers the project manager to execute the work and spend the project budget. If the charter is approved, the project moves into the planning phase.

You might also see a project charter referred to as a brief or project initiation document (PID) .

Here's a quick recap:

When Should I Create the Project Charter?

The project manager should create the project charter during the project initiation phase . Documenting the purpose of the project, what activities will be part of execution, and who is responsible for performing which activities is critical for aligning key stakeholders before the project kickoff.

Project Charter Template & Sample

Download your template here and use this guide as you are completing it—the insights in this article will help you create a rock-solid project charter. We’ve also included a filled-in sample to give you an idea of what yours should look like.

Project Charter vs. Statement of Work (SoW) and Project Plan

It’s easy to confuse a project charter with a SoW or a project management plan (also known as a project plan), as these documents are closely related. In this section, I’ll define each document and explain when and how you’d use it.

Statement Of Work

A SoW addresses the business need for a project, states what is included or not included as part of a project, and describes specific project deliverables. A SoW also typically summarizes project assumptions and proposed acceptance criteria.

A SoW is a crucial point of reference for project stakeholders, and it’s absolutely essential for PMs to know how to create a SoW . While a well-written SOW can save you a world of trouble, on the flip side, even a tiny mistake can have massive repercussions down the line.

You can think of the SoW as a precursor to and key source of input for the formal project charter.

Sign up to get weekly insights, tips, and other helpful content from digital project management experts.

• Your email *
• Yes, I want to sign up to receive regular emails filled with tips, expert insights, and more to build my PM practice.
• By submitting you agree to receive occasional emails and acknowledge our Privacy Policy . You can unsubscribe at any time. Protected by reCAPTCHA; Google Privacy Policy and Terms of Service apply.
• Comments This field is for validation purposes and should be left unchanged.

Project Plan

Whereas the project charter explains the “what” and “why” of a project, the project plan describes the “how.” Similar to how the project charter builds on the SoW, the project plan builds on the project charter.

A project plan explains how you will manage the various aspects of a project, including potential risks, the project schedule , communications, etc.

Why is the Project Charter Important?

The project charter document is important because it gets your stakeholders to agree on why you’re doing the project, what’s in scope (at a high level), and who’s doing what. Some organizations require a signed project charter before allocating resources , including funding, to your project.

Let’s consider the benefits more in-depth, from the perspectives of each party involved.

Benefits for Project Managers & Teams

• Articulates project value proposition : helps you determine if it’s worthwhile to carry out the project
• Saves time down the road : the time you take to clarify objectives at the beginning of a project is time you won’t need to spend troubleshooting and negotiating later in the project life cycle
• Clarifies the budget : ensures that funding is available and will be released on time. Settling your spending authority and budgets saves time prior to starting the project.
• Sets clear guidelines for your project team : defining success criteria is invaluable for guiding the team as you begin to brief out the project
• Boosts team morale : a team working under a sloppy charter will repeatedly find themselves confused, with their hard work wasted or headed in the wrong direction. A well-written charter gives metrics for a successful project that your team can feel motivated and confident to work toward.

Benefits for Clients & Other Stakeholders

• Creates a shared understanding : stakeholders know what to expect and what constraints the project faces
• Serves as a marketing tool : the project charter can function as a sales document to justify new or existing investments.

What to Include in a Project Charter

Here's what to include in your project charter:

• Introduction : explains the purpose of the charter and provides the project name
• Business case and scope statement : explains the purpose of the project (including business drivers and any related projects), defines high-level activities that are part of the scope of the project (this will help avoid scope creep later), and covers the expected return on investment
• Success criteria : defines what success looks like and how the team will measure success
• Major requirements or deliverables : summarizes high-level requirements and/or key deliverables
• Budget : estimates project costs, ideally by project phase, and defines sources of project funding
• Milestone schedule : estimates project duration and summarizes each major part of the project and all milestones
• Assumptions and constraints : identifies known and unknown parameters upon project initiation
• Project risks : summarizes major known threats or opportunities that may affect project success
• Team and organization : defines project roles and responsibilities
• Approvals : includes a space for stakeholders to record their approval (or disapproval) of the charter.

In addition to these project charter sections, you may also include an appendix with documents such as:

• List of deliverables : if deliverables are already defined, this list contains details about each deliverable—what it is and the associated acceptance criteria
• Scheduling documents : project timeline, calendar, or other documents that sequence project activities and include details about each project milestone or phase
• Communication plan : this includes details about how each person involved will be kept informed about progress, scope changes , etc.

The Project Management Institute’s Guide to the Project Management Body of Knowledge (PMBOK) is a good reference for more information about each of these key elements.

How to Create a Project Charter

There’s no single right way to create a project management charter, but here is a basic process you could consider:

1. Discuss With Stakeholders & Team

Gather information about the project by meeting with key stakeholders, including the project manager, sponsors, clients, and representative project team members.

Don’t forget that stakeholders may also include other teams that provide specialized support, such as network capacity and security experts.

2. Take & Organize Notes

In your discussions, ask questions and take notes that help you to fill out each of the sections of your charter. Use your time wisely to collect the most salient information; you can always fill in the supporting details later on.

3. Use A Template

Take advantage of the myriad project charter templates available online to create the format that best serves your project needs.

DPM Members can use our pre-made charter template, along with a bunch of other time-saving resources. Alternatively, you could use one of the sample project charters in this post as a starting point.

Or, if you want to build your own charter from scratch, you can work through this detailed guide from the Treasury Board of Canada , line-by-line.

4. Include Specific Information

Let’s start with a bad example. For a banking client, a project manager writes the project goal statement in the charter as “improve communication channels.” Yes, good communication is a worthy goal, but the way this is written leaves a lot to the imagination:

• Whose communication channels will be improved? Customers? Internal staff?
• How many users’ needs are we trying to address?
• Will we be updating an existing system or building a completely new system?
• When will it be completed?
• Does the scope extend to training on the new communication tool ?
• Will the contract include any ongoing support for the system?

A complete charter would provide clear, specific information on these questions so that the reader can understand the project purpose . Here’s a better example of a project scope statement (a key part of your charter):

“Create a new communication system to replace ABC system by December 2024, so that customers can chat with their product managers via XYZ bank’s proprietary mobile apps. Train 400 employees to maintain and support the system in-house.”

Of course, this is only the goal statement, not the entire charter. Yet, this example showcases the difference between a sloppily written and a thoughtfully written charter.

Apply similar logic to craft other sections of the charter. The goal of this exercise is for the project sponsor to have sufficient information to be able to approve the project.

5. Review With Team Representatives

After drafting a project charter but before reviewing it with a client, set aside time to review the charter with key members of your team to assess accuracy and completeness.

6. Present For Approval

Notice that this step is not “send for approval.” The project charter is the key to getting approval to undertake the project, and it’s important that it’s presented properly. Avoid simply attaching your charter as a PDF in an email, only to be ignored or dismissed out of hand.

Instead, present your charter to your sponsors, stakeholders, or clients—do this in a meeting or through a slide presentation that includes supporting media. Make sure you leave sufficient time for questions and answers.

Project Charter Examples

Here are three different examples of project charters to consider:

In this example project charter for an interactive voice response system, the project manager has included some notes on the business case, in addition to a project description and the scope.

They've also listed the constraints in priority order, which is useful for providing quick context to whoever is reading this document.

This project charter example clearly lists the project objectives, as well as the milestones and an accompanying timeline.

While you don't necessarily need a complete timeline yet (this will be defined in the project plan), this is a good item to include and then update for project status reports , as the team is completing the work in the execution phase.

This one is similar to the above example in that it includes milestones and a timeline.

It has also clearly laid out the objectives and what's in scope, and includes some notes on the processes that the project will impact, which is useful as this relates to the constraint of attitude towards change (which is listed in the constraints section).

Expert Tips for Creating a Project Charter

When creating a project charter, keep in mind these tips and best practices:

• Keep it simple . Your project charter should leave no room for interpretation. A layperson with no knowledge of the project or your organization should be able to pick up the document and understand what’s going on.
• Big picture over details . Provide a high level overview of the project purpose and outcomes, and avoid getting bogged down in unnecessary details that hinder alignment or create accountability problems later on.
• Create consensus . You could draft the most eloquent project charter on the planet, but it serves no purpose if stakeholders aren’t willing to agree to it. Remember that the project charter is a tool that supports stakeholder alignment. If your charter doesn’t bring stakeholders together, there’s no point in writing one.

Project Management Tools For Developing & Managing Charters

Software tools offer a simple way to develop and store your project charter in an accessible place where all stakeholders and team members can access it as needed.

Types of project management software tools that can be useful include:

• Project management software : You can enter the details about objectives and scope from your project charter and then measure how you're tracking against them throughout the project.
• Mind mapping software : This software is useful for brainstorming and organizing information about the project before you start creating a charter.
• Gantt chart maker : Use this software for plotting milestones and timelines, which will come in handy after your charter is approved.

What's Next?

Have more questions about RACI charts? Become a DPM member and join the conversation  in Slack with 100s of other digital project managers! You’ll also get access to 100+ templates, samples, and examples of project documents, which will save you time and increase your chances of project success.

How to Handle Scope Changes in Project Management

5 Project Management Software Evaluation Criteria 2024

11 Tips For Managing Projects & Resource Library For Beginners

• Search Search Please fill out this field.

What Is Project Management?

Understanding project management.

• Project vs. Program Management

The Bottom Line

What is project management and what are the types.

Investopedia / Theresa Chiechi

Project management is the planning and organization of a company's resources to move a specific task, event, or duty toward completion. It can involve a one-time project or an ongoing activity, and resources managed include personnel, finances, technology, and intellectual property.

Key Takeaways

• On a very basic level, project management includes the planning, initiation, execution, monitoring, and closing of a project.
• Many different types of project management methodologies and techniques exist, including traditional, waterfall, agile, and lean.
• Project management is used across industries and is an important part of the success of construction, engineering, and IT companies.

Generally speaking, the project management process includes the following stages: planning, initiation, execution, monitoring, and closing. We'll discuss each of those stages in more depth later in this article.

Project management often is associated with fields in engineering and construction and, more lately, healthcare and information technology (IT), which typically have a complex set of components that have to be completed and assembled in a set fashion to create a functioning product.

No matter the industry, project managers tend to have roughly the same job: to help define the goals and objectives of the project and determine when the various project components are to be completed and by whom. They also create quality control checks to ensure completed components meet a certain standard.

From start to finish, every project needs a plan that outlines how things will get off the ground, how they will be built, and how they will finish.

Every project usually has a budget and a time frame. Project management uses a type of triage process to keep everything moving smoothly, on time, and on budget. That means when the planned time frame is coming to an end, the project manager may keep all the team members working on the project to finish on schedule. 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.

Types of Project Management

Waterfall project management.

This is similar to traditional project management but includes the caveat that each task needs to be completed before the next one starts. Steps are linear and progress flows in one direction—like a waterfall. Because of this, attention to task sequences and timelines is very important in this type of project management. Often, the size of the team working on the project will grow as smaller tasks are completed and larger tasks begin.

Agile Project Management

The computer software industry was one of the first to use this methodology. With the basis originating in the 12 core principles of the Agile Manifesto, agile project management is an iterative process focused on the continuous monitoring and improvement of deliverables . At its core, high-quality deliverables are a result of providing customer value, team interactions, and adapting to current business circumstances.

Agile project management does not follow a sequential stage-by-stage approach. Instead, phases of the project are completed in parallel to each other by various team members in an organization. This approach can find and rectify errors without having to restart the entire procedure.

Lean Project Management

This methodology is all about avoiding waste, both of time and of resources. The main idea is to create more value for customers with fewer resources. When managing a project with this approach, the goal is similar to that of the lean enterprise production principle. The only resources that will be used on the project are those that directly contribute to its successful completion.

There are many more methodologies and types of project management than listed here, but these are some of the most common. The type used depends on the preference of the project manager or the company whose project is being managed.

Kanban Project Management

Kanban is a highly visual and intuitive project management methodology designed to optimize workflow and enhance productivity. At its core, Kanban relies on a Kanban board, a visual representation of the project's tasks and their status. Tasks are depicted as cards that move through different stages of the workflow, typically represented as columns on the board, such as "to do," "in progress," and "done."

As work progresses, team members move cards across the board, providing real-time visibility into the status of each task and the overall project. By visualizing work in this way, Kanban promotes transparency, collaboration, and efficiency, allowing teams to identify bottlenecks, prioritize tasks, and maintain a steady flow of work.

Six Sigma Project Management

Perhaps considered more of a process improvement tool, Six Sigma can still be used in project management. Six Sigma is a rigorous and data-driven approach to process improvement that aims to minimize defects and variability within organizational processes.

Six Sigma utilizes a structured methodology known as DMAIC : Define, Measure, Analyze, Improve, and Control. In the Define phase, project goals and objectives are clarified, and key metrics are established to measure process performance. The Measure phase involves collecting relevant data and analyzing process performance against established metrics to identify areas for improvement.

In the Analyze phase, root causes of defects or variations are identified through statistical analysis and data-driven techniques. Once root causes are understood, the Improve phase focuses on implementing targeted solutions to address identified issues and optimize process performance. Finally, the Control phase involves establishing controls and monitoring systems to sustain improvements over time, ensuring that processes remain stable and continue to meet desired performance levels.

Scrum Project Management

Scrum is a popular agile framework designed to enhance team collaboration and deliver value iteratively. Scrum breaks down project work into manageable units called sprints, usually lasting between one to four weeks. Each sprint begins with a planning session where the team selects a set of tasks from the product backlog to complete during the sprint. Once the sprint starts, the team works collaboratively to achieve the sprint goal, holding daily stand-up meetings to discuss progress, address challenges, and adapt as needed.

Throughout the sprint, Scrum teams focus on delivering incremental value, often producing a potentially shippable product increment by the end of each sprint. At the conclusion of the sprint, the team conducts a sprint review to demonstrate the completed work to stakeholders and gather feedback.

Steps of Project Management

Different project management frameworks may identify more or less steps. In general, there's five stages of project management, each discussed briefly below.

Phase 1: Initiation

The initiation phase serves as the genesis of the project, where an idea is nurtured into a clear vision. It involves brainstorming, feasibility studies , and refining the project concept to align with organizational goals and stakeholder needs. In the initiation stage, project objectives are defined, along with the scope of work and the desired outcomes.

Phase 2: Planning

Planning is the phase where the blueprint for the project is crafted. Planning involves breaking down the project into manageable tasks, sequencing them logically, estimating resources, and developing a comprehensive project plan.

Planning usually entails some sort of resource allocation tasks. Resource allocation ensures that the necessary people, materials, and budget are available when needed. Risk management identifies potential threats when those resources may not be achievable at the right time or quantity.

Phase 3: Execution

The execution phase is where the project plan comes to life, and the project team swings into action. Tasks are assigned, and the project team members collaborate to bring the project deliverables to fruition. Quality assurance processes are implemented to verify that project deliverables meet the specified quality standards. The execution phase is the period of intense activity as the project potentially visibly progresses toward its goals.

Phase 4: Monitoring

Once the project is underway, the monitoring phase involves tracking project performance against the plan, identifying any deviations or issues, and taking corrective action to bring the project back on course. Change management processes are implemented to address any changes to the project scope, schedule, or resources. Project managers use this phase to tackle any obstacles that come up (i.e. late deliveries, personnel being unavailable, etc.).

Phase 5: Closing

The closing phase marks the culmination of the project journey. Loose ends are tied, and hopefully, accomplishments are celebrated. In the closing phase, the final deliverables are handed over to the customer or end user, and any remaining administrative tasks such as contract closure or financial reconciliations are completed. It's usually a good idea to debrief on "lessons learned" to implement better processes or project management techniques for future similar projects.

Example of Project Management

Let's say a project manager is tasked with leading a team to develop software products. They begin by identifying the scope of the project. They then assign tasks to the project team, which can include developers, engineers, technical writers, and quality assurance specialists. The project manager creates a schedule and sets deadlines.

Often, a project manager will use visual representations of workflow, such as Gantt charts or PERT charts , to determine which tasks are to be completed by which departments. We'll touch on visualizations in the next section. They set a budget that includes sufficient funds to keep the project within budget even in the face of unexpected contingencies. The project manager also makes sure the team has the resources it needs to build, test, and deploy a software product.

When a large IT company acquires smaller companies, a key part of the  project manager's job is to integrate project team members from various backgrounds and instill a sense of group purpose about meeting the end goal. Project managers may have some technical know-how but also have the important task of taking high-level corporate visions and delivering tangible results on time and within budget.

Project Management Tools

To held with organizing and staying on top of tasks, the industry of project management usually leverages a handful of tools. These tools have been touched on throughout this article, but we'll call them out more specifically now. Note that projects that differ in size or scope may call for additional tools, and some smaller projects may be able to do without some of these tools altogether.

• Project management software provides a digital platform for organizing, planning, and tracking project activities. Some more common project management software tools include Microsoft Project, Asana, Trello, or Jira.
• Communication tools facilitate real-time collaboration and communication among project teams, stakeholders, and project managers. For example, Slack is a popular messaging platform that lets team members to communicate through channels, direct messages, and file sharing. Other examples include Microsoft Teams or Zoom.
• Project managers usually rely on document management systems to store, organize, and share project documents. These repositories can range from SharePoint, Google Drive, or DropBox. Document management systems ensure that team members have access to the latest project documentation.
• For companies that want to know what time is being spent on what task, time-tracking software allows team members to record what they've been up to. Platforms like Harvest offer time tracking, expense tracking , and invoicing features, helping project managers monitor project progress. This may be really important for some projects, especially if items are being billed to a client. Another example of this type of tool is Toggl.
• Last, project management entails risk management tools . Something like Risk Register can help identify potential risks, their likelihood, and their potential impact on project objectives. Meanwhile, internal model simulations like Monte Carlo can analyze probability distributions.

Project Management vs. Program Management

Program management and project management are both essential disciplines within the field of organizational management. They do serve distinct purposes and involve different responsibilities.

Project management focuses on the successful delivery of specific, time-bound initiatives. A project is more often a temporary endeavor undertaken to create a unique product, service, or result. On the other hand, program management involves the oversight of multiple related initiatives that collectively contribute to achieving strategic organizational objectives.

As opposed to a project, a program is a collection of projects. Program managers are responsible for aligning individual projects with the organization's strategic goals, and this entails managing interdependencies between projects. For example, a company may sell an entire suite of options for smart technology devices. Program management would ensure that each device (smart light bulbs, smart thermostats, smart security cameras, etc.) would align with larger company initiatives. Project management would ensure optimal management of future products.

Project management is the planning, execution, and monitoring of a series of tasks that have an end goal. Companies embark on project management to achieve a certain process, making sure the proper steps are taken at the right time. This may relate to the company's operations (i.e. moving from one office building to another) or the company's business model (i.e. a technology firm crafting a new software product).

Why Is Project Management Important?

Project management ensures that large deliverables are executed properly. Instead of focusing on one large end product, project management usually documents, evaluates, and monitors a series of smaller, more manageable tasks that come together to make something bigger possible. Project management is important because it ensures end goals are achieved.

What Are Examples of Project Types?

A common example of a project would be product development. Multiple departments are involved in creating the product, marketing it, selling it, and more. The team that designs a project is different from the teams that manufacture, market, or sell the product. As part of a project, each of these teams would be working with a project manager who helps move the product development from one stage to the next.

What Makes a Good Project Plan?

Communication is key to a good project plan. Each team's responsibilities should be detailed with a goal, a time frame, and resources available, for example. Visual explanations such as Gantt charts also are helpful. These are bar graphs that can show each stage of a project and, for example, the time when that stage will take place. This is just one example as the best way to outline a plan for those involved depends on the scope and details of the plan.

Project management is an important part of bringing different teams or different departments together to achieve a singular goal. If creating a product, for example, someone needs to design it, someone needs to build it, someone needs to test it, someone needs to market it, etc. The project manager helps define the ultimate goal of the project and set forth a timeline for how and when that project will be achieved. That way, for example, product testers and product marketers can know what to expect and when to expect it—as well as what they are expected to achieve when the project reaches their respective stages.

Agile Manifesto. " Manifesto for Agile Software Development ."

• Terms of Service
• Editorial Policy
• Privacy Policy

Difference Between Assignment and Project

It’s important to know the difference between these two terms.

Unlike the days of reading from a textbook in a classroom and doing classwork, education has now taken a more solid approach.

Academics have now set sail to project-based work in schools worldwide. Students can now learn in a fun and exciting way.

Please enable JavaScript

Main Differences Between Assignment and Project

Assignments are textbook focused while project encourages hands-on learning.

One could relate a project to simply designing a model to explain a scientific phenomenon, or watching a movie to ascertain its relevance. The freedom it brings, and the lessons learned from its processes are thrilling. Imagine the feeling a student gets from building a science model of real-life outcomes. Assignment, on the other hand, is all cut and dry.

As such, it is not a good judge of a student’s capabilities. Unlike a project, an assignment is also a significant pointer to a student’s weakness and a guide in correcting it.

• Product overview
• All features
• Latest feature release
• App integrations

CAPABILITIES

• project icon Project management
• Project views
• Custom fields
• Status updates
• goal icon Goals and reporting
• Reporting dashboards
• workflow icon Workflows and automation
• portfolio icon Resource management
• Capacity planning
• Time tracking
• my-task icon Admin and security
• Admin console
• asana-intelligence icon Asana AI
• list icon Personal
• premium icon Starter
• briefcase icon Advanced
• Goal management
• Organizational planning
• Campaign management
• Creative production
• Content calendars
• Marketing strategic planning
• Resource planning
• Project intake
• Product launches
• Employee onboarding
• View all uses arrow-right icon
• Project plans
• Team goals & objectives
• Team continuity
• Meeting agenda
• View all templates arrow-right icon
• Work management resources Discover best practices, watch webinars, get insights
• Customer stories See how the world's best organizations drive work innovation with Asana
• Help Center Get lots of tips, tricks, and advice to get the most from Asana
• Asana Academy Sign up for interactive courses and webinars to learn Asana
• Developers Learn more about building apps on the Asana platform
• Community programs Connect with and learn from Asana customers around the world
• Events Find out about upcoming events near you
• Partners Learn more about our partner programs
• Asana for nonprofits Get more information on our nonprofit discount program, and apply.

Featured Reads

• Project planning |

3 elements every project charter needs

Getting started on a new project or initiative can be an exciting feeling. But what about the step right before that, when you need to get your project approved?

The project pitching and approval process can feel like a black box if you’ve never done it before. From gathering the right information to presenting it in a way that works for your project stakeholders, you want to make sure you have the materials you need to succeed. One way to do that is with a project charter.

What is a project charter?

A project charter is an elevator pitch of your project objectives, project scope, and project responsibilities in order to get approval from key project stakeholders. In the charter, you should provide a short, succinct explanation of the main elements of your project before you get started. By creating a project charter before getting started on other, more in-depth project planning documents, you can get approval or course-correct if necessary.

A project charter is one of many project planning materials you can create. Here’s how it compares to other project planning elements:

Project charters vs. project plans

A project charter should only include three elements: your project objectives, scope, and responsibilities. Once your charter has been approved, you should then create a project plan. Your project plan builds on your project charter to provide a more in-depth blueprint of the key elements of your project.

There are seven key elements in a project plan:

Success metrics

Stakeholders and roles

Scope and budget

Milestones and deliverables

Timeline and schedule

Project charters vs. project briefs

A  project brief  is a short document that you should create after your project has been officially approved. The brief is a condensed version of your project plan that your project team and stakeholders can refer back to frequently. Your brief, like the charter, provides context about why this project is a good idea, in addition to what you’ll be doing during the project.

A project brief has four parts:

Background information

Project objectives and success criteria

Project timeline

Target audience

Project charter vs. business case

A project charter and  business case  have the same fundamentals: these are both tools to pitch a project to the appropriate stakeholders. The main difference between a project charter and a business case is scope.

A business case is a formal document that explains the benefits and risks of a significant business investment. For example, if you’re pitching a large-scale investment with an external agency, a significant increase in current business practices, or a new product line or service, you’d want to create a business case. Alternatively, if your project needs approval but it’s smaller in scope—for example, a campaign that’s similar to past campaigns or a product launch that fits within your current go-to-market strategy—create a project charter instead.

Do you need a project charter?

There are a variety of project planning tools, and a project charter isn’t always the best one for the job. Here’s when to create one—and when you might be better off creating something else.

Create a project charter  to pitch and get approval for a project. A project charter gives stakeholders a clear sense of your project objectives, scope, and responsibilities. Key stakeholders can use the project charter to approve a project or suggest changes.

Create a business case  if your project represents a significant business investment. A business case includes additional information and documentation, including the project’s return on investment and any  relevant project risks .

Create a project plan  if your project has been approved. A project plan will build on your project charter to provide additional information, like the project timeline or  key project milestones .

Create a project brief  if you want to create a document that summarizes the key high-level details of your project plan.

Create an  executive summary  if you want to provide a summary of your document to executive stakeholders.

Create a  project roadmap  if you want to view a high-level timeline of your project in a  Gantt chart .

How to create a project charter

In a project charter, you’ll share project details with key stakeholders in order to get approval to kick off your project. There are three main project charter elements:

To begin your project charter, share your  project objectives  and project purpose. In this section, you should outline why this project is important and what the key objectives are for the end of the project. Make sure your project purpose clearly explains why it’s important to work on this project and how this project will support your company goals.

In addition to your project purpose, you should also clarify your project objectives. These are the things you plan to achieve by the end of the project, like deliverables or assets. To create good project objectives, follow the  SMART method . Make sure your objectives are:

The second key element in your project charter is the project scope. Your project scope statement defines exactly what is and isn’t part of the project. When you draft a project scope, you’re setting boundaries and, more importantly, outlining what you won’t do during the project timeline.

As you create your project charter, the most important part of explaining scope is outlining the ideal project budget. Remember, you will use your project charter document to pitch this project to stakeholders—so you need to clearly show what the budget is and where that money will go.

In the final section of your project charter, you should explain who will be working on the project. This includes any key project stakeholders, executive stakeholders, project sponsors , and the general project team. If you haven’t already, draft up a brief resource management plan to illustrate how various resources will be allocated during the project.

Project charter examples

Project charter template

When you’re ready to get started, follow this easy-to-use template to create your next project charter.

Project name

Name your project. Make sure this is descriptive enough that most people will understand what you’re working on.

Project manager

Who is the point of contact for this project?

Last revision date

Your project charter is a living document. Including the last revision date can be helpful for team members who are frequently checking back on the charter.

Project purpose

Why are you working on this project?

Project objectives

What deliverables and assets do you plan to achieve by the end of the project?

Project scope

What are the boundaries of your project deliverables? Which initiatives are not included in the project?

Project team and resources

Who is working on this project? Which resources (e.g. people, tools, and budget) are available for this work.

Stakeholders and approvers

Who are the project stakeholders? Who needs to approve the project charter or any project deliverables?

From project charter to project success

Once your project charter has been approved, you can move forward with project planning. As you create additional project planning documents and get started with project management, make sure you are storing all of your project details in a centralized tool that everyone can access.

Naturally, we think Asana is the best tool for the job. With Asana, you can manage team projects and tasks to stay in sync and hit your deadlines. Learn more about the  benefits of project management .

Related resources

New site openings: How to reduce costs and delays

Provider onboarding software: Simplify your hiring process

15 creative elevator pitch examples for every scenario

Timesheet templates: How to track team progress

• EN Action Another action
• Free Counselling

Thanks for visiting TopUniversities.com today! So that we can show you the most relevant information, please select the option that most closely relates to you.

• Looking for undergraduate studies
• Looking for postgraduate studies
• Student but not looking for further education at the moment
• Parent or Guardian
• University administrator
• Professional

Thanks for sending your response.

Your input will help us improve your experience. You can close this popup to continue using the website or choose an option below to register in or login.

Already have an account? Sign in

What is a capstone project? And why is it important?

Stephanie Lukins

Share this Page

Table of contents

• Introduction

It prepares you for the working world

It helps build your cv and help you stand out as a candidate , it offers valuable practical experience – something many graduates do not have, it hones on specific skills that are highly valued by employers.

Sponsored by York University

What is a capstone project?

The capstone project has become an integral part of the university degree curriculum. It can take many various forms, but its purpose remains the same. The capstone project is a unique opportunity to carry out independent group research in order to devise an innovative solution for a real-world problem. While a project of this scope and scale can be challenging, it can also be very rewarding.

The capstone project is usually the final assignment and plays a vital role in preparing students for the world of work thanks to its practical applications and ability to help hone students’ professional knowledge and skills.

At York University in Toronto, Canada, things are a little different. In 2019, the university revised the traditional capstone project and created C4: Cross-Campus Capstone Classroom . While it still possesses the fundamentals of the traditional capstone project, C4 is a new, year-long initiative that brings students together from various degree programmes to work in interdisciplinary teams with faculty and project partners on real-world challenges pitched by non-profit organisations, start-ups and businesses to create social impact.

TopUniversities spoke to Megan Tran and Javeria Mirza, two students at York University, to find out about their capstone project and why they feel it has played an important role in not just their academic development, but their professional development as well.

What is the purpose of a capstone project?

The capstone project is designed to consolidate final-year students’ learning with valuable hands-on experience to help develop them into well-prepared and well-rounded graduates.

Students work together in small groups to come up with innovative solutions for real-life problems, all while gaining valuable insights into the demands and responsibilities of the working world. This gives students a chance to bring their leadership and management skills alive and understand the consequences of their decisions in a ‘safe space’.

C4 gives students an insight into global affairs, international relations as well as social corporate responsibility and sustainability. 

Final-year bachelor’s in international studies student Megan and master’s in political science student Javeria were two of the eight interdisciplinary students, from the Faculty of Environmental Studies, the Lassonde School of Engineering, Glendon College, and the Faculty of Liberal Arts & Professional Studies at York University who worked together on the ‘Solar Floatie’ project.

“As a group, we were all interested in using technology and design-thinking for good. Our collective passion for social impact brought us together as a team. CooperLab at York University led by Professor Thomas Cooper was already spearheading the idea of an inflatable solar collector,” said Javeria.

“But how we went about developing the technology and what we wanted to use it for was up to us,” added Megan.

“ The Solar Floatie was born when the engineering side of the solar collector project was merged with the anthropology side and the United Nations Sustainable Development Goals (SDG) framework to propose a sustainable implementation model,” explained Javeria.

Undertaking a capstone project demonstrates to prospective employers that you’re more than just a potential candidate with the necessary academic qualifications. It shows your dedication to an issue which demands time and effort, as well as strict professionalism, work ethic and experience working in a practical, hands-on setting.

As a graduate, the reality of securing a job can be difficult as many roles demand practical experience. Many graduates are conceptually strong and suitable candidates, but a lack of applied knowledge in practical settings can make it challenging to demonstrate such experience and skills on their CV or in an interview.

The capstone project is a great solution and is something which both Megan and Javeria felt helped bridge that critical gap and has given them a competitive advantage as young professionals.

“It gave me an opportunity to learn outside a traditional academic setting and allowed me to explore my interest in sustainability and passion for social impact,” said Megan. “Since being a part of this project, I’ve been involved with a variety of organisations carrying out work that align with these passions.”

Javeria echoes Megan’s sentiments.

She said: “Bridging the lessons learnt during the capstone project such as the value of continuously learning, taking initiative, and working effectively with people from diverse disciplinary backgrounds has been invaluable in both my UN work and my graduate studies.”

Testimonials

"CUHK’s MBA programme provided me with the stepping stone into a larger sports Asian market wherein I could leverage the large alumni network to make the right connections for relevant discussions and learning."

Read my story

Abhinav Singh Bhal Chinese University of Hong Kong graduate

"I have so many wonderful memories of my MBA and I think, for me, the biggest thing that I've taken away was not what I learned in the classroom but the relationships, the friendships, the community that I'm now part of."

Alex Pitt QS scholarship recipient

"The best part of my degree is getting to know more about how important my job as an architect is: the hidden roles I play, that every beautiful feature has significance, and that even the smallest details are well thought out."

Rayyan Sultan Said Al-Harthy University of Nizwa student

"An MBA at EAHM is superior due to  the nature of the Academy’s academic and  industry strength. The subject  matter, the curriculum structure and the  access to opportunities within the hospitality industry is remarkable."

Sharihan Al Mashary Emirates Academy of Hospitality Management graduate

The capstone project encompasses a real-life working culture which aims to instil a set of specific skills that are both highly valued by employers and will ultimately serve students well into their careers.

York University’s C4 focuses on the development of a wide range of skills, including creative, critical, and strategic thinking, effective communication, teamwork, problem solving and research analysis through diverse learning approaches and perspectives. Students deepen their sense of social and ethical responsibilities as they learn to mobilise their knowledge across disciplines and work effectively in interdisciplinary teams while engaging professionally with their peers and professors.

Lead image: Solar Floatie project team members work on assembling the solar energy collector, under Professor Thomas Cooper’s direction. Credit: York University

+ 2 others saved this article

+ 3 others saved this article

As the former Head of Sponsored Content for TopUniversities.com and TopMBA.com, Stephanie created and published a wide range of articles for universities and business schools across the world. She attended the University of Portsmouth where she earned a BA in English Language and an MA in Communication and Applied Linguistics.

Recommended articles Last year

Oxford or Cambridge?

Top law schools

Top business schools

Discover top-ranked universities!

universities

events every year

Sign up to continue reading

Ask me about universities, programs, or rankings!

Our chatbot is here to guide you.

QS SearchBot