← All articles

Project planning with Power BI: Gantt, dependencies and resources in an example

A fictional example shows how to review project dates, dependencies and a resource bottleneck together in Power BI.

A project can appear on schedule while still having a resource bottleneck: several teams may have planned the same specialist at the same time. A Power BI report can bring existing dates, dependencies and capacity together to prepare the next planning decision.

What belongs in a project report?

A Gantt chart needs a unique ID, name, start and finish for each task, along with its project. Add milestones, progress, an approved baseline and links between tasks where needed. Resource analysis also requires people or roles, planned effort, its distribution over time and available capacity for the same period.

Check the source and refresh date of the data, and make sure effort and capacity use the same units and working days. Missing capacity data does not mean capacity is available.

Fictional example: three projects, one BI specialist

A synthetic planning dataset contains 30 tasks across three projects and eight people. On 14 October 2026, the BI specialist Lea is assigned to three concurrent tasks. Together they require 24 hours in one day, while her daily capacity is 8 hours: a 16-hour shortfall that day. Names, projects and figures are fictional and do not represent customer results.

Across 20 working days, Lea has 160 hours of capacity. The three demo projects require 200 hours: 200 / 160 = 125%, or 40 hours more than available over the period. The sum of daily excesses is 112 hours. It is higher because free days do not automatically resolve overload on other days. The dataset represents only the three demo projects, not necessarily all of the person's work.

Review the bottleneck and dependencies together

  1. Focus on the period: Show all three projects and Lea's tasks on 14 October. Check the assignments and daily effort distribution against the source data.
  2. Read the impact in the Gantt chart: Review dates, milestones and supplied dependencies. With a finish-to-start dependency, a successor cannot begin until its predecessor finishes; moving a task can therefore affect subsequent dates.
  3. Discuss options: Agree with the owners whether tasks can move or suitable people can take them on. Availability alone does not establish that someone has the necessary skills.
  4. Update the authoritative plan: Compare the proposal with the baseline, check dependencies and record decisions in the source planning system. The report makes conflicts visible; it does not replace business approval.

A single-project view must not hide the same person's other assignments. Check capacity conflicts across projects using all available allocation data.

Implement project analysis in Power BI

Model tasks, dependencies, resource assignments and capacity with unique keys. Align filters and periods, and verify some known tasks and daily values against the source. Start with a limited pilot before adding more projects.

The Aivana Project Intelligence visual supports analysis of dates, milestones, dependencies and resource load. Planning drafts in the visual do not replace an authoritative update in the source system; validate features and field mapping in the intended Power BI host. The Power BI project planning solution explains how to get started. A separate DemoReport uses its own example dataset.