Tools and Documentation PK0-005 Practice Quiz

• A. A horizontal bar chart that plots project activities against a timeline, each bar's length represents the activity's duration; bars are arranged vertically by activity name; the chart shows planned start/end dates, actual progress (percentage complete bars), and relationships between activities
• B. A hierarchical breakdown of all project deliverables organized by level
• C. A probability-impact grid that maps project risks by likelihood and severity
• D. A pie chart showing the percentage of budget allocated to each project phase

GANTT CHART: the most widely used project schedule visualization tool. KEY CHARACTERISTICS: HORIZONTAL BAR CHART: each project activity appears as a horizontal bar; the bar's LEFT EDGE = planned start date; the bar's RIGHT EDGE = planned end date; bar LENGTH = planned duration; TIMELINE AXIS: the horizontal axis is a calendar (days, weeks, months); activities are listed vertically on the left axis; PROGRESS TRACKING: many Gantt tools show a 'progress bar' within each activity bar (e.g., 60% shaded = 60% complete); DEPENDENCIES: dependency lines connect related activities (showing which activities must precede others); MILESTONES: shown as diamond shapes (zero duration) at key completion points; BASELINES: many tools overlay the original planned dates (baseline) against current dates for variance comparison. WHAT GANTT SHOWS AT A GLANCE: which activities are active right now; which are complete; which are not yet started; which are behind schedule (actual end date exceeds planned end date); the overall project timeline. GANTT LIMITATIONS: complex dependency relationships can be hard to read; doesn't show statistical probability of durations (PERT does); not ideal for showing the critical path calculation (network diagram does).

• A. A milestone chart shows only significant project events (milestones) against a timeline, no task-level detail; milestones are key completion events such as phase completions, deliverable approvals, and major go/no-go decision points; executives need the high-level status without operational detail
• B. Milestone charts show every task in the project with daily granularity, more detail for executives
• C. Milestone charts show resource allocation by team member, who is doing what on which date
• D. Milestone charts are identical to Gantt charts, same tool, different name

MILESTONE CHART characteristics and executive suitability: WHAT IT SHOWS: significant project events only, no task-level detail; each milestone is a single point on the timeline (a date, not a duration range); typically includes 8-15 milestones for a large project (vs. hundreds of tasks in a full schedule); MILESTONE EXAMPLES: Phase 1 Requirements Complete (planned: March 15 | actual: March 18, 3 days late); Architecture Review Approved (planned: April 1 | status: On Track); UAT Start (planned: June 1 | risk: vendor delay may impact); Final Go-Live (planned: September 30); VISUAL FORMAT: points or diamonds on a timeline; often color-coded: GREEN = on track or complete; AMBER = at risk; RED = delayed; STATUS AT A GLANCE: executives can see in 5 seconds which milestones are complete, on track, or at risk; WHY APPROPRIATE FOR EXECUTIVES: respects executives' limited time; focuses on decisions and strategic-level status; doesn't require understanding of task dependencies or technical detail; easily updated (8-15 milestones vs. 200 tasks); CONTRAST WITH GANTT: a Gantt chart shows all activities with durations and task-level detail, appropriate for the project team; a milestone chart shows only key events, appropriate for governance.

• A. Activity 7 is behind schedule (actual completion on September 22 is 7 days later than the September 15 baseline); Activity 12's actual completion extending beyond the baseline end date means Activity 12 took longer than planned (behind schedule or over-duration)
• B. Activity 7 is ahead of schedule; Activity 12 is behind schedule
• C. Both activities are on schedule, baseline and actual bars always appear different as a formatting choice
• D. Activity 7 is exactly on schedule. September 22 is within the acceptable tolerance range of September 15

GANTT CHART BASELINE vs. ACTUAL INTERPRETATION: ACTIVITY 7, SCHEDULE DELAY: BASELINE end date: September 15 (what was planned); ACTUAL end date: September 22 (when it actually completed or is currently projected to complete); September 22 > September 15 = 7 calendar days late; VISUAL: the actual bar EXTENDS BEYOND the right edge of the baseline bar; this extension represents the schedule variance (SV is negative for this activity); ACTIVITY 12, DURATION OVERRUN: 'Actual bar shorter than actual completion bar', if the actual bar extends beyond the baseline bar, the activity took more time than planned; the additional length of the actual bar beyond the baseline represents the additional time consumed; INTERPRETATION: Activity 12 is similarly delayed relative to its baseline. CRITICAL PATH CONSIDERATION: whether either delay affects the project end date depends on: whether the activity is on the critical path (zero float → any delay = project delay); whether the activity has remaining float (float absorbs the delay if float exceeds the variance). GANTT CHART VALUE for tracking: by overlaying baseline and actual, project managers and stakeholders can immediately see which activities are ahead, on track, or behind, no detailed schedule analysis required; RAG status can be derived from baseline vs. actual comparison.

• A. PERT expected duration = (O + 4M + P) / 6 = (10 + 60 + 28) / 6 = 98/6 = 16.33 days; PERT weights the most likely estimate 4× to acknowledge it is more likely than the extremes; the expected duration (16.33) is higher than the most likely (15) because the pessimistic tail (28) pulls the weighted average up, PERT accounts for uncertainty and schedule risk more realistically than a single point estimate
• B. PERT expected duration = (O + M + P) / 3 = (10+15+28)/3 = 17.67 days
• C. PERT expected duration = P − O = 28 − 10 = 18 days (the range)
• D. PERT uses only the pessimistic estimate, the pessimistic value provides the most conservative schedule

PERT FORMULA: Expected Duration = (O + 4M + P) / 6; CALCULATION: O = 10, M = 15, P = 28; = (10 + (4×15) + 28) / 6; = (10 + 60 + 28) / 6; = 98 / 6; = 16.33 days. WHY PERT vs. MOST LIKELY: PERT ACCOUNTS FOR ASYMMETRIC UNCERTAINTY: the most likely estimate (15 days) reflects the typical case; the pessimistic estimate (28 days) is 13 days above most likely; the optimistic estimate (10 days) is only 5 days below most likely; real-world project activities often have LONGER tails on the pessimistic side (things go wrong more often than they go wonderfully right); the PERT formula's weighting (4M + extremes ÷ 6) captures this asymmetry; EXPECTED VALUE: the PERT expected duration (16.33 days) is the AVERAGE OUTCOME across all probability-weighted scenarios; using 15 days (most likely) would underestimate duration in expectation because the pessimistic tail is heavier; PRACTICAL USE: schedule buffers derived from PERT estimates are more realistic than those derived from most-likely-only estimates; PERT is particularly valuable for: novel activities with high uncertainty; activities with complex dependencies; research or technical discovery work where the pessimistic scenario is meaningfully different from the most likely. STANDARD DEVIATION: σ = (P−O)/6 = (28−10)/6 = 3 days → provides the variability estimate for probabilistic schedule analysis.

• A. The sprint was completed successfully, any burndown ending with points remaining is normal
• B. The Day 5 spike means the team completed extra work and added it to the sprint, the chart shows overcapacity
• C. The burndown reveals three distinct patterns: Days 1-4 flat at 50 (blocked, no work completed for 3 days, a serious impediment needs investigation); Day 5 spike from 50 to 60 (scope was added mid-sprint, 10 story points added without removing equivalent work, potentially disrupting sprint commitment); Days 6-10 descent to 15 (team worked productively but the sprint ends with 15 points remaining, sprint goal not fully achieved)
• D. The burndown is perfectly normal, all burndown charts look like this

BURNDOWN PATTERN ANALYSIS: DAYS 1-4, FLAT LINE AT 50 POINTS (MAJOR CONCERN): zero work completed in the first 3 sprint days; CAUSES: blockers preventing work start (environment not set up, dependencies not available, unclear acceptance criteria); team members unavailable or working on non-sprint work; stories not properly refined for development to begin; SCRUM MASTER ACTION: in the Day 2 stand-up, the Scrum master should have identified the impediment immediately; a flat burndown for 3 days in a 10-day sprint means 30% of the sprint is gone without progress; DAY 5 SPIKE FROM 50 TO 60, SCOPE ADDITION: remaining work INCREASES from 50 to 60 = 10 story points were added; this violates sprint integrity: once a sprint begins, the committed scope should remain fixed unless extraordinary circumstances warrant changes; the product owner added work without removing equivalent work; this further risks sprint goal achievement; DAYS 6-10, DESCENT TO 15 REMAINING: the team worked productively (burning down 45 points in 5 days = 9 points/day); however, starting from 60 points with 5 days of productive work (9 points/day × 5 days = 45 points burned), 60−45=15 remaining is logical; SPRINT OUTCOME: 15 of 60 points incomplete (25% of work not delivered); the sprint goal was likely not met; retrospective should address: what caused the 3-day blockage?; why was scope added mid-sprint?; what will prevent recurrence?

• A. Use a network diagram for all three, it's the most comprehensive chart
• B. Use a Gantt chart for all three. Gantt charts serve all schedule communication needs
• C. (1) Gantt chart, the project team needs full task-level detail with durations, progress, and dependencies in a time-scaled format; (2) Milestone chart, the steering committee needs high-level status of key events without task-level detail; (3) Sprint-level Gantt or Kanban board, development leads need current sprint task status at a tactical level
• D. Use a burndown chart for all three, burndown is the most modern schedule tracking tool

CHART SELECTION BY AUDIENCE AND NEED: (1) PROJECT TEAM, ALL 80 ACTIVITIES: BEST CHART: Full Gantt Chart; WHY: shows all 80 activities with planned start/end dates; duration bars show relative length of each activity; dependency arrows show task relationships; percentage-complete bars show current progress; baselines overlay shows variance from plan; allows team members to see how their work connects to others; TOOL: MS Project, Smartsheet, Monday.com; (2) STEERING COMMITTEE, 10 MILESTONES: BEST CHART: Milestone Chart; WHY: executives need strategic visibility, not operational detail; 10 milestones fit on 1 page with RAG status; shows critical dates without overwhelming detail; enables 5-minute governance review instead of 2-hour schedule deep-dive; appropriate detail level matches the governance role; (3) DEVELOPMENT LEADS, CURRENT SPRINT: BEST CHART: Sprint-level Gantt OR Kanban Board; SPRINT GANTT: zoomed to the current sprint (2-week view); shows individual sprint stories/tasks with day-level detail; progress visible at task level; KANBAN BOARD: shows stories in 'To Do / In Progress / Done / Blocked' columns; visual representation of sprint state; immediate visibility into blockers; popular in Scrum teams for daily stand-up use. PRINCIPLE: the right chart matches the information need and the audience's decision-making level.

• A. The project org chart should show only the project manager hierarchy, functional reporting is irrelevant
• B. In a matrix structure, the project manager has no authority over team members, the org chart shows only functional reporting
• C. Matrix structures are too complex to show in an org chart, verbal description is sufficient
• D. A matrix org chart explicitly shows dual reporting lines: solid lines represent the primary reporting relationship (typically to the functional manager for administrative matters, HR, performance review, salary); dotted lines represent the secondary reporting relationship (to the project manager for project work priorities); the dual-reporting structure can create conflicts when functional manager priorities and project manager priorities compete for the same person's time

MATRIX ORG CHART REPRESENTATION: SOLID LINE (administrative authority): shows the functional manager → team member relationship; functional manager handles: performance reviews; salary decisions; vacation approval; HR issues; career development; DOTTED LINE (project authority): shows the project manager → team member relationship; project manager controls: day-to-day work priorities; task assignments; quality standards; delivery timelines; project reporting requirements; VISUAL: a team member in a matrix appears in TWO places: under their functional manager (solid line); under the project manager (dotted line). CONFLICTS IN MATRIX STRUCTURES: TIME ALLOCATION CONFLICTS: functional manager wants team member on a new department initiative; project manager needs them for a critical path activity; the team member is caught in the middle, who takes priority?; RESOLUTION: typically requires escalation to a common superior; some organizations have PMO priority rules; PERFORMANCE REVIEW CONFLICTS: functional manager evaluates performance; but project manager knows 80% of the employee's actual work quality; best practice: PM provides input to functional manager's review; AUTHORITY AMBIGUITY: team members may be uncertain whose instruction to follow when priorities conflict; clear role definitions in the RACI matrix help reduce this confusion. MATRIX VARIANTS: WEAK MATRIX: functional manager has more authority; PM acts more as a coordinator; BALANCED MATRIX: shared authority; STRONG MATRIX: PM has more authority; closer to projectized structure.

• A. Use only the Gantt chart for everything, it is the most comprehensive tracking tool
• B. Gantt: team-level timeline; PERT: probabilistic duration; Milestone: executive-level; Burndown: Agile sprint/release; Network diagram: dependency/critical path; Org chart: team structure. For MOST comprehensive schedule visibility on a complex project: combine Network diagram (for CPM analysis) + Gantt chart (for timeline communication) + milestone chart (for executive reporting), the three together cover analytical, operational, and governance needs
• C. Use PERT for everything, it is the most statistically rigorous tool
• D. The burndown chart provides the most comprehensive visibility, it is the most modern tracking method

CHART USE CASE FRAMEWORK: GANTT CHART: BEST FOR: team-level schedule communication; showing all activities with durations, progress, and dependencies in a time-scaled format; AUDIENCE: project team, work-stream leads; WHEN TO USE: throughout execution for operational schedule tracking; PERT CHART/ESTIMATING: BEST FOR: estimating activity durations when uncertainty is HIGH; producing probabilistic completion forecasts; AUDIENCE: PM, planners, sponsors who want probability-based forecasts; WHEN TO USE: during planning for novel activities; when schedule risk quantification is needed. MILESTONE CHART: BEST FOR: executive and steering committee reporting; showing high-level project state without operational detail; AUDIENCE: sponsor, steering committee, board; WHEN TO USE: monthly governance reporting; phase gate preparation. BURNDOWN CHART: BEST FOR: Agile sprint and release progress tracking; showing remaining work vs. ideal; AUDIENCE: Agile development team, product owner; WHEN TO USE: during sprints (sprint burndown) and across releases (release burndown). NETWORK DIAGRAM: BEST FOR: dependency analysis; critical path calculation (CPM); float analysis; schedule compression planning; AUDIENCE: PM, planners, schedule analysts; WHEN TO USE: during planning to identify critical path; when schedule compression options must be evaluated. ORGANIZATIONAL CHART: BEST FOR: showing team structure, reporting relationships, and authority; AUDIENCE: all project participants, new team members, stakeholders; WHEN TO USE: created in initiation; updated when team structure changes. COMPREHENSIVE SCHEDULE VISIBILITY COMBINATION: NETWORK DIAGRAM: tells you WHICH activities have zero float and MUST be protected; calculates the critical path; enables schedule compression analysis; GANTT CHART: shows ALL activities in time sequence; tracks progress; communicates the schedule to the team; MILESTONE CHART: gives executives the governance view (are key events on track?); the three charts work at three different levels of analysis: network = analytical; Gantt = operational; milestone = governance.