Every project tells a story about its goals, team, timing, and deliverables—and it requires detailed project planning and management to get the story right. Some of those stories are short and to the point while others are epic novels rife with twists and turns. No matter the length or level of drama, every story is based on a story arc or an outline—or as we call it in the project management world, a project plan.
Project planning is the process of defining the project scope, objectives, and steps needed to get the work done. It's one of the most important processes in project management. The output of the project planning process is a project management plan.
A project plan—also known as a project management plan—is a document that outlines the process your team will use to manage the project according to scope to meet its stated objectives. The purpose of a project plan is to map out the steps and resources it will take to complete a project on time and budget.
A project plan communicates vital information—such as deadlines, assignments, and key milestones—to all project stakeholders and is integral to project success. It is most commonly represented in the form of a gantt chart to make it easy to ensure work stays on track.
The fact is, 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!
Any solid project plan should answer these questions:
Learning how to develop a project plan doesn’t have to be difficult. Follow these 9 simple project planning steps to create a project plan that’s both well-written and on target.
Rather watch than read? Check out our video tutorial on how to make a realistic project plan.
Before you start creating a project plan, make sure you know all the facts. Dive into the documents and communications relevant to the project.
Go over the scope of work and related documents (maybe an RFP or notes from sales calls or meetings with your client team). Be thorough. Understand the details and ask thoughtful questions before you commit to anything.
A good project manager is well-informed and methodical in how they write a project plan. At a minimum, you’ll be responsible for possessing a thorough understanding of:
Understanding your client's team and process may help you answer:
In addition to all of your questions about your client team and their expectations, set some time aside with your main client contact and ask them some tough questions about process, organizational politics, and general risks before creating a project plan. Doing so will convey that your team has the experience to handle any type of difficult personalities or situation and that you care about the success of the project from the start.
Questions that may impact a project plan:
After getting the answers you need, take some time to think about the responses in light of the project goals and how your team might approach a similar project.
If you’re at a loss for where to start, take a look at the questions at the beginning of this chapter to outline the who, what, when, and how of the project. Think about the tasks outlined in the scope of work and try to come up with a project planning and management approach by creating a high-level outline. All you need is a calendar to check dates.
Side note: There will always be multiple ways to execute the work you’re planning, and it’s easy to focus on what the end product will look like. Don’t go there. Instead, focus on the mechanics of how it will happen.
Getting tied up in the execution will only confuse you and likely make you feel unimpressed by the final product because it’s not what you envisioned. Remind yourself: You’re there to plan and guide the project, not create it.
A project outline will help you to organize your thoughts, formulate what might work for the project, and then transform everything into a discussion. Take this time to build a simple project plan outline—it doesn't have to have all the details just yet. Doing so lays the foundations for a solid, sustainable project plan.
Starting a project must begin with clear communication of the project goals and the effort required to meet them. This comes with understanding the fact that a project manager can’t be the only one writing a project plan.
Sure, you could try—but if you’re interested in team buy-in, you won’t. That's because 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. Doing that would be like stabbing every single one of your coworkers in the back. Not so good for the old reputation.
It’s also great to utilize the super-smart folks surrounding you to get their input on how the team 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 your project plan review time to question your own thinking and push the team to take a new approach to the work.
For instance, if you’re working on a website design project plan, can designers start creating visual concepts while the wireframes are being developed? Will it make sense for this project and for the team? 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 project plan. It’s also a big help in getting everyone to think about the project in the same terms.
This type of buy-in and communication builds trust on a team and gets people excited about working together to solve a goal. It can work wonders for the greater good of your team and your project.
When you’ve got all the info you need and you’ve spoken to all parties, you should feel more than comfortable enough to put together a rock solid project schedule using whatever tool works for you. (Ahem, TeamGantt works nicely for a lot of happy customers).
Any good online project planning tool will help you formalize your thoughts and lay them out in a consistent, readable way.
Make it readable
To make your project plan readable, ensure tasks, durations, milestones, and dates are crystal-clear. Try to make a simple project plan—the more straightforward and easier to read it is, the better. No matter what tool you’re using, you should include these features:
Within TeamGantt's resource management software, you can assign who's responsible to each task so everyone knows who's responsible for what.
In addition to all of this, you should be as flexible as possible when it comes to how your project plan is presented. There's no absolute when it comes to how you represent your plan as long as you and your team understand what goes into one.
Remember, people absorb information differently. While some people prefer a list view, others might prefer to see a calendar or even a gantt chart. You can make all of those variations work if you’ve taken the steps to create a solid plan.
If your team currently prefers the traditional Excel gantt chart and isn’t quite ready to use TeamGantt yet, try our free Excel template.
TeamGantt gives you the ability to quickly and easily build a project plan using most of the tips listed above. And it makes your project plan even easier to adjust using a simple drag and drop feature.
Once you've created your project, you can have peace of mind knowing you thought ahead and have a plan to guide you along as you go. Try it out, and create a gantt chart for completely free!
You’re almost finished! You’ve done your research, outlined your approach, discussed it with your team, and built your formal project plan. Do yourself one quick favor and ask someone on your team to review it before you hand it over to your clients.
There’s nothing more embarrassing than being a project manager and delivering a plan with an error—like an incorrect date. It’ll take someone 10 minutes, and you’ll have peace of mind.
After you’ve put all of that work into creating this important document, you want to make sure it's actually been reviewed.
When you’re delivering your project plan, make sure you provide a summary of it in prose format. A short message that covers the overall methodology, resources, assumptions, deadlines, and related review times will help you to convey what the project plan means to the project and to everyone involved.
Don’t be bashful about it: Explain the thought that's gone into the process of building the project plan, and open it up for discussion. It can be good to set up a call to review the plan line by line with a client. This ensures your client will understand the process and what each step in the plan means.
Sure, you might have to explain it a few more times, but at least you’re making the effort to help establish good project planning standards across the board and educate your clients on how your team works. And again, it shows that you care.
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 (it happens). Regardless, plans will change.
With a good team and a clear scope of work, you’re on your way to making a project plan that's manageable and well-thought-out. Having a solid project plan is your best defense against project chaos.
If you’re an easygoing project manager who can adapt your approach and your plan to go with the flow while calling out the appropriate risks, you’ll be happy. Otherwise, the daily changes will cloud your vision, and you’ll focus on things that won’t help your team, your client, or the project.
And remember: Project managers can have fun too! So pick up your project scope, dig into your own research, and start writing your next masterpiece.
Learn how easy project planning can be with TeamGantt. Create your first gantt chart for free!