CompTIA PK0-005 Gantt, Burndown, and Dashboards Guide
April 13, 2026
Study CompTIA PK0-005 Gantt, Burndown, and Dashboards: key concepts, common traps, and exam decision cues.
On this page
This lesson is about reading the question behind the tool. Project+ cares less about the brand name and more about whether you chose the artifact that actually shows schedule status, remaining work, or tracked project decisions clearly.
Tool chooser
If the team needs to see…
Strongest first tool
task order, duration, and dependencies
Gantt chart
remaining agile work over time
burndown chart
approved or requested changes
change log
active problems
issue log
future threats and responses
risk register
summary status in one view
dashboard
What CompTIA is really testing
If the stem shows…
Strong reading
dependency and milestone questions
schedule-view tool choice matters
sprint progress or remaining effort
burndown thinking matters
scattered status details
dashboard or register fit matters
confusion between active problem and future concern
log or register choice matters
Common traps
Trap
Better rule
using a dashboard when the question needs a detailed working log
summary views do not replace control records
choosing a Gantt chart for a simple issue-tracking problem
schedule view is not the same as blocker tracking
treating burndown like a generic status report
burndown is specifically about remaining work over time
Decision order that usually wins
Decide whether the need is schedule visualization, remaining-work tracking, issue control, or executive summary.
Use detailed logs for control and dashboards for summary, not interchangeably.
Match the artifact to whether the work is predictive-style scheduling or agile remaining effort.
Keep current blockers separate from future risks and approved changes.
Choose the artifact that answers the exact reporting question in the stem.