project approach assignment

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

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.

How to Create a Realistic Project Plan with Templates & Examples

As a project manager, a huge part of your role is to write project plans that help you keep projects on track. But that’s not all a project plan should do. 

A project plan is arguably the most important document you’ll create for a project. At its core, a plan should communicate your project approach and the process your team will use to manage the project according to scope.

Let’s take a closer look at how you can develop a rock-solid planning process that guides your team and projects to success.

What is a project plan?

Project plan example: what to include, why you should always write a project plan, 5 steps to an effective project planning process, how to create a project plan in teamgantt, free project plan templates.

A project plan is a document that maps out the tasks, effort, timing, and resources needed to meet project goals within a predefined scope. It’s often presented in the form of a gantt chart because it’s easy to visualize the project timeline and ensure work stays on track.

Any solid project management plan should answer the following questions:

• What are the major deliverables?
• How will we get to those deliverables and the deadline?
• Who’s on the project team, and what role will they play in those deliverables?
• Which stakeholders need to provide feedback on deliverables, and when?
• When will the team meet milestones?

A project plan communicates this information in a simple, straightforward way so everyone clearly understands the objectives and how they contribute to project success. It may also be accompanied by other planning documents, such as a project charter , risk assessment , or communication plan .

While no two project plans are alike, they all share the same common building blocks. Be sure to include the following components in any project plan you create:

• Project tasks : A detailed list of work to be done organized by project phase, process step, or work group
• Project schedule : A visual timeline of task start dates, durations, and deadlines, with clear progress indicators
• Key milestones : Major events, dates, decisions, and deliverables used for tracking forward progress
• Dependencies : A line connecting tasks that need to happen in a certain order
• Resources : Assignments that indicate the person or team responsible for completing a task

Here’s a simple example of what a project plan looks like with these basic elements highlighted:

Some people don’t understand the power of a good project plan. If you feel pressured to skip the plan and jump right into the work, remind your team and stakeholders that having a plan benefits everyone by making it easier to:

• Build consensus before work begins : A detailed project plan ensures everyone has a clear understanding of—and agrees on—the overall process, scope, staffing, and even communications from the outset. That goes a long way in keeping project confusion and pop-up requests from gumming up the works.
• Avoid scheduling conflicts : Project plans enable you to organize tasks so it’s clear who's responsible for what and when. If your team is juggling multiple projects, you can cross-reference other plans to see who’s available to take on new work before committing to a timeline.
• Monitor project goals and scope : When new tasks creep in, it’s easy to lose sight of the original objectives. Spelling out the work you need to complete in a time-based plan keeps project goals front and center so you can ensure project scope stays intact.  ‍
• Hold your team and stakeholders accountable : A good project plan sets expectations around the process and pacing you'll follow each step of the way. When plans are shared with teams and stakeholders, it keeps folks honest about what is—or isn’t—happening and forces you to resolve issues in a timely way.

Easy drag and drop features with templates for faster scheduling. Plan a project in minutes, collaborate easily as a team, and switch to calendar and list views in a single click.

Poor planning can lead to some pretty ugly consequences—from missed deadlines and budget overages to team burnout and client frustration. That’s why it’s important to establish a solid process you can use to plan any project. 

Planning a project doesn’t have to be difficult. These basic project planning steps can help you write a plan that’s both realistic and on target.

• Start with project discovery & definition
• Draft a rough outline of your plan
• Formalize your project management plan
• Present & confirm your plan
• Execute your plan & adjust as needed

Step 1: Start with project discovery and definition

A project plan is more than a dry document with dates. It’s the story of your project, and you don’t want it to be a tall tale! So make sure you know all the facts before you start creating a project plan.

Understand the project scope and value

Understanding the ins and outs of the project will help you determine the best process and identify any snags that might get in the way of success. Conduct your own research to dig deeper on:

• Project goals and outcomes
• Partnerships and outlying dependencies
• Potential issues and risks

Review the scope of work , and dive into any documents or communications relevant to the project (maybe an RFP or notes from sales calls or client meetings). Be thorough in your research to uncover critical project details, and ask thoughtful questions before you commit to anything. 

Interview key stakeholders

If you want to dazzle stakeholders with a stellar project delivery, you’ve got to know how they work and what they expect. Schedule time with your main project contact, and ask them some tough questions about process, organizational politics, and general risks before creating a project plan. 

This will give project stakeholders confidence that your team has the experience to handle any difficult personality or situation. It also shows you care about the success of the project from the start.

Be sure to discuss these things with your stakeholders:

• Product ownership and the decision-making process
• Stakeholder interest/involvement levels
• Key outages, meetings, deadlines, and driving factors
• Related or similar projects, goals, and outcomes
• The best way to communicate with partners and stakeholders

See a list of sample interview questions to ask stakeholders so you can develop better project plans.

Get to know your team

The last step in the research phase is to take time to learn more about the people who’ll be responsible for the work. Sit down with your team and get to know their:

• Collaboration and communication styles
• Availability and workload

Understanding these basics about your team will help you craft a thoughtful plan that takes their work styles and bandwidth into consideration. After all, a happy team delivers better projects.

Step 2: Draft a rough outline of your plan

Now that you’ve gathered the basic project details, the next step is to knock out a rough draft of your plan. Take some time to think about the discussions you had in the pre-planning phase and the approach your team might take to meet the project goals.

Sketch out the main components of your project plan

Sit down with a pen and paper (or a whiteboard), and outline how the project should work at a high level. Be sure you have a calendar close by to check dates.

If you’re at a loss for where to begin, start with the who, what, when, and how of the project. A first outline can be very rough and might look something like a work breakdown structure . Make sure your project outline includes the following components:

• Deliverables and the tasks required to create them
• Your client’s approval process
• Timeframes associated with tasks/deliverables
• Ideas on resources needed for tasks/deliverables
• A list of the assumptions you’re making in the plan
• A list of absolutes as they relate to the project budget and/or deadlines

Considering these elements will help you avoid surprises—or at least minimize them. And remember, you’re doing this as a draft so you can use it as a conversation-starter for your team. It’s not final yet!

Get input from your team on process, effort, and timing

You don’t want to put yourself or your team in an awkward position by not coming to a consensus on the approach before presenting it to your client. That's why a project manager can’t be the only one writing a project plan.

Once you’ve created a basic project outline, take those rough ideas and considerations to your team. This enables you to invite discussion about what might work rather than simply dictating a process. After all, every project must begin with clear communication of the project goals and the effort required to meet them. 

Be sure to get input from your team on how they can complete the tasks at hand without killing the budget and the team’s morale. As a project manager, you can decide on Agile vs. Waterfall approaches , but when it comes down to it, you need to know that the team can realistically execute the plan.

You can also use this review time to question your own thinking and push the team to take a new approach to the work. For example, if you’re working on a digital product, could designers start creating visual concepts while the wireframes are being developed? Or can you have two resources working on the same task at once?

Running ideas by the team and having an open dialogue about the approach not only helps you build a more accurate project plan. It gets everyone thinking about the project in the same terms. This type of buy-in and communication builds trust and gets people excited about working together to solve a goal. It can work wonders for the greater good of your team and project.

Step 3: Formalize your project management plan

You should feel comfortable enough at this point to put together a rock-solid project schedule using whatever tool works for you. 

Build out a detailed project schedule that’s easy to read

Any good online project planning tool will help you formalize your thoughts and lay them out in a consistent, visual format that’s easy to follow and track. (Ahem, TeamGantt works nicely for a lot of happy customers. ) 

Make sure tasks have clear start and end dates so there’s no question when work needs to happen to hit project deadlines. Organize work into phases, and use labels and/or color-coding to improve scannability. The easier your project plan is to understand at a glance, the better!

See how to create a project plan in TeamGantt

Consider how your team likes to work

Be as flexible as possible when it comes to how your project plan is presented. There's no absolute when it comes to how to format your plan as long as you and your team understand what goes into one.

Remember, people absorb information differently. While you might be partial to a gantt chart, others might prefer to view tasks in a list, calendar, or even a kanban board. You can make all of those variations work if you’ve taken the steps to create a solid plan.

For example, here’s an Agile project plan we built that lists each sprint as its own task group with milestones for sprint planning and deployment.

And here’s what that same project plan looks like if you turn it into a kanban board in TeamGantt. Simply click the Board tab and set up your columns so your team can manage their daily workflows more easily.

If your team currently prefers spreadsheets and isn’t quite ready to use TeamGantt yet, try our free Excel gantt chart template .

Step 4: Present and confirm your plan

You’re almost finished! Now it’s time to do your due diligence. It’s easy to throw stuff in a plan, but you have to make sure you get it right.

Run your final plan by your internal team

Your team needs to know the reality of your plan as it stands after you’ve built it out in TeamGantt. And you want to be sure they’re comfortable committing to the details. If they don’t, things will quickly fall apart!

Always review your final plan with your team before delivering it to stakeholders. Why? Because things like dates and tasks—and even assignments—will shift as you formalize the rough sketch of your plan. 

Here are a few things you’ll want to discuss with your team as you review the final plan together:

• Review times
• Team work times
• Dependencies
• Time off, meetings, and milestones
• The final deadline
• Any assumptions you’ve made
• Major changes since your last talk

There’s nothing more embarrassing than delivering a plan with an error or a promise you can’t keep. Taking a few minutes to get buy-in from your team will give everyone peace of mind about your plan.

Review your project plan with stakeholders

Once you’ve confirmed the plan with your team and have their full sign-off, you’re ready to share your project plan with stakeholders . 

When delivering your project plan, make sure you provide an executive summary. This might come in the form of a project brief . A short recap of the overall methodology, resources, assumptions, deadlines, and related review times will help you convey what the plan means to the project and everyone involved.

Project plans can be daunting, so schedule time to present your project plan to stakeholders at a high level. Here are some things you’ll want to point out about your plan during this review:

• Overall process and pacing
• Major deliverables and timing
• The time they’ll have to review deliverables
• Overall timing for task groups or phases
• How far off you are from the deadline
• Wiggle room on the final deadline

If a stakeholder is interested in the day-to-day details, feel free to walk them through the plan line by line. Otherwise, start by explaining overall sections or phases, and be sure to come back to your plan at intervals throughout the project to remind them of tasks, next steps, and overall progress.

Step 5: Execute your plan and adjust as needed

Some projects are smooth and easy to manage, and others are a complete nightmare that wake you up at 3 a.m. every other night. Thankfully, having a solid project plan is your best defense against project chaos once work gets underway.

Keep in mind that project plans are living documents. Projects change constantly, and someone has to stay on top of—and document—that change. Remember to:

• Update your plan regularly as work progresses and things change
• Communicate changes to your team, partners, and stakeholders
• Monitor and communicate risks as your project evolves

Ready to plan your project in TeamGantt? Follow these easy steps to build a plan that’s structured well and includes the elements you need for project success.

1. Enter your basic project details.

To create a new project plan in TeamGantt, click the New Project button in the upper right corner of the My Projects screen. Then enter your project name and start date, and select the days of the week you want to include in your plan. Click Create New Project to move on to the next step.

2. List out your project tasks and milestones.

Now the real planning fun begins! Enter all the different tasks it will take to get the job done. If there are any key meetings, deliverable deadlines, or approvals, add those as milestones in your project plan.

3. Organize tasks into subgroups. 

Scrolling through one long list of tasks can be mind-numbing, even to the best of us. Break tasks down into phases or sections to ensure your project plan is easy to read and understand. 

4. Add task durations and milestone dates to the project timeline.

A visual project plan makes it easy to see exactly what needs to get done by when. Make sure every task has a start and end date so nothing falls through the cracks. TeamGantt’s drag and drop feature makes this planning step quick and easy.

5. Connect related tasks with dependencies.

Adding dependencies between tasks ensures work gets done in the right order and also helps you plan for delay risks. If your plan shifts and you need to move tasks around, dependencies speed up the process.

6. Assign responsible team members to tasks.

That way there’s no confusion about who’s doing what, and your team can update and manage their daily tasks . Don’t forget to check team availability along the way to avoid overloading anyone with too much work.

7. Use the RACI chart to define task roles more clearly.

This feature takes accountability one step further by letting you assign more specific roles to each task: Responsible , Accountable , Consulted , and Informed . Learn how RACI charts work and what each role means.

8. Add hourly estimates and/or points to each task. 

This makes it easy to see the lift each task involves at a glance. Including hourly estimates in your project plan also enables you to manage workloads and track overages more accurately.

9. Color-code tasks for better scannability.

You can use colors to categorize tasks by project phase, priority, department, or team member—whatever makes visual sense to you and your team.

10. Add notes to clarify tasks or spell out important details.

There’s no such thing as too much information if it means your team has what they need to deliver quality work on time. Use the Notes section of your Discussion tab to enter any pertinent details your team will find helpful.

11. Upload important documents to the project.

This ensures project files are accessible to everyone in a centralized hub.  For example, you might attach your creative brief to the project so your content and design teams have clear direction for completing their deliverables.

If you’re planning a project for the first time or taking on a totally new type of project, you might be struggling to get your plan off the ground. We created a simple project management plan template to help you get started.

TeamGantt gives you the ability to quickly and easily build and adjust your plan using drag and drop scheduling. Plus, it comes with customizable views to fit every team member’s work style. 

Try our basic project plan template for free!

Looking for more specific project plan examples to jumpstart your process? Use these project planning templates to generate ideas and save time building out your plan:

• Construction project plan template
• Event planning template
• Strategic marketing plan template
• Tactical marketing plan template
• Software development plan template
• Video production schedule template
• Website project plan template

Plan your next project in minutes

Discover just how easy project planning can be with TeamGantt. Create your first gantt chart for free!

Total with VAT: {{CartWithDetails.cartMaster.total_after_vat}} {{currency}}

Your cart is empty.

12 Project Management Methodologies: Types, Tools, Techniques, And How to Choose

Written By : Bakkah

27 Feb 2024

Table of Content

Definition of Project Management Methodologies:

Types of project management methodologies, project management methodologies tools , project management methodologies techniques, how to choose a project management methodology, explore bakkah's leading courses to boost your skills in project management and business analysis:, popular articles.

PRINCE2 Methodology - 2024 Full Guide About Advantages and Disadvantages

Prosci Methodology - Change Management Methodology

Application of PMO in government entities in Saudi Arabia

Project management methodologies are systematic frameworks and guidelines utilized by organizations to efficiently plan, execute, and complete projects. They offer structured approaches to project management, ensuring adherence to timelines, budgets, and objectives. These methodologies encompass diverse principles, practices, and tools designed to facilitate effective communication and coordination among project-implementing teams. 

Project management methodologies vary in their approach, with some emphasizing flexibility and adaptability (e.g., Agile) while others focus on sequential and structured processes (e.g., Waterfall). The appropriate methodology must be selected according to the type of project and its unique circumstances. The goal is to enhance project efficiency, minimize risks, and deliver high-quality results, ultimately contributing to achieving the specified goals and objectives of the project.

Project management methodologies refer to the systematic frameworks, processes, and guidelines organizations follow to plan, execute, monitor, and complete projects. These methodologies provide a structured approach to managing projects, ensuring they are completed on time, within budget, and meet the specified goals and objectives.

Project management methodologies encompass diverse principles, practices, and tools designed to facilitate effective communication and coordination among project-implementing teams.

They can vary in their approach, with some methodologies emphasizing flexibility and adaptability (e.g., Agile), while others focus on sequential and structured processes (e.g., Waterfall). The appropriate methodology must be selected according to the type of project and its unique circumstances.

The goal of Project Management Methodologies is to enhance project efficiency, minimize risks, and deliver high-quality results, ultimately contributing to achieving the specified goals and objectives of the project.

Various tools support their implementation, enhancing collaboration and communication, while diverse techniques facilitate effective project planning, execution, and control.

There are diverse project management methodologies, each with different principles, processes, and approaches. Here are some common types:

1. Waterfall Methodology

Waterfall project management is a traditional approach to project management where tasks are completed sequentially and linearly. 

The methodology is called "waterfall" because progress is seen as flowing steadily downwards through phases, like a waterfall. Each phase must be completed before moving on to the next one, and changes to the project are generally not allowed once a phase is closed.

Here are the main phases in the waterfall project management methodology:

• Requirements: Define project scope, objectives, and deliverables.
• Design: Create a detailed plan for how the solution meets requirements.
• Implementation (or Construction): Include coding or construction of the project.
• Testing: Ensure the project meets specified requirements through various testing phases.
• Deployment (or Implementation): Implement the project in the production environment after the success of testing.
• Maintenance and Support: Address issues and user concerns and make updates as needed.

The waterfall methodology is best suited for projects where the requirements are well-understood and unlikely to change significantly during the development process.

It is often used in industries like construction and manufacturing. However, one of its main drawbacks is its inflexibility to adapt to changes once the project has started, as it does not easily accommodate changes in requirements.

2. Agile Methodology

Agile methodology is an iterative and flexible approach to project management that focuses on collaboration, adaptability, and customer satisfaction.

Unlike the linear nature of the waterfall model, agile divides a project into small increments with minimal planning and delivers functional pieces of the project in short time frames, known as iterations or sprints.

Primary principles and practices of agile include:

• Projects are divided into small manageable iterations, delivering potentially shippable product increments.
• Collaboration and communication between team members, stakeholders, and customers are crucial for quick adaptation to changes and alignment with goals.
• Continuous customer feedback allows for adjustments based on changing requirements.
• Agile is flexible and adaptable to changes in requirements or priorities at any stage.
• Continuous delivery aims for a potentially shippable product at the end of each iteration, allowing for early and regular value delivery to the customer.
• Prioritization and timeboxing based on value and importance ensure focus and urgency in delivering value.
• Agile encourages self-organizing, cross-functional team formation that collectively possess the necessary skills to deliver a complete product.

Popular agile frameworks include Scrum, Kanban, and Extreme Programming (XP), each with specific practices and roles. 

Agile is widely used in software development and various industries for its adaptability and customer-centric approach.

3. Scrum Framework

Scrum is one of the most widely used agile frameworks for managing complex software development projects. It provides a structured yet flexible approach to product development.

Key elements of the Scrum framework include:

• Roles: Include Product Owner, Scrum Master, and Development Team.
• Artifacts: Comprise the Product Backlog, Sprint Backlog, and Increment.
• Events: Include Sprint Planning, Daily Stand-up, Sprint Review, and Sprint Retrospective.

Scrum's iterative and incremental approach, along with its emphasis on collaboration and adaptability, makes it particularly effective for projects where requirements may change or evolve during development.

4. Kanban Methodology

Kanban is a project management methodology that visualizes workflow using boards, cards, and columns. It also limits tasks that are in progress simultaneously to prevent overloading the team and ensure a steady flow of work.

Emphasizing continuous improvement, Kanban employs feedback loops and a pull system, adapting work based on demand. Service Level Agreements (SLAs) are often used in Kanban to define the expected time frames.

Known for flexibility and adaptability, Kanban suits various industries like architecture, construction, marketing, education, software development, design, and law. Kanban fosters collaboration and shared responsibility and allows incremental process improvements based on specific needs and context.

5. Lean Project Management

Lean Project Management (LPM) is an approach to project management that draws inspiration from Lean principles. The Lean philosophy focuses on minimizing waste, optimizing efficiency, and continuously improving processes.

Lean principles are applied to enhance project delivery, reduce unnecessary activities, and deliver value more effectively. 

Principal aspects of Lean Project Management methodology include eliminating waste, using value stream mapping, continuous improvement (Kaizen), customer focus, pull scheduling, visual management, batch size reduction, flexible planning, and cross-functional team use. LPM is suitable for industries like manufacturing, construction, and software development.

Its focus on efficiency and customer value makes it a valuable approach for organizations seeking to optimize their project delivery processes.

6. PRINCE2 (Projects IN Controlled Environments)

PRINCE2 (Projects IN Controlled Environments) is a widely adopted project management methodology developed by the UK government. It provides a structured and process-driven approach to project management, emphasizing flexibility and adaptability.

PRINCE2 divides projects into manageable stages, with defined roles and responsibilities, ensuring organized and controlled project execution.

The methodology consists of seven processes:

• Starting Up a Project (SU): Ensures project prerequisites are in place.
• Initiating a Project (IP): Defines project scope, objectives, and plans.
• Directing a Project (DP): Provides senior management with chief controls.
• Controlling a Stage (CS): Manages day-to-day project activities.
• Managing Product Delivery (MP): Ensures efficient product work.
• Managing a Stage Boundary (SB): Focuses on transitioning between stages.
• Closing a Project (CP): Formally closes the project and ties up loose ends.

PRINCE2 is known for its focus on continuous improvement and adaptability, making it a valuable tool for delivering successful projects within time, cost, and quality constraints.

Boost your career with Bakkah’s PRINCE2 courses:

• PRINCE2® Training Course Online
• PRINCE2® Agile Foundation & Practitioner Online Course and Certification

7. Critical Path Method (CPM)

Critical Path Method (CPM) is a project management technique that identifies the critical path of activities, potential risks, team roles, and the sequence of tasks determining the shortest project duration. Key steps:

• Task Breakdown: Identify and sequence project tasks. 
• Duration Estimation: Assign time estimates to tasks.
• Network Diagram: Create a visual representation of task dependencies.
• Critical Path Identification: Find the path critical for project completion.
• Float/Slack Calculation: Determine non-critical task flexibility.
• Resource Allocation: Efficiently allocate resources.
• Monitoring and Control: Monitor progress continuously, update schedules, and take corrective actions., update schedules, and take corrective actions.

CPM is an essential tool for effective project planning and control. It aids in prioritizing critical tasks, managing time constraints, and optimizing project schedules. CMP can be used in several projects, such as engineering, manufacturing, construction, and science.

8. Six Sigma ( Continuous Improvement Methodology)

Six Sigma is a data-driven project management methodology focused on improving process efficiency continuously and reducing defects or errors. Developed by Motorola in the 1980s, Six Sigma seeks to minimize variations and achieve higher levels of quality in processes. It is often applied in manufacturing and process improvement projects. Here is a concise overview of the Six Sigma project management methodology:

• Define (D): Clearly articulate the problem, project goals, scope, and customer requirements.
• Measure (M): Establish metrics, collect data, and measure baseline performance.
• Analyze (A): Use statistical tools to identify root causes of defects or inefficiencies.
• Improve (I): Develop and implement solutions, testing and refining as needed.
• Control (C): Establish measures to sustain improvements and prevent recurrence of defects or issues.

The Six Sigma methodology is often represented by the acronym DMAIC (Define, Measure, Analyze, Improve, Control). Additionally, for more complex or considerable process changes, there is another phase known as DMADV (Define, Measure, Analyze, Design, Verify).

Bakkah provides certification levels such as Six Sigma Green Belt and Six Sigma Black Belt are available for individuals to demonstrate proficiency in applying Six Sigma principles and methodologies. Organizations implementing Six Sigma often experience enhanced efficiency, reduced defects, and improved customer satisfaction.

9. RAD (Rapid Application Development)

Rapid Application Development (RAD) is a project development methodology that prioritizes quick iterations and prototypes over extensive planning.

It involves user participation throughout the process, parallel development of system components, and a flexible, adaptive approach. Prototyping is a key feature, allowing for continuous refinement based on user feedback. RAD aims to deliver a functional product rapidly, focusing on time and cost efficiency.

Popular RAD tools include Microsoft Visual Basic, PowerBuilder, and OutSystems. The methodology suits projects with changing requirements but may not be ideal for highly structured endeavors.

10. Incremental and Iterative Methodologies

Incremental development involves dividing the project into small increments, each delivering a part of the final product's functionality linearly. User feedback is integrated after each increment, providing ongoing adaptability and the ability to identify and correct issues early. This approach enables early delivery and reduced project risk.

On the other hand, iterative development goes through cycles or iterations, refining the entire system with each iteration. It is highly flexible and accommodates changing requirements throughout the development process.

11. Hybrid Methodologies

Hybrid methodologies in project development involve blending elements from different traditional and agile approaches to create a flexible and tailored solution. That allows teams to adapt practices based on the project's unique requirements, leveraging both structured planning and iterative development. 

In a hybrid methodology, the most appropriate elements from each methodology are identified and combined harmoniously. Examples include combining Waterfall and Scrum or integrating lean principles with agile practices.

The goal is to manage risks effectively, enhance flexibility, and address the project-specific needs. Effective communication is crucial to mitigate potential challenges introduced by diverse practices integration.

12. Extreme Programming (XP)

XP is an Agile methodology that emphasizes collaboration, adaptability, and delivering high-quality software through practices such as continuous testing and frequent releases.

Extreme Programming methodology is one of the famous methodologies for managing and developing software and other technical projects. It is based on diverse principles and practices, focusing on increasing software quality and improving team productivity.

A team needs to follow this method if the project is fast-paced or subject to regular change and thus has a dynamic rather than static nature.

The Extreme methodology also aims to achieve productive cooperation between team members and increase the quality of the final product and its flexibility in the face of changes.

Here are the main principles and practices of Extreme Programming:

• XP is built on a set of core values, including communication, simplicity, feedback, and courage.
• Developers work in pairs, one writing code and the other reviewing it in real time. That promotes collaboration, knowledge sharing, and code quality.
• Developers write tests before writing the actual code. That ensures that the code meets specifications and facilitates maintenance and updates.
• Code is integrated frequently to identify and address integration issues early in the development process.
• XP improves code design regularly without changing its functionality.
• XP keeps the design as simple as possible, making it easier to understand, modify, and maintain.
• Frequent and direct interaction with the customer allows for quick adjustments to changing requirements and priorities.
• XP emphasizes continuous improvement through regular reflection on the development process and changes in implementation to enhance efficiency and quality.

Bakkah provides a variety of accredited project management Courses for all professional certificates in project management, risk management, and others.

In brief, choosing the most suitable project management methodology depends on factors such as project size, complexity, industry, and organizational culture. Project managers often customize or combine methodologies to best fit the unique requirements of their projects.

Project management methodologies are often supported and implemented using various tools to enhance efficiency, collaboration, and communication throughout the project lifecycle. Here are some commonly used tools associated with project management methodologies:

1. Project Management Software

Tools like Microsoft Project, Asana, Jira, Trello, and Monday.com provide features for project planning, scheduling, task assignment, and progress tracking.

2. Version Control Systems

Git, SVN (Subversion), and Mercurial help manage changes to source code and documentation, ensuring version control and collaboration in software development projects.

3. Communication and Collaboration Tools

Slack, Microsoft Teams, and Discord facilitate real-time communication, file sharing, and collaboration among team members, supporting Agile and remote work environments.

4. Gantt Charts

Tools like GanttPRO and SmartDraw help create visual representations of project timelines, tasks, and dependencies, commonly used in Waterfall and traditional project management methodologies.

5. Kanban Boards

Trello, KanbanFlow, and LeanKit enable teams to visualize work and optimize workflow, particularly in Agile and Lean methodologies.

6. Scrum Tools

Jira, VersionOne, and Targetprocess support the Scrum framework with features for sprint planning, backlog management, and burndown charts.

7. Resource Management Tools

Workfront, Mavenlink, and TeamGantt assist in resource allocation, workload tracking, and managing team capacity in project management.

8. Risk Management Tools

RiskWatch, RiskyProject, and ProjectManager.com help identify, assess, and manage risks throughout the project lifecycle.

9. Collaborative Document Management

Tools like SharePoint, Google Workspace, and Dropbox Business enable teams to collaborate on documents, share project-related files, and ensure version control.

10. Continuous Integration and Deployment (CI/CD) Tools

Jenkins, Travis CI, and GitLab CI/CD automate integration code changes process and deploying software, commonly used in Agile and DevOps methodologies.

11. Time Tracking and Timesheet Tools

Harvest, Toggl, and Clockify assist in tracking project-related activities, allowing for accurate time management and resource allocation.

12. Customer Relationship Management (CRM) Tools

Salesforce, HubSpot, and Zoho CRM support customer-centric projects. That helps teams manage client interactions, feedback, and requirements.

Project managers and teams should carefully select tools that align with their chosen methodologies and project requirements. Integrating these tools can significantly improve project management efficiency and contribute to successful project outcomes.

Project management methodologies involve various techniques to plan, execute, and control projects effectively. Here are some commonly used techniques associated with project management methodologies:

1. Work Breakdown Structure (WBS)

Break a project into smaller, manageable tasks and create a hierarchical structure to define clearly the scope and deliverables.

2. PERT (Program Evaluation and Review Technique) and CPM (Critical Path Method)

Techniques for scheduling and managing tasks by identifying critical paths and dependencies and estimating project duration.

2. SWOT Analysis

Evaluate the project's Strengths, Weaknesses, Opportunities, and Threats to make informed decisions and develop effective strategies.

3. Risk Management

Identify, assess, mitigate, and monitor risks throughout the project lifecycle to minimize potential negative impacts.

4. Stakeholder Analysis

Identify and analyze stakeholders to understand their interests, influence, and expectations and ensure effective communication and engagement.

5. PERT Charts (Program Evaluation and Review Technique)

Graphical representations of project tasks and their dependencies, helping visualize the project schedule and critical path.

6. Scrum Meetings

Daily Standups, Sprint Planning, Sprint Review, and Sprint Retrospective are regular Scrum meetings that facilitate communication and collaboration in Agile projects.

7. Earned Value Management (EVM)

Analyze project performance by measuring the planned value, earned value, and actual cost to assess progress and forecast future performance.

8. Quality Management

Implement techniques such as quality audits, inspections, and control charts to ensure project deliverables meet predefined quality standards.

9. Mind Mapping

Visualize project ideas, requirements, and tasks using mind maps to stimulate creative thinking and organize information in a structured way.

10. Critical Chain Method

Identify and manage resource dependencies to optimize project schedules and improve overall performance.

11. Prototyping

Creating a working model or prototype of a product or system to gather feedback early in the development process is common in Agile and iterative methodologies.

12. Benchmarking

Compare project performance metrics and processes against industry standards or best practices to identify areas for improvement.

13. Dependency Mapping

Identify and visualize dependencies between different tasks or project activities to understand their interrelationships and potential impacts.

14. Agile Estimation Techniques

Use techniques like Planning Poker, Relative Sizing, and Story Points to estimate the effort required for Agile project tasks.

15. Change Management

Implement strategies and techniques to manage and communicate changes effectively, ensuring minimal disruptions to project progress.

16. Communication Plans

Developing plans outlines how project information will be communicated to stakeholders, ensuring clear and consistent communication.

These techniques are often applied based on the specific requirements, characteristics, and principles of the chosen project management methodology. Project managers may tailor and combine these techniques to suit the needs of their projects.

Choosing a suitable project management methodology is crucial for the success of a project. The decision should be based on the project's characteristics, team dynamics, organizational culture, and the nature of the work to be performed. Here is a step-by-step guide on how to choose a project management methodology:

1. Understand Project Requirements

Clearly define the project scope, objectives, and deliverables. Consider the size, complexity, and nature of the project work.

2. Assess Team Skills and Experience

Evaluate the skills and experience of the project team. Consider their familiarity with different methodologies and their adaptability to new approaches.

3. Consider Project Flexibility

Assess the level of flexibility required throughout the project. Some projects may benefit from a more adaptive and iterative approach, while others may require a more structured and sequential process.

4. Examine Project Constraints

Identify any constraints such as budget limitations, time constraints, regulatory requirements, or client preferences that may influence the choice of methodology.

5. Evaluate Organizational Culture

Consider the existing organizational culture and whether it aligns with the principles of certain project management methodologies. Some organizations may prefer traditional, plan-driven approaches, while others may be more receptive to Agile or iterative methods.

6. Define Stakeholder Involvement

Determine the level of involvement and collaboration required from project stakeholders. Some methodologies, like Agile, emphasize continuous stakeholder engagement and feedback.

7. Analyze Project Risks

Evaluate the potential risks associated with the project. Some methodologies, such as Agile, are well-suited for projects with high uncertainty and evolving requirements.

8. Review Industry Standards

Consider industry standards and best practices. Certain industries or project types may have specific guidelines or regulations that align with particular methodologies.

9. Explore Hybrid Approaches

Assess the possibility of combining elements from different methodologies to create a hybrid approach tailored to the project's specific needs.

10. Pilot or Prototype

If feasible, consider running a pilot or prototype using a small-scale version of the project to test how well a methodology fits the team and project requirements.

11. Consult with Stakeholders

Seek input from key stakeholders, including team members, clients, and sponsors. Understand their preferences, expectations, and concerns regarding project management approaches.

12. Training and Transition Plan

Evaluate the readiness of the team to adopt a new methodology. Plan for necessary training and establish a transition plan to smoothly implement the chosen methodology.

13. Continuous Improvement

Be open to evaluating and adjusting the chosen methodology throughout the project. Continuous improvement is essential to address evolving project needs and improve overall project management processes.

Elevate your project management skills with Bakkah Learning's expert-led courses. From PMP to Prince2, Six Sigma to Agile, we offer tailored programs to suit your career goals. With interactive learning, flexible access, and certification preparation, we're your partner for professional growth. Start your journey to mastery today with Bakkah Learning!

Here are some Project Management Courses :

• Certified Associate in Project Management CAPM Course
• PMI-ACP® certification
• PgMP certification
• PMI Scheduling Professional - PMI-SP certification

Risk Management Courses And Certifications:

• Risk Management Professional - PMI-RMP Course
• MoR Certification and course

PRINCE2 Courses

• PRINCE2 Certification
• PRINCE2 Agile.

Project Management Tools:

• Primavera P6 Course
• MSP Course - Managing Successful Programmes
• Microsoft Project training course  

Portfolio Management

• P3O Foundation certification
• Management of Portfolios MoP
• The Portfolio Management Professional – PfMP certificate
• Lean Six Sigma Yellow Belt Course
• Lean Six Sigma Green Belt Course
• Lean Six Sigma Black Belt Course

Ultimately, the choice of a project management methodology should be a thoughtful and informed decision that aligns with the unique characteristics of the project and the organization. Regularly reassess the chosen methodology to ensure its continued effectiveness and make adjustments as needed.

Related Courses

Our learning programs are delivered through a tested and professionally designed methodology.

3,737.5 SAR

Live Online

5,621.2 SAR

6,152.5 SAR

Exam is included

Your experience on this site will be improved by allowing cookies.

Added to Cart

{{ convertjson(lastcartitem.course.title) }}, features with this course, total with vat, {{ parsefloat(totalfeatures(lastcartitem)) }} {{currency}}.

Project Management Approaches and Methodologies

by Cate Curry | May 5, 2021 | Project Management | 0 comments

As a project manager , selecting the right project management approach and methodology is an important step you’ll need to take before starting work on a project. That’s because using the appropriate approach and methodology can make a major difference in the flow of your project and its successful completion.

• What is a Project Management Approach?

What Are Popular Project Management Approaches?

How to select the right approach for your project, a hybrid approach, what are common project management methodologies, what is a project management approach.

A project management approach defines the overall mindset you have for how to manage the project. Should you plan it traditionally, meaning as completely as possible before you execute, or should you plan and execute the project incrementally? Your project management approach falls along a continuum between plan-based (traditional), and adaptive (incremental). On the other hand, there are many methodologies to choose from. While this might feel overwhelming at first, the nice thing is you can select an approach that best suits each project, and that will help you know what methods to choose. After all, every project is unique, so even though a an approach and methodology might work for one project, it might not for another.

As mentioned, you can use different project management approaches to ensure every project you lead will be a success. To simplify things a bit, we’ve put together overviews of  the most popular types.

1. Agile Project Management 

The great thing about taking an agile approach to project management is it provides you with plenty of flexibility. You can change the way you do things as you go to adjust to change, and still keep your project on track.

Rather than following a strict, linear method, this adaptable and collaborative approach makes it easier to implement changes when needed. Therefore, your team may make changes as new learning about the needs of the project requires.

This approach can be helpful if you anticipate a project will need a lot of changes before completion. It’s also beneficial if your stakeholders want to give you frequent feedback as the project progresses.

Pro tip: When you’re ready to learn about how to apply agile principles and methods, RMC is here to help. You can enroll in courses to learn about agile , and we offer exam prep courses that will prepare you to become an Agile Certified Practitioner .

2. Waterfall Project Management 

Unlike the agile methodology, waterfall (or traditional project management) provides a more linear,  approach that is less flexible once planning is completed. Basically, your team progresses from one phase to the other as they’re completed.

With this methodology, you rely on more detailed requirements as you move from the start of a project to its end. However, you don’t have the flexibility to make changes after your team starts working without carefully vetting them. For this reason, it’s a good choice when you know how a project needs to go and what the outcome should be.

The stages in this methodology include requirements and analysis, along with design and construction, testing, deployment, and transition to operations. So, if you want to run a project that’s carefully planned with a schedule your team can adhere to, and there’s a clear goal that can be planned in detail with stakeholders , the waterfall method can be a suitable option.

There are pros and cons associated with each project management approach.  It’s wise to weigh your options and select the method that will be most beneficial to you, your team, and your stakeholders.

A few things to consider as you think about which approach to use:

• The number of people on your team, and how much guidance they require
• If a project allows for flexible changes and risks
• The level of involvement your stakeholders will have
• The amount of time you have to complete the project
• The project’s budget, and if it’s fixed or flexible

Sometimes your project calls for a blended plan driven and agile approach. This technique allows you to select elements of from both methodologies to get the project done.  For example, you use Agile sprints because the scope of your project might not be well defined at the outset of your project.  You create a general project charter to gain approval, which is a plan driven technique. 

Therefore, this hybrid approach takes the best of two methodologies and allows you to apply the most appropriate aspects of both.  If you’re interested in how to build the most effective hybrid approach for your project, consider RMC’s Hybrid Agile eLearning Course to guide you through the process.

Once you get to know the various methodologies available, and you begin to try them out in the real world, you’ll become confident in your ability to choose the right one for every project.

Popular project management methods include:

• Scrum – An agile methodology characterized by short, fixed production cycles (sprints) with specific goals, that works well with small, skillful and disciplined teams, and uses short, focused meetings.
• Extreme programming (XP) – A type of agile methodology that’s focused on collaboration.
• Critical path method – A method that uses a work breakdown structure to map out milestones, commonly used in traditional approaches.

Since agile is considered an instance of Lean thinking, these practices are often integrated into many agile methodologies:

• Lean – A method of optimizing the way your team works by reducing waste.
• Kanban – An agile method that uses a visual representation of the phases and steps that need to be completed throughout a project.

Once you get to know the various approaches and  methodologies available, and you begin to try them out in the real world, you’ll become confident in your ability to choose the right one for every project.  

Related posts:

• Recent Posts

• The PMP Exam 2023 - October 10, 2023
• CAPM Exam Format and Content - May 17, 2023
• Are You Ready for the PMP Exam? - May 9, 2023

Submit a Comment Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Popular Posts

Peterson’s LLC Successfully Completes Acquisition of RMC Learning Solutions

All New PMP Exam Prep Audiobook-11th Edition

The PMP Exam 2023

Scope Management for Agile, Hybrid or Predictive

CAPM Exam Format and Content

General Info

• RMC Guarantee
• PMP® Exam Changes
• CAPM Exam Changes
• PMI Talent Triangle®
• Class Policies
• Privacy Policy
• Terms of Use
• Project Management
• Business Analysis
• PMI-PBA® Prep
• PMI-ACP® Prep
• Fundamentals
• PDUs & Skills
• Refer a Friend
• Rita’s Process Chart Game

Project Management Plan: Samples, Examples & Free Template

Learn how to create a project management plan that actually works and ensures you get your project over the line on time and on budget, with samples and examples

Table of Contents

What is a project management plan, what is a project management plan used for, what are the main elements of a project plan, how to write a project management plan, sample project management plan outline, using our project management plan template to build your project plan, project management plan: faq's.

A project management plan is a comprehensive document that outlines how a project will be executed, monitored, controlled and closed. For project managers and their teams, it's the ultimate toolkit for achieving their objectives while managing day-to-day pressures such as time, cost, scope, resourcing and risk. This guide outlines what a project management plan is used for, why it's important , and offers a step-by-step guide on how to make one that actually works.

Your project plan document is where you go deep on the ins, outs, overs, and unders of your project. It's where you break this vision down into the day-to-day execution of your project, covering everything you need to do to reach your project goals.

A detailed project plan will plot out everything from timelines to budget, resourcing to deliverables, and more, giving you a blueprint of what needs to be done (and when) that you can use to guide — and assess — your project.

The key components of a project management plan are:

Project Objectives

Scope Statement

Schedule Management

Cost Management

Resource Management

Communication Plan

Stakeholder Management

Procurement Management

Closure Criteria

Project Organization

Ready to get down to business? Here are 5 key things you need to do when writing a project plan.

1. Identify the baselines for your project

Before you begin writing a project plan, you need to make sure you have the basics down. Start by identifying the baselines for the project’s scope, schedule and cost, as the rest of your project planning will need to fit in around those constraints.

As mentioned above, these baselines should already be roughly outlined in your project charter — but here’s where you really start to map them out and create accurate estimates. And the more detailed, the better, because these are what you’ll be using for comparison to measure how your project performs.

2. Identify your project dependencies

Or in other words, ask yourself: what needs to happen before this other thing can happen? Identifying your project dependencies at the outset of your project means you can plan your timelines more efficiently, spot potential blockers, and ensure that you avoid unnecessary delays.

3. Identify project stakeholders

You’ll already have done the groundwork for this in your stakeholder analysis, but as you flesh out your project management plan and think through the phases of your project in more detail, you’ll likely start to find more project stakeholders at each phase.

Now is also a good time to go deeper on which stakeholders need to be informed and involved at which stages, for a more comprehensive stakeholder management plan you can use at each phase of your project.

4. Identify project milestones

What are the key markers of your project’s progress? It can be a concrete deliverable, the end of a phase in a stage-gate process — whatever milestones make sense to you, breaking your project down into manageable chunks, each with a defined goal, helps to keep the team motivated, allows you to celebrate each achievement, and signposts how the overall progress is coming along.  Learn more about using Milestones here .

5. Identify who’s responsible for what

Once you start to get a big-picture understanding of the work that’s needed and the resources you have to complete it, you can start deciding who should do what. Giving each item an owner is essential to getting things done. No more “oh, was I supposed to do that?” — once you identify who’s responsible for what, you can ensure accountability and transparency.

The 5 Stages of Team Development

All teams develop according to some natural patterns and using that knowledge, you can offer some guidance to build the kind of team that communicates well and finds better ways to collaborate and achieve the goals you’ve established. Here’s what you need to know.

Now let's go through a sample project plan. In the below example, we highlight the main sections of the plan and what needs to be included in each one to set your project up for success.

Section 1: Executive summary

The executive summary offers a concise overview of the entire project. It includes key highlights such as the project's purpose, objectives, scope, timeline, budget, and major stakeholders. It's often the first section stakeholders read to get a high-level understanding of the project.

Section 2: Project introduction

This section sets the stage by providing context and background information about the project. It explains why the project is being undertaken and introduces the main objectives and scope of the project.

Section 3: Project objectives

Here, the project's specific goals and objectives are outlined in detail. Objectives should be SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) to provide clarity and guidance.

Section 4: Project scope

The scope section defines what is included and excluded from the project. It helps prevent scope creep by establishing clear boundaries and also mentions any assumptions and constraints that may affect the project.

Section 5: Schedule management

This section details the project's timeline, including milestones and deadlines. It breaks down the project into tasks and identifies task dependencies. Often, visual representations like Gantt charts are used for clarity.

Section 6: Cost management

Here, the project budget is presented, including cost estimates for various project components. It may also outline cost control measures to ensure the project stays within budget.

Section 7: Quality management

This section focuses on the quality standards and objectives for the project. It describes quality control and assurance processes, as well as any inspection and testing procedures that will be implemented.

Project management template

Save time on setup without sacrificing attention to detail. With our project management template, you can quickly create project management plans that help you complete your project on time and on budget.

Section 8: Resource management

In this section, the project team is introduced, and roles and responsibilities are defined. It addresses resource allocation, scheduling, and, if applicable, procurement needs.

Section 9: Risk management

The risk management section identifies potential risks and uncertainties that could impact the project. It discusses risk assessment, prioritization, and mitigation strategies to reduce the impact of these risks.

Section 10: Communication plan

The communication plan outlines how project information will be shared with stakeholders and team members. It specifies communication methods, frequency, and reporting channels to ensure effective communication throughout the project.

Section 11: Stakeholder management

This section lists project stakeholders and analyzes their interests, influence, and expectations. It also outlines strategies for engaging and managing these stakeholders to ensure their needs are addressed.

Section 12: Procurement management

If procurement of goods or services is involved, this section explains the procurement strategy, vendor selection criteria, and how contracts will be managed.

Section 13: Change management

Change management procedures are detailed here, including how changes to the project scope, schedule, or other aspects will be requested, evaluated, approved, and communicated.

Section 14: Closure criteria

Criteria for determining when the project is complete and ready for closure are specified in this section. It may also include plans for project handover and post-project evaluation.

Section 15: Project organization

This section describes the project team's structure, roles, and responsibilities, ensuring everyone understands their positions and reporting lines. It may also mention external stakeholders and their roles if applicable.

Once you’ve documented your project management plan, bring it to life with a project management tool that will help you to stay on track, keep your team accountable, and promote transparency.

Here are 3 ways you can use Teamwork.com to supercharge your project management plan.

Add your supporting documentation to Teamwork Spaces

Use the Teamwork.com and Teamwork Spaces integration to link a project in Teamwork.com with a space in Teamwork Spaces, so your important project documents are only ever a click away.

Some documents you might want to add in addition to your project charter and project management plan include:

Scoping documents

Risk assessments

Change management plans

SOPs for important project processes

List of stakeholders and their roles

Outline of approval processes

Communications management plan

Any other best practices documentation or supporting info as necessary

You can even embed task lists into your pages and mark tasks as complete right from Teamwork Spaces, so you can keep work flowing without even needing to switch tabs.

Start adding your Milestones

Break down your work into Milestones and task lists that are going to help you reach them. With Teamwork.com, you can assign an owner to each Milestone, map out your Milestone due dates and see them represented in the project calendar, and even get a full change history for milestones so you can track any edits.

Visualize your task dependencies with a Gantt chart

Gantt chart-style views are a useful way to get a visual representation of your tasks and their dependencies, allowing for better scheduling and resourcing. In Teamwork.com, you can drag and drop to quickly rearrange your project schedule , without throwing everything out of order or straying off-plan.

Remember: software should support the way you work, not dictate it. So regardless of methodology or team type, create a project plan that works for you and your team — and find a tool that helps you put it into action.

Use our project plan template

Now that you know how to create a project management plan that actually works, you’re ready to implement using our team management software . To help you get up and running quickly, we’ve created a ready to use project plan template . Our project template will help you quickly create project plans that ensure all of your projects are completed on time and on budget

What is a project management plan template?

A project management plan template is a pre-designed framework that provides a structured format for creating a project management plan. It serves as a starting point for project managers and teams to develop their specific project plans, saving time and ensuring that key project management components are properly addressed.

How can a template help you build a great project management plan?

A template can help you build a great project management plan by saving time, ensuring comprehensive coverage of project management aspects, and incorporating industry best practices and visual aids for clarity. They also support collaboration, version control, and customization to fit the unique needs of each project, making them a valuable tool for project managers in achieving successful project outcomes.

What is the main purpose of a project management plan?

The main purpose of a project management plan is to provide a comprehensive and structured roadmap for successfully executing, monitoring, controlling, and closing a project. It serves as a central document that outlines project objectives, scope, schedule, budget, quality standards, resource allocation, risk management strategies, and communication approaches.

What tools do I need to help manage a project plan?

To effectively manage a project plan, you'll need a set of tools and software that cover various aspects of project management. These include project management software, communication and collaboration platforms, file and document management solutions, time and task tracking apps, and budgeting and financial management tools.

What steps are involved in the project planning process?

The steps involved in the project planning process include defining specific project objectives and scope, identifying deliverables and key milestones, budgets, risk assessment and quality control measures. It should also include a communication plan and stakeholder engagement strategies.

You may also like...

Get started with Teamwork.com

Start working together beautifully. See how Teamwork.com can help your team with our 30-day free trial.

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?

5 things you need to know before creating a project management plan, what should a project management plan include, how do you write a project plan, project plan best practices, project management plan templates and examples, 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 .

The importance of a project management plan

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

To write a successful project plan, follow these 5 steps below to create an effective project 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 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 . 

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

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 !

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

• Contact sales

Start free trial

How to Write a Project Proposal (Examples & Template Included)

Table of Contents

What is a project proposal, types of project proposals, project proposal vs. project charter, project proposal vs. business case, project proposal vs. project plan, project proposal outline, how to write a project proposal, project proposal example, project proposal tips.

• ProjectManager & Project Proposals

A project proposal is a project management document that’s used to define the objectives and requirements of a project. It helps organizations and external project stakeholders agree on an initial project planning framework.

The main purpose of a project proposal is to get buy-in from decision-makers. That’s why a project proposal outlines your project’s core value proposition; it sells value to both internal and external project stakeholders. The intent of the proposal is to grab the attention of stakeholders and project sponsors. Then, the next step is getting them excited about the project summary.

Getting into the heads of the audience for which you’re writing the project proposal is vital: you need to think like the project’s stakeholders to deliver a proposal that meets their needs.

We’ve created a free project proposal template for Word to help structure documents, so you don’t have to remember the process each time.

Get your free

Project Proposal Template

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

In terms of types of project proposals, you can have one that’s formally solicited, informally solicited or a combination. There can also be renewal and supplemental proposals. Here’s a brief description of each of them.

• Solicited project proposal: This is sent as a response to a request for proposal (RFP) . Here, you’ll need to adhere to the RFP guidelines of the project owner.
• Unsolicited project proposal: You can send project proposals without having received a request for a proposal. This can happen in open bids for construction projects , where a project owner receives unsolicited project proposals from many contractors.
• Informal project proposal: This type of project proposal is created when a client asks for an informal proposal without an RFP.
• Renewal project proposal: You can use a renewal project proposal when you’re reaching out to past customers. The advantage is that you can highlight past positive results and future benefits.
• Continuation project proposal: A continuation project proposal is sent to investors and stakeholders to communicate project progress.
• Supplemental project proposal: This proposal is sent to investors to ask for additional resources during the project execution phase.

A project proposal is a detailed project document that’s used to convince the project sponsor that the project being proposed is worth the time, money and effort to deliver it. This is done by showing how the project will address a business problem or opportunity. It also outlines the work that will be done and how it will be done.

A project charter can seem like the same thing as a project proposal as it also defines the project in a document. It identifies the project objectives, scope, goals, stakeholders and team. But it’s done after the project has been agreed upon by all stakeholders and the project has been accepted. The project charter authorizes the project and documents its requirements to meet stakeholders’ needs.

A business case is used to explain why the proposed project is justified. It shows that the project is worth the investment of time and money. It’s more commonly used in larger companies in the decision-making process when prioritizing one project over another.

The business case answers the questions: what is the project, why should it be taken up, who will be involved and how much will it cost? It’s therefore related to a project proposal, but the project proposal comes before the business case and is usually part of the larger proposal.

Again, the project proposal and the project plan in this case are very similar documents. It’s understandable that there would be some confusion between these two project terms. They both show how the project will be run and what the results will be. However, they’re not the same.

The project proposal is a document that aims to get a project approved and funded. It’s used to convince stakeholders of the viability of the project and their investment. The project plan, on the other hand, is made during the planning phase of the project, once it’s been approved. It’s a detailed outline of how the project will be implemented, including schedule, budget, resources and more.

All the elements in the above project proposal outline are present in our template. This free project proposal template for Word will provide you with everything you need to write an excellent project proposal. It will help you with the executive summary, project process, deliverables, costs—even terms and conditions. Download your free template today.

There are several key operational and strategic questions to consider, including:

• Executive summary: This is the elevator pitch that outlines the project being proposed and why it makes business sense. While it also touches on the information that’ll follow in the project proposal, the executive summary should be brief and to the point.
• Project background: This is another short part of the proposal, usually only one page, which explains the problem you’ll solve or the opportunity you’re taking advantage of with the proposed project. Also, provide a short history of the business to put the company in context to the project and why it’s a good fit.
• Project vision & success criteria: State the goal of the project and how it aligns with the goals of the company. Be specific. Also, note the metrics used to measure the success of the project.
• Potential risks and mitigation strategies: There are always risks. Detail them here and what strategies you’ll employ to mitigate any negative impact as well as take advantage of any positive risk.
• Project scope & deliverables: Define the project scope, which is all the work that has to be done and how it will be done. Also, detail the various deliverables that the project will have.
• Set SMART goals: When setting goals, be SMART. That’s an acronym for specific, measurable, achievable, relevant and time-bound. All your goals would be defined by those five things.
• Project approach: Define the approach you’ll use for the contract. There are several different types of contracts used in construction , for example, such as lump sum, cost plus, time and materials, etc. This is also a good place to describe the delivery method you’ll use.
• Expected benefits: Outline the benefits that will come from the successful completion of the project.
• Project resource requirements: List the resources, such as labor, materials, equipment, etc., that you’ll need to execute the project if approved.
• Project costs & budget: Detail all the costs, including resources, that’ll be required to complete the project and set up a budget to show how those costs will be spent over the course of the project.
• Project timeline: Lay out the project timeline , which shows the project from start to finish, including the duration of each phase and the tasks within it, milestones, etc.

In addition to these elements, it’s advisable to use a cover letter, which is a one-page document that helps you introduce your project proposal and grab the attention of potential clients and stakeholders.

To make the best proposal possible, you’ll want to be thorough and hit on all the points we’ve listed above. Here’s a step-by-step guide to writing a persuasive priority proposal.

1. Write an Executive Summary

The executive summary provides a quick overview of the main elements of your project proposal, such as your project background, project objectives and project deliverables, among other things. The goal is to capture the attention of your audience and get them excited about the project you’re proposing. It’s essentially the “elevator pitch” for the project life cycle. It should be short and to the point.

The executive summary should be descriptive and paint a picture of what project success looks like for the client. Most importantly, it should motivate the project client; after all, the goal is getting them to sign on the dotted line to get the project moving!

2. Provide a Project Background

The project background is a one-page section of your project proposal that explains the problem that your project will solve. You should explain when this issue started, its current state and how your project will be the ideal solution.

• Historic data: The history section outlines previously successful projects and those that could have run more smoothly. By doing so, this section establishes precedents and how the next project can be more effective using information from previous projects.
• Solution: The solution section addresses how your project will solve the client’s problem. Accordingly, this section includes any project management techniques , skills and procedures your team will use to work efficiently.

3. Establish a Project Vision & Success Criteria

You’ll need to define your project vision. This is best done with a vision statement, which acts as the north star for your project. It’s not specific as much as it’s a way to describe the impact your company plans to make with the project.

It’s also important to set up success criteria to show that the project is in fact doing what it’s proposed to do. Three obvious project success criteria are the triple constraint of cost, scope and time. But you’ll need to set up a way to measure these metrics and respond to them if they’re not meeting your plan.

4. Identify Potential Risks and Mitigation Strategies

To reduce the impact of risk in your project, you need to identify what those risks might be and develop a plan to mitigate them . List all the risks, prioritize them, describe what you’ll do to mitigate or take advantage of them and who on the team is responsible for keeping an eye out for them and resolving them.

5. Define Your Project Scope and Project Deliverables

The project scope refers to all the work that’ll be executed. It defines the work items, work packages and deliverables that’ll be delivered during the execution phase of your project life cycle. It’s important to use a work breakdown structure (WBS) to define your tasks and subtasks and prioritize them.

6. Set SMART Goals for Your Project Proposal

The best mindset when developing goals and objectives for your project proposal is to use the SMART system :

• Specific – Make sure your goals and objectives are clear, concise and specific to the task at hand.
• Measurable – Ensure your goals and objectives are measurable so it’s obvious to see when things are on track and going well, and conversely, when things are off track and issues need to be addressed. Measurable goals make it easy to develop the milestones you’ll use to track the progress of the project and identify a reasonable date for completion and/or closure.
• Attainable – It’s important every project has a “reach” goal. Hitting this goal would mean an outstanding project that extends above and beyond expectations. However, it’s important that the project’s core goal is attainable, so morale stays high and the job gets done with time and resources to spare.
• Relevant – Make sure all of your goals are directly relevant to the project and address the scope within which you’re working.
• Time-Based – Timelines and specific dates should be at the core of all goals and objectives. This helps keep the project on track and ensures all project team members can manage the work that’s ahead of them.

7. Explain What’s Your Project Approach

Your project approach defines the project management methodology , tools and governance for your project. In simple terms, it allows project managers to explain to stakeholders how the project will be planned, executed and controlled successfully.

8. Outline The Expected Benefits of Your Project Proposal

If you want to convince internal stakeholders and external investors, you’ll need to show them the financial benefits that your project could bring to their organization. You can use cost-benefit analysis and projected financial statements to demonstrate why your project is profitable.

9. Identify Project Resource Requirements

Project resources are critical for the execution of your project. The project proposal briefly describes what resources are needed and how they’ll be used. Later, during the planning phase, you’ll need to create a resource management plan that’ll be an important element of your project plan. Project requirements are the items, materials and resources needed for the project. This section should cover both internal and external needs.

10. Estimate Project Costs and Project Budget

All the resources that you’ll need for your project have a price tag. That’s why you need to estimate those costs and create a project budget . The project budget needs to cover all your project expenses, and as a project manager, you’ll need to make sure that you adhere to the budget.

11. Define a Project Timeline

Once you’ve defined your project scope, you’ll need to estimate the duration of each task to create a project timeline. Later during the project planning phase , you’ll need to create a schedule baseline, which estimates the total length of your project. Once the project starts, you’ll compare your actual project schedule to the schedule baseline to monitor progress.

Now let’s explore some project proposal examples to get a better understanding of how a project proposal would work in the real world. For this example, let’s imagine a city that’s about to build a rapid transit system. The city government has the funds to invest but lacks the technical expertise and resources that are needed to build it, so it issues a request for proposal (RFP) document and sends it to potential builders.

Then, the construction companies that are interested in executing this rapid transit project will prepare a project proposal for the city government. Here are some of the key elements they should include.

• Project background: The construction firm will provide an explanation of the challenges that the project presents from a technical perspective, along with historical data from similar projects that have been completed successfully by the company.
• Project vision & success criteria: Write a vision statement and explain how you’ll track the triple constraint to ensure the successful delivery of the project.
• Potential risks and mitigation strategies: List all risks and how they’ll be mitigated, and be sure to prioritize them.
• Project scope & deliverables: The work that’ll be done is outlined in the scope, including all the deliverables that’ll be completed over the life cycle of the project.
• Set SMART goals: Use the SMART technique to define your project goals by whether they’re specific, measurable, achievable, relevant and time-bound.
• Project approach: Define the methodology that the project manager will employ to manage the project. Also, figure out what type of contract will be used to define the project.
• Expected benefits: Show how the project will deliver advantages to the company and define what these benefits are in a quantifiable way.
• Project resource requirements: List all the resources, such as labor, materials, equipment, etc., needed to execute the project.
• Project costs & budget: Estimate the cost of the project and lay that out in a project budget that covers everything from start to finish.
• Project timeline: Outline the project schedule, including phases, milestones and task duration on a visual timeline.

Whatever project proposal you’re working on, there are a few tips that apply as best practices for all. While above we suggested a project proposal template that would have a table of contents, meaning it would be many pages long, the best-case scenario is keeping the proposal to one or two pages max. Remember, you’re trying to win over stakeholders, not bore them.

Speaking of project stakeholders , do the research. You want to address the right ones. There’s no point in doing all the work necessary to write a great proposal only to have it directed to the wrong target audience. Whoever is going to read it, though, should be able to comprehend the proposal. Keep the language simple and direct.

When it comes to writing, get a professional. Even a business document like a project proposal, business case or executive summary will suffer if it’s poorly constructed or has typos. If you don’t want to hire a professional business writer, make sure you get someone on your project team to copy, edit and proof the document. The more eyes on it, the less likely mistakes will make it to the final edition.

While you want to keep the proposal short and sweet, it helps to sweeten the pot by adding customer testimonials to the attachments. Nothing sells a project plan better than a customer base looking for your product or service.

ProjectManager & Project Proposals

ProjectManager allows you to plan proposals within our software. You can update tasks for the project proposal to signify where things stand and what’s left to be done. The columns allow you to organize your proposal by section, creating a work breakdown structure (WBS) of sorts.

When building a project proposal, it’s vital to remember your target audience. Your audience includes those who are excited about the project, and see completion as a gain for their organization. Conversely, others in your audience will see the project as a pain and something to which they aren’t looking forward. To keep both parties satisfied, it’s essential to keep language factual and concise.

Our online kanban boards help you think through that language and collaborate on it effectively with other team members, if necessary. Each card shows the percentage completed so everyone in the project management team is aware of the work done and what’s left to be done.

As you can see from the kanban board above, work has begun on tasks such as product documentation and design. Tasks regarding stakeholder feedback, ideation, market research and more have been completed, and there’s a good start on the engineering drawings, 3D rendering, supply chain sourcing and translation services.

A PDF is then attached to the card, and everyone added to the task receives an email notifying them of the change. This same process can be used throughout the life-cycle of the project to keep the team updated, collaborating, and producing a first-class project proposal. In addition to kanban boards, you can also use other project management tools such as Gantt charts , project dashboards, task lists and project calendars to plan, schedule and track your projects.

Project proposals are just the first step in the project planning process. Once your project is approved, you’ll have to solidify the plan, allocate and manage resources, monitor the project, and finally hand in your deliverables. This process requires a flexible, dynamic and robust project management software package. ProjectManager is online project management software that helps all your team members collaborate and manage this process in real-time. Try our award-winning software with this free 30-day trial .

Deliver your projects on time and under budget

Start planning your projects.

THE PROJECT APPROACH

Managed by the Educators Institute at Duke School

ENGAGING CHILDREN'S MINDS

Building on natural curiosity to engage, problem-solve, and connect

Authentic Discovery

Problem-Solving

Extending beyond the classroom to each student's community

Shaping the next generation of problem-solvers

Natural Curiosity

Building on natural curiosity to enable interaction and connection

The Project Approach

Children have a strong disposition to explore and discover. The Project Approach builds on natural curiosity, enabling children to interact, question, connect, problem-solve, communicate, reflect, and more. This kind of authentic learning extends beyond the classroom to each student’s home, community, nation, and world. It essentially makes learning the stuff of real life and children active participants in and shapers of their worlds.

The Project Approach Study Guide

The study guide offers educators an overview of the Project Approach and guides them through the process of developing and implementing a project in the classroom. Readings provide both practical knowledge and a theoretical framework, while assignments offer a flexible, step-by-step approach that allows teachers to learn in the process of trying out their first (or second or third) project in the classroom.

The Guide is an adaptation of the online course as taught by Project Approach founder, Sylvia Chard. It is still a little like a course but designed for a teacher to study for him or herself.

Journal prompts with each of the seven sections offer opportunities for teachers to reflect on and refine their strategies, ideas, and practices. Establishing a regular journal writing routine is a fundamental part of project-based teaching as this is a process that evolves with reflection and experience.

• NAEYC Login
• Member Profile
• Hello Community
• Accreditation Portal
• Online Learning
• Online Store

Popular Searches:   DAP ;  Coping with COVID-19 ;  E-books ;  Anti-Bias Education ;  Online Store

Project Approach

You are here

Most recent.

Powering Up: Interdisciplinary Project-Based Learning for Young Engaged Citizens

Authored by.

Rethinking Field Trips: Venturing Out to Foster Meaningful Learning

Exploring Nature Indoors with Observational Drawing and Scientific Thinking

What Are You Thinking? Scaffolding Thinking to Promote Learning

مشروع مركز القيادة: التخلص من التوتر المرافق للمنهاج الدراسي المستجد The Command Center Project: Resolving My Tensions with Emergent Curriculum

Reflecting on the Fish Tank: Using the Project Approach to Make Connections

Our Trip Down to the Bay: A Model of Experiential Learning

تطبيق نهج التعلم القائم على المشاريع في فصول الدمج: المحاولة الأولى لإحدى المعلمات لاستخدام التعلم القائم على المشاريع Implementing the Project Approach in an Inclusive Classroom: A Teacher’s First Attempt With Project-Based Learning (Voices)

Beyond Bouncing the Ball: Toddlers and Teachers Investigate Physics ما وراء طبطبة الكرة: المعلمات والأطفال الفطم يدرسون الفيزياء

14-Day Salad: Using Project-Based Learning to Grow Microgreens أربعة عشر يومًا لاستنبات نباتات السلطة: استخدام التعلم القائم على المشاريع لاستنبات نباتات المايكروغرين

New Year, New Use: Discarded Holiday Trees Transform the Playground

Metamorphosis: Life Cycle in a Box

Connecting our Nature Walks to the Classroom

The Making of an Art Museum: A Preschool Project

Cultivo de vegetales en 14 días: cómo usar el aprendizaje basado en proyectos para cultivar micro vegetales

14-day salad: using project-based learning to grow microgreens.

Full STEAM Ahead. Worm Fun! Children’s Interest Sparks Worm Study

Program Focus Interest Forums

What's in a Shadow?

¿qué hay en una sombra.

The Project Approach to Teaching and Learning

What is the Project Approach?

The Project Approach offers teachers a way to develop in-depth thinking while engaging the hearts and minds of young children. Teachers take a strong guidance role in the process while children study topics with purpose and flexibility. Project work presents many opportunities for young children’s ideas to be valued, their creativity to be encouraged, their interests to be nurtured, and for their learning needs to be met.

In early childhood, projects can be defined as open ended studies of everyday topics which are worthy of being included in an educational program. Projects emerge from the questions children raise and develop according to their particular interests. Rather than offering immediate answers to the questions children ask, teachers provide experiences through which children can discover the answers themselves through inquiry at field sites and interviewing experts. For example, if the children wonder what shoes are made of or how are they made, the teacher may arrange a field visit where the answer to these questions can be provided by an expert, in this case a shoe factory, the shoe repair man’s shop, or a shoe store. Children also consult secondary sources of information such as books and the internet in the classroom and with their parents at home.

Project investigations promote in-depth understanding and cover a wide range of relevant subtopics. For this reason projects usually take several weeks to complete—and sometimes much longer, depending on the age and interests of the children.

The Project Approach, then, is the method of teaching children through project investigations. Because project work follows an unpredictable path based on the interests of particular children, a flexible framework to support teachers has been developed. This framework makes the inquiry more manageable: it shapes the development of the area of investigation. Teachers guide children through a three phase process from the beginning of a project to its conclusion. You may find the Project Planning Journal helpful in understanding and implementing project work. It’s from the book Young Investigators: The Project Approach in the Early Years by Judy Harris Helm and Lilian G. Katz.

What is the Structure of the Project Approach?

Phase 1: In the beginning of a project, the teacher builds interest in the topic through encouraging the children to share relevant personal stories of experience. As the children represent their current understanding of the topic; the river, cars, or dogs, for example, the teacher assesses the children’s vocabulary, their individual interests, misconceptions or gaps in current knowledge, and helps them formulate questions which they can investigate.

Phase 2: As the inquiry begins in earnest, teachers enable the children go on field visits, interview adults who are experts, such as waiters, farmers, or nurses, for example, according to the topic of study. Children also look at books, internet sites, videos, and so on. As they learn more about the topic they use many forms of representation to illustrate what they have learned and to share new knowledge with their classmates.

Phase 3:  Finally, the teacher guides the conclusion of the study and helps the children review their achievements. The children share their work with parents, another class, or members of the local community who have helped them in the process of the investigation. This final phase of the work includes the assessment by teachers of what the children have learned through the project. All children will have learned basic facts about the topic. Some children will have learned more about certain aspects of the topic such as the role of the adults, or the steps or materials used in the manufacture of an important item. There will be times when one child may have achieved individual learning goals such as developing confidence in a particular personal strength or learning to collaborate effectively with other classmates.

​Sharing what they have learned with others helps the children to review their achievements.

What are the advantages of the Project Approach?

When teachers encourage children’s curiosity and help them to ask questions, the study of local everyday topics becomes interesting and relevant to them. Young children’s learning is energized as they become part of a community of investigators and share the findings of their inquiry. Children apply skills and knowledge in their study of buses, shoes, trees, or grocery stores. They learn about the value of reading, writing, and numbers in the life of the adults around them. In the context of the project the children become apprentices in the pursuit of knowledge alongside their teachers. Teachers take a responsive role in developing the project. They coordinate different interests and support small group and individual inquiries as these emerge. Teachers who use the project approach report that students show great interest and actively participate. They ask questions and follow up their own curiosity with investigations.

Along with the motivation it provides, project work also integrates all areas of learning and aspects of child development. It offers many chances to practice problem solving and critical thinking—skills that build language, math and scientific understanding. In fact, it helps children gain confidence in themselves and their abilities and develops in them the disposition to strive for understanding.

How does the Project Approach align with curriculum requirements and standards?

This type of learning differs considerably from the preplanned lessons of a published curriculum. While project work supports the curriculum standards identified for testing, teachers do not teach to the test through project work. The emphasis is on the context in which learning is intrinsically motivated and engaging to young children.

Through careful observation and skillful planning on the part of the teacher, curriculum goals can be integrated into project work. The teacher anticipates where a project may go, and includes elements of the required curriculum in her plans. For example, the curriculum goal of data collection and analysis can be incorporated into a project on cars, if children decide to count and record the kinds of cars they see. The teacher records her plan and project documentation provides evidence of learning.

In addition to the aspects of the curriculum which relate directly to the acquisition of skills and knowledge, project work offers interesting opportunities for children to apply and practice what they have learned in other parts of their daily program in school. Intrinsic motivation enables children to learn through projects in personally meaningful ways. Children who excel in certain academic areas learn to offer leadership to their peers. Children who experience difficulty in some areas frequently learn from skilled or knowledgeable peers more easily than from adults.

In classrooms where the Project Approach is well implemented, teachers and parents report that children show increased achievement and confidence in talking about what they know and can do.

Curriculum goals, such as data collection and analysis, can be naturally integrated into project work.

How does the Project Approach fit with other teaching strategies?

Project work can be incorporated into learning centers, as well as into a typical daily schedule. For example, circle time can be used to discuss a current investigation or books on the subject can be placed in the literacy area.

However, with all its advantages, most early childhood professionals would agree that project work alone does not cover all the learning experiences that should be included in the curriculum. Children learn through many different experiences in school. For young children these experiences include sensory exploration, various kinds of play activity, observation, and practice. They learn some things through direct instruction, some through small group work, some through repeated trials and persistence, and some through collaboration and lively discussion with their classmates.

The Project Approach offers children the flexibility to develop interests, to work hard at their strengths, to share expertise and make personal contributions to the work of the classroom. The use of open-ended learning centers in a classroom can make for easier differentiation by teachers in their instruction as they help children to self-assess and challenge themselves appropriately in the classroom context.

Open-ended learning centers complement project work by allowing children to reconstruct their experiences.

What are the challenges of implementing the Project Approach?

The principle challenge for teachers is to know the children well and to be able to guide them effectively in their inquiry. It requires dedication and creativity to take full advantage of individual strengths and interests, engage parental expertise (for interviews, access to field sites, etc.), and seek out resources. The key to a successful project is the teacher’s daily classroom assessment; it guides the work towards optimal learning opportunities in responsive environments for all children. These challenges demand that the teacher’s own creativity be engaged in crafting with the children the stories of their learning through projects.

As with any teaching approach or method, positive results are only evident when the teaching is done well. It is easier to set up learning centers with activities, worksheets, and boxes of props which are the same each year. It is easier to read the same fantasy literature and have the children play the parts of the characters in dramatic play year after year. In project work, teachers depend on rich communication with the children to determine their interests and prior levels of understanding. A project on ‘pets’ for instance, may focus on different subtopics from one year to the next as different groups of children and their parents show interests, expertise, or gaps in knowledge. One year the direction might be how to care for pets’ everyday needs, another year the focus might be around pet health and the work of the veterinarian, while yet another might be the work that animals can do for human beings, such as service dogs, leisure pursuits and exercise, or work with the elderly or young people with autism or other challenges. Teacher’s responsiveness to children challenges them always to bring fresh thinking to project work.

Another challenge for teachers is to plan the work so that there is a unity and cohesiveness to each project which all the children can appreciate. As various interests are developed teachers have to keep the communication focused on the value of each group’s contribution to the knowledge and understanding of the topic by all the children in their classes.

Yet, teachers wishing to help students develop a life-long love of learning and understand the interconnected relationship of all things will find there are unique advantages to project learning.

Beghetto, RA & Kaufman, JC (2013). Fundamentals of Creativity. Educational Leadership , Vol. 70, No. 5, pp. 10-15.

Chard, SC (2009) The Project Approach: Six Practical Guides for Teachers. These guides are available as .pdf files at the following web site: www.projectapproach.org

Katz LG & Chard, SC (2000) Engaging Children’s Minds: The Project Approach , Greenwood.

is Professor Emerita of Early Childhood Education at the University of Alberta, Canada. She has worked at the University since 1989; for seven years as director of the elementary education laboratory school. Dr. Chard has taught at various levels from preschool through high school in England, and completed her M.Ed. and Ph.D. at the University of Illinois. Dr. Chard has written extensively about the Project Approach, including the book Engaging Children's Minds: The Project Approach , which she co-authored with Lilian G. Katz. Dr. Chard maintains a website and blog The Project Approach and lectures around the world.

Let's Stay in Touch

Request a Free Catalog:

Sign up for our weekly blog

Understanding Assignments

What this handout is about.

The first step in any successful college writing venture is reading the assignment. While this sounds like a simple task, it can be a tough one. This handout will help you unravel your assignment and begin to craft an effective response. Much of the following advice will involve translating typical assignment terms and practices into meaningful clues to the type of writing your instructor expects. See our short video for more tips.

Basic beginnings

Regardless of the assignment, department, or instructor, adopting these two habits will serve you well :

• Read the assignment carefully as soon as you receive it. Do not put this task off—reading the assignment at the beginning will save you time, stress, and problems later. An assignment can look pretty straightforward at first, particularly if the instructor has provided lots of information. That does not mean it will not take time and effort to complete; you may even have to learn a new skill to complete the assignment.
• Ask the instructor about anything you do not understand. Do not hesitate to approach your instructor. Instructors would prefer to set you straight before you hand the paper in. That’s also when you will find their feedback most useful.

Assignment formats

Many assignments follow a basic format. Assignments often begin with an overview of the topic, include a central verb or verbs that describe the task, and offer some additional suggestions, questions, or prompts to get you started.

An Overview of Some Kind

The instructor might set the stage with some general discussion of the subject of the assignment, introduce the topic, or remind you of something pertinent that you have discussed in class. For example:

“Throughout history, gerbils have played a key role in politics,” or “In the last few weeks of class, we have focused on the evening wear of the housefly …”

The Task of the Assignment

Pay attention; this part tells you what to do when you write the paper. Look for the key verb or verbs in the sentence. Words like analyze, summarize, or compare direct you to think about your topic in a certain way. Also pay attention to words such as how, what, when, where, and why; these words guide your attention toward specific information. (See the section in this handout titled “Key Terms” for more information.)

“Analyze the effect that gerbils had on the Russian Revolution”, or “Suggest an interpretation of housefly undergarments that differs from Darwin’s.”

Additional Material to Think about

Here you will find some questions to use as springboards as you begin to think about the topic. Instructors usually include these questions as suggestions rather than requirements. Do not feel compelled to answer every question unless the instructor asks you to do so. Pay attention to the order of the questions. Sometimes they suggest the thinking process your instructor imagines you will need to follow to begin thinking about the topic.

“You may wish to consider the differing views held by Communist gerbils vs. Monarchist gerbils, or Can there be such a thing as ‘the housefly garment industry’ or is it just a home-based craft?”

These are the instructor’s comments about writing expectations:

“Be concise”, “Write effectively”, or “Argue furiously.”

Technical Details

These instructions usually indicate format rules or guidelines.

“Your paper must be typed in Palatino font on gray paper and must not exceed 600 pages. It is due on the anniversary of Mao Tse-tung’s death.”

The assignment’s parts may not appear in exactly this order, and each part may be very long or really short. Nonetheless, being aware of this standard pattern can help you understand what your instructor wants you to do.

Interpreting the assignment

Ask yourself a few basic questions as you read and jot down the answers on the assignment sheet:

Why did your instructor ask you to do this particular task?

Who is your audience.

• What kind of evidence do you need to support your ideas?

What kind of writing style is acceptable?

• What are the absolute rules of the paper?

Try to look at the question from the point of view of the instructor. Recognize that your instructor has a reason for giving you this assignment and for giving it to you at a particular point in the semester. In every assignment, the instructor has a challenge for you. This challenge could be anything from demonstrating an ability to think clearly to demonstrating an ability to use the library. See the assignment not as a vague suggestion of what to do but as an opportunity to show that you can handle the course material as directed. Paper assignments give you more than a topic to discuss—they ask you to do something with the topic. Keep reminding yourself of that. Be careful to avoid the other extreme as well: do not read more into the assignment than what is there.

Of course, your instructor has given you an assignment so that they will be able to assess your understanding of the course material and give you an appropriate grade. But there is more to it than that. Your instructor has tried to design a learning experience of some kind. Your instructor wants you to think about something in a particular way for a particular reason. If you read the course description at the beginning of your syllabus, review the assigned readings, and consider the assignment itself, you may begin to see the plan, purpose, or approach to the subject matter that your instructor has created for you. If you still aren’t sure of the assignment’s goals, try asking the instructor. For help with this, see our handout on getting feedback .

Given your instructor’s efforts, it helps to answer the question: What is my purpose in completing this assignment? Is it to gather research from a variety of outside sources and present a coherent picture? Is it to take material I have been learning in class and apply it to a new situation? Is it to prove a point one way or another? Key words from the assignment can help you figure this out. Look for key terms in the form of active verbs that tell you what to do.

Key Terms: Finding Those Active Verbs

Here are some common key words and definitions to help you think about assignment terms:

Information words Ask you to demonstrate what you know about the subject, such as who, what, when, where, how, and why.

• define —give the subject’s meaning (according to someone or something). Sometimes you have to give more than one view on the subject’s meaning
• describe —provide details about the subject by answering question words (such as who, what, when, where, how, and why); you might also give details related to the five senses (what you see, hear, feel, taste, and smell)
• explain —give reasons why or examples of how something happened
• illustrate —give descriptive examples of the subject and show how each is connected with the subject
• summarize —briefly list the important ideas you learned about the subject
• trace —outline how something has changed or developed from an earlier time to its current form
• research —gather material from outside sources about the subject, often with the implication or requirement that you will analyze what you have found

Relation words Ask you to demonstrate how things are connected.

• compare —show how two or more things are similar (and, sometimes, different)
• contrast —show how two or more things are dissimilar
• apply—use details that you’ve been given to demonstrate how an idea, theory, or concept works in a particular situation
• cause —show how one event or series of events made something else happen
• relate —show or describe the connections between things

Interpretation words Ask you to defend ideas of your own about the subject. Do not see these words as requesting opinion alone (unless the assignment specifically says so), but as requiring opinion that is supported by concrete evidence. Remember examples, principles, definitions, or concepts from class or research and use them in your interpretation.

• assess —summarize your opinion of the subject and measure it against something
• prove, justify —give reasons or examples to demonstrate how or why something is the truth
• evaluate, respond —state your opinion of the subject as good, bad, or some combination of the two, with examples and reasons
• support —give reasons or evidence for something you believe (be sure to state clearly what it is that you believe)
• synthesize —put two or more things together that have not been put together in class or in your readings before; do not just summarize one and then the other and say that they are similar or different—you must provide a reason for putting them together that runs all the way through the paper
• analyze —determine how individual parts create or relate to the whole, figure out how something works, what it might mean, or why it is important
• argue —take a side and defend it with evidence against the other side

More Clues to Your Purpose As you read the assignment, think about what the teacher does in class:

• What kinds of textbooks or coursepack did your instructor choose for the course—ones that provide background information, explain theories or perspectives, or argue a point of view?
• In lecture, does your instructor ask your opinion, try to prove their point of view, or use keywords that show up again in the assignment?
• What kinds of assignments are typical in this discipline? Social science classes often expect more research. Humanities classes thrive on interpretation and analysis.
• How do the assignments, readings, and lectures work together in the course? Instructors spend time designing courses, sometimes even arguing with their peers about the most effective course materials. Figuring out the overall design to the course will help you understand what each assignment is meant to achieve.

Now, what about your reader? Most undergraduates think of their audience as the instructor. True, your instructor is a good person to keep in mind as you write. But for the purposes of a good paper, think of your audience as someone like your roommate: smart enough to understand a clear, logical argument, but not someone who already knows exactly what is going on in your particular paper. Remember, even if the instructor knows everything there is to know about your paper topic, they still have to read your paper and assess your understanding. In other words, teach the material to your reader.

Aiming a paper at your audience happens in two ways: you make decisions about the tone and the level of information you want to convey.

• Tone means the “voice” of your paper. Should you be chatty, formal, or objective? Usually you will find some happy medium—you do not want to alienate your reader by sounding condescending or superior, but you do not want to, um, like, totally wig on the man, you know? Eschew ostentatious erudition: some students think the way to sound academic is to use big words. Be careful—you can sound ridiculous, especially if you use the wrong big words.
• The level of information you use depends on who you think your audience is. If you imagine your audience as your instructor and they already know everything you have to say, you may find yourself leaving out key information that can cause your argument to be unconvincing and illogical. But you do not have to explain every single word or issue. If you are telling your roommate what happened on your favorite science fiction TV show last night, you do not say, “First a dark-haired white man of average height, wearing a suit and carrying a flashlight, walked into the room. Then a purple alien with fifteen arms and at least three eyes turned around. Then the man smiled slightly. In the background, you could hear a clock ticking. The room was fairly dark and had at least two windows that I saw.” You also do not say, “This guy found some aliens. The end.” Find some balance of useful details that support your main point.

You’ll find a much more detailed discussion of these concepts in our handout on audience .

The Grim Truth

With a few exceptions (including some lab and ethnography reports), you are probably being asked to make an argument. You must convince your audience. It is easy to forget this aim when you are researching and writing; as you become involved in your subject matter, you may become enmeshed in the details and focus on learning or simply telling the information you have found. You need to do more than just repeat what you have read. Your writing should have a point, and you should be able to say it in a sentence. Sometimes instructors call this sentence a “thesis” or a “claim.”

So, if your instructor tells you to write about some aspect of oral hygiene, you do not want to just list: “First, you brush your teeth with a soft brush and some peanut butter. Then, you floss with unwaxed, bologna-flavored string. Finally, gargle with bourbon.” Instead, you could say, “Of all the oral cleaning methods, sandblasting removes the most plaque. Therefore it should be recommended by the American Dental Association.” Or, “From an aesthetic perspective, moldy teeth can be quite charming. However, their joys are short-lived.”

Convincing the reader of your argument is the goal of academic writing. It doesn’t have to say “argument” anywhere in the assignment for you to need one. Look at the assignment and think about what kind of argument you could make about it instead of just seeing it as a checklist of information you have to present. For help with understanding the role of argument in academic writing, see our handout on argument .

What kind of evidence do you need?

There are many kinds of evidence, and what type of evidence will work for your assignment can depend on several factors–the discipline, the parameters of the assignment, and your instructor’s preference. Should you use statistics? Historical examples? Do you need to conduct your own experiment? Can you rely on personal experience? See our handout on evidence for suggestions on how to use evidence appropriately.

Make sure you are clear about this part of the assignment, because your use of evidence will be crucial in writing a successful paper. You are not just learning how to argue; you are learning how to argue with specific types of materials and ideas. Ask your instructor what counts as acceptable evidence. You can also ask a librarian for help. No matter what kind of evidence you use, be sure to cite it correctly—see the UNC Libraries citation tutorial .

You cannot always tell from the assignment just what sort of writing style your instructor expects. The instructor may be really laid back in class but still expect you to sound formal in writing. Or the instructor may be fairly formal in class and ask you to write a reflection paper where you need to use “I” and speak from your own experience.

Try to avoid false associations of a particular field with a style (“art historians like wacky creativity,” or “political scientists are boring and just give facts”) and look instead to the types of readings you have been given in class. No one expects you to write like Plato—just use the readings as a guide for what is standard or preferable to your instructor. When in doubt, ask your instructor about the level of formality they expect.

No matter what field you are writing for or what facts you are including, if you do not write so that your reader can understand your main idea, you have wasted your time. So make clarity your main goal. For specific help with style, see our handout on style .

Technical details about the assignment

The technical information you are given in an assignment always seems like the easy part. This section can actually give you lots of little hints about approaching the task. Find out if elements such as page length and citation format (see the UNC Libraries citation tutorial ) are negotiable. Some professors do not have strong preferences as long as you are consistent and fully answer the assignment. Some professors are very specific and will deduct big points for deviations.

Usually, the page length tells you something important: The instructor thinks the size of the paper is appropriate to the assignment’s parameters. In plain English, your instructor is telling you how many pages it should take for you to answer the question as fully as you are expected to. So if an assignment is two pages long, you cannot pad your paper with examples or reword your main idea several times. Hit your one point early, defend it with the clearest example, and finish quickly. If an assignment is ten pages long, you can be more complex in your main points and examples—and if you can only produce five pages for that assignment, you need to see someone for help—as soon as possible.

Tricks that don’t work

Your instructors are not fooled when you:

• spend more time on the cover page than the essay —graphics, cool binders, and cute titles are no replacement for a well-written paper.
• use huge fonts, wide margins, or extra spacing to pad the page length —these tricks are immediately obvious to the eye. Most instructors use the same word processor you do. They know what’s possible. Such tactics are especially damning when the instructor has a stack of 60 papers to grade and yours is the only one that low-flying airplane pilots could read.
• use a paper from another class that covered “sort of similar” material . Again, the instructor has a particular task for you to fulfill in the assignment that usually relates to course material and lectures. Your other paper may not cover this material, and turning in the same paper for more than one course may constitute an Honor Code violation . Ask the instructor—it can’t hurt.
• get all wacky and “creative” before you answer the question . Showing that you are able to think beyond the boundaries of a simple assignment can be good, but you must do what the assignment calls for first. Again, check with your instructor. A humorous tone can be refreshing for someone grading a stack of papers, but it will not get you a good grade if you have not fulfilled the task.

Critical reading of assignments leads to skills in other types of reading and writing. If you get good at figuring out what the real goals of assignments are, you are going to be better at understanding the goals of all of your classes and fields of study.

You may reproduce it for non-commercial use if you use the entire handout and attribute the source: The Writing Center, University of North Carolina at Chapel Hill

Make a Gift

.css-s5s6ko{margin-right:42px;color:#F5F4F3;}@media (max-width: 1120px){.css-s5s6ko{margin-right:12px;}} AI that works. Coming June 5, Asana redefines work management—again. .css-1ixh9fn{display:inline-block;}@media (max-width: 480px){.css-1ixh9fn{display:block;margin-top:12px;}} .css-1uaoevr-heading-6{font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-1uaoevr-heading-6:hover{color:#F5F4F3;} .css-ora5nu-heading-6{display:-webkit-box;display:-webkit-flex;display:-ms-flexbox;display:flex;-webkit-align-items:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:start;-ms-flex-pack:start;-webkit-justify-content:flex-start;justify-content:flex-start;color:#0D0E10;-webkit-transition:all 0.3s;transition:all 0.3s;position:relative;font-size:16px;line-height:28px;padding:0;font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-ora5nu-heading-6:hover{border-bottom:0;color:#CD4848;}.css-ora5nu-heading-6:hover path{fill:#CD4848;}.css-ora5nu-heading-6:hover div{border-color:#CD4848;}.css-ora5nu-heading-6:hover div:before{border-left-color:#CD4848;}.css-ora5nu-heading-6:active{border-bottom:0;background-color:#EBE8E8;color:#0D0E10;}.css-ora5nu-heading-6:active path{fill:#0D0E10;}.css-ora5nu-heading-6:active div{border-color:#0D0E10;}.css-ora5nu-heading-6:active div:before{border-left-color:#0D0E10;}.css-ora5nu-heading-6:hover{color:#F5F4F3;} Get early access .css-1k6cidy{width:11px;height:11px;margin-left:8px;}.css-1k6cidy path{fill:currentColor;}

• Product overview
• All features
• 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
• Time tracking
• my-task icon Admin and security
• Admin console
• asana-intelligence icon Asana Intelligence
• list icon Personal
• premium icon Starter
• briefcase icon Advanced
• Goal management
• Organizational planning
• Campaign management
• Creative production
• Marketing strategic planning
• Request tracking
• Resource planning
• Project intake
• 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
• What's new Learn about the latest and greatest from Asana
• 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
• Support Need help? Contact the Asana support team
• 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

How to track utilization rate and drive team profitability

How to accomplish big things with long-term goals

Smooth product launches are simpler than you think

What is stakeholder analysis and why is it important?