Overview
Tools and Documentation is 19% of Project+ and has three objectives. The first covers tools used across the life cycle: tracking charts such as Gantt and PERT, logs and registers, dashboards, status reports, version control, time tracking, task boards and the requirements traceability matrix. The second compares productivity tools for communication, collaboration, meetings, documents, scheduling and ticketing, including cloud versus on-premises options.
The third objective asks you to read quality and performance charts, including histograms, Pareto, run, scatter, fishbone, control, burnup and burndown, velocity and decision trees, and use them to make a project decision. The domain is the practical layer under Domains 1 and 2: those domains tell you what to manage, and this one tells you where to record it and how to read the evidence.
How it's tested
Domain 3 questions either describe a need and ask which tool or document is BEST, or present a chart and ask what it shows or what the project manager should do. Performance-based items may ask you to match charts to purposes or interpret a burndown, Pareto or control chart.
-
Tool to need matching
A stakeholder or team need is described, such as tracking requirement coverage, and you pick the tool designed for it.
-
Chart interpretation
A chart is shown or described and you decide what it means, such as a burndown above the ideal line meaning the sprint is behind.
-
Chart to decision
Given chart data, you choose the action it supports, such as fixing the top two defect categories on a Pareto chart first.
A quality lead reports seven consecutive defect measurements above the mean on a control chart, all within the control limits. Candidates often answer that the process is in control because no point is outside the limits. The rule of seven says a run of seven points on one side of the mean signals a non-random pattern, so the process should be investigated even though no single point is out of limits.
Objectives 3
Official objectives from the CompTIA outline, in outline order.
3.1 Given a scenario, use the appropriate tools throughout the project life cycle.Tracking charts, logs, registers, dashboards, status reports and traceability.
- What it means
- These are the tools that track and document the project: Gantt and PERT charts for schedules, logs and registers for risks, issues, changes, decisions and actions, dashboards and status reports for performance, plus version control, time tracking, task boards and the requirements traceability matrix.
- What to understand
- A Gantt chart shows tasks against a timeline with bars, progress and dependencies; a PERT chart is a network diagram of dependencies and estimated durations used to find the critical path. A dashboard gives an at-a-glance summary of key indicators, while a status report explains progress, risks and next steps. The requirements traceability matrix links each requirement to its source, design, test and deliverable so nothing is dropped.
- How it shows up
- A scenario describes an information need, such as proving every requirement was tested, and asks which tool to use.
- Common confusion
- Candidates use a Gantt chart to answer a dependency and critical path question that needs a network diagram, or pick a dashboard for an audience that needs explanation and context.
3.2 Compare and contrast various project management productivity tools.Communication, collaboration, meeting, document, scheduling and ticketing tools.
- What it means
- Productivity tools support the daily work of the team: real-time and asynchronous communication tools, collaboration and shared document platforms, meeting and video conferencing tools, office productivity software, scheduling software and ticketing systems, deployed in the cloud or on premises.
- What to understand
- Choose by need: real-time chat or video for quick decisions and distributed teams, shared document repositories with version history for co-authoring, scheduling software for dependencies and resource loading, and ticketing systems for tracking requests and defects through a workflow. Cloud tools offer access from anywhere and vendor-managed updates; on-premises tools give the organization more direct control over data location and configuration.
- How it shows up
- A team situation is described, such as members in three time zones losing track of document versions, and you choose the tool category that solves it.
- Common confusion
- Candidates pick email as a collaboration tool. Email distributes information but does not provide shared editing, version control or workflow tracking.
3.3 Given a scenario, analyze quality and performance charts to inform project decisions.Reading Pareto, control, run, scatter, fishbone, burndown, velocity and decision trees.
- What it means
- Each chart answers a specific question: a histogram shows frequency distribution, a Pareto chart ranks causes by frequency to reveal the vital few, a run chart shows a trend over time, a scatter diagram shows correlation between two variables, a fishbone diagram organizes possible causes, a control chart shows whether a process is stable, burnup and burndown charts show work completed or remaining, a velocity chart shows work completed per iteration, and a decision tree compares options by expected value.
- What to understand
- Pareto applies the 80/20 principle, so fix the tallest bars first. On a control chart, a point outside the upper or lower control limit or seven consecutive points on one side of the mean means the process needs investigation. Burndown slopes down toward zero remaining work; a line above the ideal line means behind. A decision tree multiplies outcome values by probabilities to find expected monetary value.
- How it shows up
- A chart or its data is described and you identify what it shows or which action it supports.
- Common confusion
- Candidates treat correlation on a scatter diagram as proof of cause, or read a burnup chart as if it were a burndown.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Gantt chart
A bar chart that plots tasks against calendar time, often showing progress, milestones and dependencies.
- Remember
- It is the standard way to communicate a schedule visually to most audiences.
- Tested as
- Questions ask which tool shows task durations and timeline to stakeholders.
- Trap
- Using it to explain probabilistic duration estimates, which is PERT's purpose.
-
PERT chart
A network diagram of activities and dependencies that uses optimistic, most likely and pessimistic estimates to calculate expected durations.
- Remember
- It highlights the critical path and dependency logic rather than calendar dates.
- Tested as
- Scenarios that need dependency analysis or estimate uncertainty.
- Trap
- Assuming it shows calendar dates like a Gantt chart.
-
Requirements traceability matrix
A table that links each requirement to its source, design element, test case and delivered feature.
- Remember
- It proves coverage and shows what is affected when a requirement changes.
- Tested as
- Questions about confirming every requirement was built and tested.
- Trap
- Confusing it with the RACI matrix, which tracks people, not requirements.
-
Logs vs. registers
Logs record events as they occur, such as issues, changes, decisions and action items; registers hold managed inventories such as risks and stakeholders.
- Remember
- The risk register holds potential events; the issue log holds current problems.
- Tested as
- Questions ask where a specific item should be recorded.
- Trap
- Recording a decision in the issue log or a new risk in the change log.
-
Dashboard vs. status report
A dashboard is a visual, at-a-glance display of key metrics; a status report is a periodic written summary of progress, risks, issues and next steps.
- Remember
- Executives often want the dashboard; stakeholders who need context and actions want the report.
- Tested as
- Communication tool selection scenarios.
- Trap
- Assuming one tool satisfies every audience.
-
Pareto chart
A bar chart of causes sorted from most to least frequent with a cumulative percentage line.
- Remember
- Based on the 80/20 principle: focus on the few causes that produce most of the problems.
- Tested as
- Questions ask which defects to fix first.
- Trap
- Fixing the most expensive single defect instead of the most frequent categories.
-
Control chart
A chart of process measurements over time with a mean and upper and lower control limits.
- Remember
- Investigate any point outside the limits or seven consecutive points on one side of the mean.
- Tested as
- Questions ask whether a process is in control and what to do.
- Trap
- Confusing control limits, which come from process data, with specification limits set by the customer.
-
Run chart
A line chart of a measure over time that shows trends without control limits.
- Remember
- Use it to see whether performance is improving or degrading.
- Tested as
- Scenarios about spotting a trend in defect counts or response times.
- Trap
- Expecting it to show whether the process is statistically in control.
-
Scatter diagram
A plot of paired values for two variables to reveal correlation.
- Remember
- Correlation shows a relationship, not proof of causation.
- Tested as
- Questions ask what relationship the data suggests.
- Trap
- Concluding one variable causes the other.
-
Fishbone diagram
A cause-and-effect (Ishikawa) diagram that groups possible causes of a problem into categories.
- Remember
- It supports root cause analysis by organizing brainstormed causes.
- Tested as
- Issue scenarios that need structured root cause analysis.
- Trap
- Using it to rank causes by frequency, which is Pareto's job.
-
Burndown vs. burnup
Burndown shows work remaining falling over time; burnup shows work completed rising toward a total scope line.
- Remember
- Burnup reveals scope changes because the total scope line moves.
- Tested as
- Agile performance questions about progress and scope growth.
- Trap
- Reading a flat burndown as finished work rather than stalled progress.
-
Velocity chart
Shows the amount of work, usually story points, completed per sprint.
- Remember
- Average velocity is used to forecast how many sprints remaining work will take.
- Tested as
- Questions ask how many sprints are needed for the remaining backlog.
- Trap
- Comparing velocity between different teams, whose point scales differ.
-
Decision tree and EMV
A branching diagram of choices, probabilities and outcomes; expected monetary value multiplies each outcome by its probability and sums them.
- Remember
- Choose the path with the best EMV, usually highest value or lowest cost.
- Tested as
- Questions present two options with probabilities and ask which is better.
- Trap
- Ignoring the probability and comparing only the best-case outcomes.
-
Cloud vs. on-premises tools
Cloud tools are hosted and maintained by a provider and accessed over the internet; on-premises tools run on the organization's own infrastructure.
- Remember
- Cloud favors access and low setup effort; on-premises favors direct control over data and configuration.
- Tested as
- Productivity tool comparison questions with remote teams or data constraints.
- Trap
- Assuming cloud is always cheaper or always less secure.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Gantt vs. PERT
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Gantt chart | Tasks as bars across a calendar timeline | Shows when work happens and progress against dates | Using it to calculate expected durations from three estimates |
| PERT chart | Network of activities, dependencies and estimated durations | Shows logic, critical path and estimate uncertainty | Expecting it to show calendar dates and percentage complete |
Pareto vs. histogram vs. fishbone
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Histogram | Bars showing the frequency distribution of a variable | Shows shape and spread, not ranked causes | Using it to decide which cause to fix first |
| Pareto chart | Causes ranked by frequency with a cumulative line | Identifies the vital few causes to fix first | Confusing it with an unsorted histogram |
| Fishbone diagram | Possible causes grouped by category | Explores potential causes; does not measure frequency | Using it to prioritize causes by data |
Burndown vs. burnup vs. velocity
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Burndown | Work remaining over time | Falls toward zero; hides scope additions | Missing that scope grew because the line stays level |
| Burnup | Work completed over time against a total scope line | Shows scope changes explicitly | Reading a rising line as a problem |
| Velocity | Work completed per sprint | Used to forecast future sprints | Comparing velocity across teams |
Control limits vs. specification limits
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Control limits | Boundaries calculated from the process's own data, typically three standard deviations from the mean | Show whether the process is stable | Treating them as customer requirements |
| Specification limits | Boundaries set by the customer or requirement | Show whether output is acceptable | Assuming an in-control process always meets specifications |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Dashboard for every audience
- What candidates pick
- Give the steering committee a dashboard only.
- Why it looks right
- Dashboards look polished and summarize everything.
- Why it's wrong
- When stakeholders need context, explanations of variance and requested decisions, a status report or presentation is the better tool; a dashboard alone shows numbers without narrative.
Clue to watch for The audience must approve something or understand why performance changed.
-
Fix the biggest single defect
- What candidates pick
- Fix the defect that caused the most expensive outage first.
- Why it looks right
- Cost seems like the obvious priority.
- Why it's wrong
- When the question presents a Pareto chart of defect frequency, the decision it supports is fixing the categories that produce most defects.
Clue to watch for The data shows counts by category sorted with a cumulative percentage.
-
No points outside the limits
- What candidates pick
- Declare the process in control.
- Why it looks right
- Control limits seem like the only rule.
- Why it's wrong
- Seven or more consecutive points on one side of the mean is a non-random pattern that calls for investigation even inside the limits.
Clue to watch for The scenario counts consecutive points above or below the mean.
-
Correlation as cause
- What candidates pick
- Conclude overtime hours cause defects because the scatter diagram shows a strong positive pattern.
- Why it looks right
- The relationship looks clear.
- Why it's wrong
- A scatter diagram shows correlation only; another factor, such as schedule pressure, may drive both, so root cause analysis is still required.
Clue to watch for The question asks what the diagram proves.
-
Flat burndown means done
- What candidates pick
- Report that the sprint is on track because the burndown line is flat.
- Why it looks right
- A flat line looks stable.
- Why it's wrong
- A flat burndown means remaining work is not decreasing, so progress has stalled; done means the line has reached zero.
Clue to watch for Several days pass with no change in remaining work.
-
Email as collaboration
- What candidates pick
- Have distributed authors email document versions to each other.
- Why it looks right
- Everyone already uses email.
- Why it's wrong
- Shared collaboration platforms with version history and concurrent editing prevent conflicting copies; email multiplies versions.
Clue to watch for Team members are overwriting changes or working from different copies.
Answer framework
For tool and chart questions, define the question the stakeholder is asking before choosing the tool that answers it.
- Restate the information need in plain words, such as when tasks happen, why defects occur, which cause matters most, or whether the process is stable.
- Identify the audience and how they will use the information: an executive scanning status, a team managing daily work, or an auditor checking coverage.
- Match the need to the tool built for it, such as Gantt for timeline, PERT for dependencies, Pareto for priority, fishbone for causes, control chart for stability and the traceability matrix for requirement coverage.
- If a chart is shown, read its axes, limits and reference lines before the data, then apply the chart's rules such as the rule of seven or the ideal burndown line.
- Choose the action the evidence supports and record it in the right log or register so the decision is traceable.
Practice question
Want more like this? The CompTIA Project+ practice test has questions for every domain.
Checklist
0 of 13
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Build a one-page grid of every chart and tool with three columns: the question it answers, what it looks like, and its most common misuse. Start with objective 3.3 because chart interpretation carries the most reasoning, then cover 3.1 tracking tools and finish with 3.2 productivity tools, which are mostly recognition.
Commonly underestimated areas are the control chart rules, the difference between burndown and burnup when scope changes, and the requirements traceability matrix, which candidates mix up with the RACI matrix. Practice reading charts rather than only memorizing names: sketch a burndown that stalls mid-sprint, a control chart with seven points above the mean, and a Pareto chart, then say aloud what decision each supports.
After the content, take practice items that show a chart and ask for an action, and time yourself, since performance-based items can consume minutes. Then revisit Domain 1 earned value and velocity topics, which these charts display, and Domain 2 to place each tool in its life cycle phase.
FAQ
How much of Project+ is Domain 3?
Tools and Documentation is 19% of the PK0-005 exam, with three official objectives covering life cycle tools, productivity tools and quality and performance charts.
Which charts should I know for Project+?
The outline lists histogram, Pareto, run, scatter, fishbone, control, burnup and burndown, velocity and decision tree charts. Know what question each answers and how to read it.
Do I need to know specific software products?
No. The objectives name tool categories such as scheduling software, ticketing systems and collaboration platforms, so questions test which category fits a need rather than a vendor's features.
What is the rule of seven?
On a control chart, seven or more consecutive points on one side of the mean indicate a non-random pattern that should be investigated, even if every point is within the control limits.
How is a burnup chart different from a burndown chart?
A burndown shows remaining work falling toward zero, while a burnup shows completed work rising toward a total scope line. Because the scope line can move, a burnup makes scope changes visible.
How long should I study Domain 3?
As a planning estimate, about 15 to 20 hours, with most of that time spent practicing chart interpretation rather than memorizing tool names.
How does Domain 3 relate to the other domains?
It records and displays the work of the other domains: risks and issues from Domain 1 live in its logs and registers, Domain 2 phases use its schedules and reports, and its quality charts support Domain 1 quality and performance decisions.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- PRINCE2 7 Foundation Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Certified Associate in Project Management Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 3 knowledge
You have matched tools to needs and practiced reading Pareto, control, burndown and velocity charts. Test whether you can interpret charts and pick the right tool under timed Project+ conditions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the CompTIA Project+ AI tutor Get any concept explained your way