Buying Guide
How to pick a project management tool for heavy planning
Gantt charts, dependencies, baselines and workload views are where planning tools differ most, so here is what each one does, which plan has it, and when a simple board is all you need.
By Matt Wagner7 min read
In this guide9 sections
Key takeaways
- If your work is a stream of small tasks, a Kanban board is usually enough.
- If one late task can push back a whole launch, you need a Gantt chart with dependencies.
- The critical path, baselines and workload views are often on a higher plan than the Gantt chart itself.
- Test with a real plan: move one task and watch what moves with it.
Do you need a planning tool, or a board?
Most project tools can make a list and a board. Far fewer can tell you that if the design review slips two days, the launch slips two days too. That second job is planning, and it is where tools are most different from each other.
Before you compare features, decide how your team actually works. There are three common ways.
Kanban
Work moves across columns like "To do," "Doing" and "Done." Great when tasks are small and mostly independent, like support requests or a content calendar. A board is enough here.
Gantt with dependencies
Tasks sit on a timeline as bars, with arrows showing which task must finish before another can start. This is the classic way to plan a building project, an office move, or a product launch with a fixed date.
Hybrid
Some teams work in sprints or on boards day to day, while a manager needs one timeline across all of them. You need a tool that does both, or two tools that talk to each other.
A board is probably enough if
- Most tasks take a day or two and do not wait on each other.
- Nobody asks "if this slips, what else slips?"
- Your deadlines are per task, not one big date at the end.
Start a decision space
Tell Otis what your team needs and Juukbox lists matching products in order of best fit.
Timelines and Gantt charts
A Gantt chart is a timeline where each task is a bar. The bar starts on the start date and ends on the end date, so you can see at a glance what happens when, and what overlaps.
Here is where the view sits on each pricing page:
| Microsoft Projectdesktop and Planner plans | Jira | Airtable | |
|---|---|---|---|
| Gantt or timeline view | Project Standard 2024, Project Professional 2024, Planner Plan 1 and Planner and Project Plan 3 | All plans | From Team |
Gantt or timeline view
- Microsoft Project
- Project Standard 2024, Project Professional 2024, Planner Plan 1 and Planner and Project Plan 3
- Jira
- All plans
- Airtable
- From Team
- Jira: Jira says its timeline "shows work within a single project." Planning across teams is a separate feature, covered below.
Some tools call their version a "timeline" and some call it a "Gantt" view, and they are not always the same thing. Airtable, for example, has both: its help pages say the Gantt view is for plotting tasks and the dependencies between them, while the Timeline view "can visualize any set of records over time, grouped by any field in your table."
Dependencies and the critical path
A dependency is a rule that one task has to wait for another. You cannot paint a wall before it is built. In a good planning tool, when the first task moves, the tasks that depend on it move too.
The critical path is the longest chain of dependent tasks in the project. If a task on that chain is late, the whole project is late. If a task off the chain is late, you may have some slack.
| Microsoft Projectdesktop and Planner plans | Jira | Airtable | |
|---|---|---|---|
| Dependencies in one project | Project Standard 2024, Project Professional 2024, Planner Plan 1 and Planner and Project Plan 3 | All plans | From Team |
| Dependencies across projects | Project Standard 2024 and Project Professional 2024 | From Premium | Not listed |
| Lead and lag | Planner and Project Plan 3 | Not listed | From BusinessWith all four dependency types |
| Critical path | Project Standard 2024, Project Professional 2024 and Planner and Project Plan 3 | Not listed | From Team |
Dependencies in one project
- Microsoft Project
- Project Standard 2024, Project Professional 2024, Planner Plan 1 and Planner and Project Plan 3
- Jira
- All plans
- Airtable
- From Team
Dependencies across projects
- Microsoft Project
- Project Standard 2024 and Project Professional 2024
- Jira
- From Premium
- Airtable
- Not listed
Lead and lag
- Microsoft Project
- Planner and Project Plan 3
- Jira
- Not listed
- Airtable
- From BusinessWith all four dependency types
Critical path
- Microsoft Project
- Project Standard 2024, Project Professional 2024 and Planner and Project Plan 3
- Jira
- Not listed
- Airtable
- From Team
- Airtable: Dependencies need a linked record field that links to its own table, so expect a little setup.
Airtable's help pages put the critical path simply: it is "a chain of dependent tasks that can influence the finishing date of the overall project."
Lead and lagLag is a planned wait between two tasks, like letting concrete dry for three days. Lead is the opposite: the next task can start a little before the first one ends. If your plans have gaps like these, check that the tool can store them, not just draw an arrow.
Watch for tasks that fall off the path. Airtable says tasks without a dependency link to the final task are left out of its critical path. In any tool, a task nobody linked can hide a real delay.
Baselines: the plan you started with
A baseline is a saved copy of your plan at one moment, usually the day everyone agreed to it. Later you compare today's plan against it and see exactly what slipped and by how much. Without one, the plan quietly changes week by week and nobody can say how far it has drifted.
Microsoft Project lists baselines on both its Standard 2024 and Professional 2024 desktop plans. In Microsoft's cloud plans, baselines are on Planner and Project Plan 3 and not on Planner Plan 1. We did not find baselines listed on Jira's or Airtable's pricing pages, so if your boss or your client asks "how does this compare to the original plan?", ask those vendors how they would answer it.
Resource and workload planning
A timeline can look perfect and still be impossible, because the same person is booked on three things at once. Resource planning, also called workload or capacity planning, is how a tool catches that.
Each tool does it its own way.
| Microsoft Projectdesktop and Planner plans | Jira | Airtable | |
|---|---|---|---|
| Resource leveling | Project Standard 2024 and Project Professional 2024 | Not listed | Not listed |
| Team capacity | Project Professional 2024Team Planner | From PremiumCapacity, in Plans | From TeamUtilization in the Timeline view |
| Workload view | Planner Plan 1 and Planner and Project Plan 3People view | Not listed | Not listed |
Resource leveling
- Microsoft Project
- Project Standard 2024 and Project Professional 2024
- Jira
- Not listed
- Airtable
- Not listed
Team capacity
- Microsoft Project
- Project Professional 2024Team Planner
- Jira
- From PremiumCapacity, in Plans
- Airtable
- From TeamUtilization in the Timeline view
Workload view
- Microsoft Project
- Planner Plan 1 and Planner and Project Plan 3People view
- Jira
- Not listed
- Airtable
- Not listed
- Jira: Capacity is counted per team per sprint, in story points or hours, and a work item only counts once it has a team, a sprint and an estimate.
- Airtable: You set it up yourself with fields for allocated hours, the person or team, and their available hours.
The pattern: Microsoft Project works with people and their assignments, Jira works with teams and sprints, and Airtable gives you the parts to build your own. None is wrong. Pick the one that matches how your team already estimates work.
Planning across many projects
One project on one timeline is the easy case. It gets harder when five teams share people and one team's delay blocks another's. This is where the planning features usually move up a plan.
Jira is a clear example. Its timeline is on every plan, but Plans, its cross-team planning feature, is "only available on Jira Premium and Jira Enterprise." Jira describes Plans as letting managers "track capacity, manage dependencies, and model delivery scenarios." Microsoft Project's desktop plans let you "Group smaller related projects under a single master project," and Microsoft lists portfolios on its Planner plans.
What if?Scenario planning lets you try a change, like moving a deadline or adding a person, without changing the real plan. Jira lists Scenario Modeling on Premium and Enterprise. If you are often asked "what happens if we...", put it on your list.
Price it out
Planning tools are priced in very different ways, so compare the way each one charges, not just the number.
- Project Standard 2024, one-time purchase
- $679.99
- Free plan, for up to 10 users
- $0
- Team, per seat per month, billed annually ($24 billed monthly)
- $20
- Business, per seat per month, billed annually ($54 billed monthly)
- $45
Microsoft also sells Project Professional 2024 for $1,129.99, one time, and Planner and Project Plan 3, which includes the Project desktop app, for $30 per user per month, paid yearly.
Two things to notice. The one-time Microsoft Project desktop licenses are each "Licensed for one user" on one PC, so a team of ten needs ten. And the plan with the Gantt chart is not always the plan with the rest: Jira's timeline is on every plan, including Free, but capacity and cross-team planning are on Premium, and Airtable's fixed dependencies with lead and lag are on Business, not Team.
Test it with a real plan
A demo plan always works. Yours has to.
During a free trial
- Rebuild one real project from the last year, with its real tasks, dates and people.
- Link the dependencies, then push one early task back a week and see what moves with it.
- Turn on the critical path and check that it matches the chain you know was critical.
- Save a baseline, change a few dates, and see how clearly the tool shows the difference.
- Book one person on two overlapping tasks and see whether the tool warns you.
If a tool makes any of these hard, that is the work your team will be doing by hand every week.
Questions to ask
"Which plan has the Gantt chart, and which plan has dependencies, the critical path, and baselines?"
"Does workload planning count hours per person, or points per team, and what do we have to set up first?"
"Can we plan across several projects at once, and is that on the plan we are quoting?"
If you want a head start, describe your team and how you plan your projects in Juukbox, and you will see matching tools in order of fit.
Know what your team needs?
Tell Otis about your team and Juukbox builds a space with matching products in order of best fit.
Sources
- Compare Project plans, Microsoft
- Compare Planner plans, Microsoft
- Pricing, Atlassian
- Introduction to Jira Advanced Planning, Atlassian
- How your plan assigns capacity, Atlassian Support
- Pricing, Airtable
- Gantt view milestones, dependencies, and critical paths, Airtable Support
- Timeline view overview, Airtable Support
- Date dependencies in Airtable, Airtable Support
- Timeline view: Resource allocation, Airtable Support





