PMBOK 7 - Schedule Manage - Free Practice Quiz

Question 1 of 150

A PM is sequencing project activities using the Precedence Diagramming Method (PDM). What does PDM use to represent activities and their logical relationships?

A A spreadsheet with dates and durations B Nodes (boxes) represent activities and arrows represent the logical dependencies between them — this activity-on-node (AON) notation is the standard method used in modern project scheduling C A Gantt chart with milestone markers D Arrows represent activities and nodes represent events

1 / 150

Question 2 of 150

In PDM, what are the four types of logical relationships between activities?

A Internal, External, Hard, Soft B Sequential, Parallel, Mandatory, Discretionary C Start-Start, Start-Finish, Finish-Start, Finish-Finish D Finish-to-Start (FS): successor starts after predecessor finishes; Start-to-Start (SS): successor starts when predecessor starts; Finish-to-Finish (FF): successor finishes when predecessor finishes; Start-to-Finish (SF): successor finishes when predecessor starts

2 / 150

Question 3 of 150

Which dependency type is MOST commonly used in project scheduling and why?

A Finish-to-Start (FS) because it represents the most natural workflow — one activity must be completed before the next can begin; approximately 90% of dependencies in typical project networks are FS relationships B Start-to-Finish because it provides the most flexibility C Finish-to-Finish because it ensures quality D Start-to-Start because it enables parallel work

3 / 150

Question 4 of 150

A PM has two activities: 'Pour concrete' and 'Cure concrete.' The curing must begin immediately when pouring finishes. What dependency type and what lead/lag should be applied?

A Finish-to-Start (FS) with zero lag — the curing begins exactly when pouring finishes; no delay is needed because curing is the natural next step in the sequence B FF with 5-day lag C SS with 2-day lead D SF with 1-day lead

4 / 150

Question 5 of 150

A PM uses a Start-to-Start (SS) relationship between 'Lay pipe' and 'Backfill trench.' The backfilling can begin 3 days after pipe laying starts. How is this modeled?

A SS with a 3-day lag — the SS relationship means the successor starts when the predecessor starts, and the 3-day lag delays the successor's start until 3 days after the predecessor has begun, allowing enough pipe to be laid before backfilling commences B FF with 3-day lead C SS with 3-day lead D FS with 3-day lag

5 / 150

Question 6 of 150

What is the difference between lead time and lag time in PDM?

A Lead time accelerates the successor activity (allows it to start before the dependency would normally permit), while lag time delays the successor activity (forces a waiting period after the dependency is satisfied) — lead compresses the schedule, lag extends it B Lead is used in agile and lag is used in waterfall C Lead applies to critical activities and lag applies to non-critical activities D Lead and lag are the same concept

6 / 150

Question 7 of 150

A PM applies a 5-day lead to a Finish-to-Start relationship between Activity A (10 days) and Activity B. What does this mean for Activity B's start?

A Activity B takes 5 fewer days to complete B Activity B starts 5 days BEFORE Activity A finishes — the lead allows Activity B to overlap with the last 5 days of Activity A, compressing the overall schedule by 5 days compared to a pure sequential FS relationship C Activity B starts 5 days after Activity A finishes D Activity A is shortened by 5 days

7 / 150

Question 8 of 150

A PM has a Finish-to-Start dependency between 'Submit document' and 'Receive approval.' The approval process takes a minimum of 10 business days. How should the PM model this waiting period?

A Apply a 10-day lag to the FS relationship — the lag represents the mandatory waiting period between the predecessor's completion and the successor's start, accurately modeling the external delay without inflating any activity's duration B Use a lead of negative 10 days C Increase the duration of 'Submit document' by 10 days D Create a separate 10-day activity called 'Wait for approval'

8 / 150

Question 9 of 150

What is the difference between mandatory dependencies and discretionary dependencies in PDM?

A Mandatory dependencies apply to critical path activities only B Discretionary dependencies are never used in project scheduling C Mandatory dependencies (hard logic) are inherent to the nature of the work and cannot be changed (e.g., foundation before framing), while discretionary dependencies (soft logic/preferred logic) reflect best practices or team preferences and CAN be modified during schedule optimization D Mandatory dependencies are set by the PM and discretionary dependencies are set by the team

9 / 150

Question 10 of 150

A PM identifies an external dependency on a government permit that must be obtained before construction begins. What type of dependency is this and how should it be managed?

A External dependencies do not affect the project schedule B The PM should convert this to an internal dependency C This is a discretionary dependency that can be removed D This is a mandatory external dependency — it is imposed by factors outside the project and cannot be changed; the PM should identify it early, build appropriate lag time into the schedule, monitor the external process, and develop contingency plans for delays

10 / 150

Question 11 of 150

A PM draws a network diagram and discovers that Activity C has both a Finish-to-Start relationship with Activity A and a Start-to-Start relationship with Activity B. Activity A finishes on Day 10 and Activity B starts on Day 8. When is the EARLIEST Activity C can start?

A Day 9, the average of 8 and 10 B Day 10 — when multiple dependencies constrain an activity, the LATEST of all predecessor constraints determines the early start; the FS from A requires waiting until Day 10, which is later than the SS from B on Day 8 C Day 1 because Activity C has no duration constraint D Day 8 because of the SS with Activity B

11 / 150

Question 12 of 150

A PM uses a Finish-to-Finish (FF) relationship between 'Write code' and 'Write unit tests.' What does this mean operationally?

A Testing must finish before coding starts B Coding must finish before testing starts C Unit testing must finish when (or after) coding finishes — the FF relationship means the successor cannot complete until the predecessor completes, but both can be in progress simultaneously; this is common when two parallel activities must end together D Both activities must start at the same time

12 / 150

Question 13 of 150

A PM encounters the rarely-used Start-to-Finish (SF) dependency type. In which scenario would SF be MOST appropriate?

A SF is the default relationship in agile projects B SF is used in just-in-time (JIT) scenarios where the successor's finish is controlled by the predecessor's start — for example, a new security system (predecessor) starts and the old security system (successor) finishes; the old system stays active UNTIL the new one starts C SF is never used in modern project management D SF is used when the schedule needs to be compressed

13 / 150

Question 14 of 150

A PM is building a network diagram for a software project. The testing team says they can begin writing test cases (Activity B) while requirements are still being finalized (Activity A), but they need at least 3 days of requirements work completed first. What is the best way to model this?

A Create a dummy activity between A and B B FS with a 3-day lead on a separate finish dependency C Start-to-Start (SS) with a 3-day lag — this allows test case writing to begin 3 days after requirements work starts, enabling parallel execution while ensuring enough requirements are defined to support meaningful test case development D FS with no modifications

14 / 150

Question 15 of 150

A PM applies a 2-day lead to every FS relationship in the project to compress the schedule. What risk does this introduce?

A No risk; leads always improve the schedule B Excessive lead time increases rework risk — when successor activities start before predecessors are fully complete, changes in the predecessor's final deliverables may invalidate work already started on the successor, creating rework cycles that can ultimately delay the project more than the lead time saved C The PMO must approve all lead time usage D Leads only work on non-critical path activities

15 / 150

Question 16 of 150

In a network diagram, a path goes: A(5d) -> B(3d) -> C(7d) -> D(4d). All relationships are FS with zero lag. What is the total duration of this path?

A 4.75 days (average) B 15 days C 7 days (longest activity only) D 19 days — the total path duration is the sum of all activity durations on the path: 5 + 3 + 7 + 4 = 19 days, assuming all relationships are Finish-to-Start with no lead or lag

16 / 150

Question 17 of 150

A PM has Activity A (8 days) with an FS relationship to Activity B, but with a 3-day lag. If Activity A starts on Day 1 and finishes on Day 8, when does Activity B start?

A Day 12 — Activity A finishes on Day 8, and the 3-day lag adds a mandatory waiting period, so Activity B cannot start until Day 8 + 3 + 1 = Day 12 (or equivalently, 3 working days after Day 8) B Day 11 C Day 5 D Day 9

17 / 150

Question 18 of 150

A PM modifies a Finish-to-Start relationship from FS + 0 lag to FS with a 5-day lead. How does this affect the network path duration?

A Path duration decreases by 5 days — a lead allows the successor to start 5 days before the predecessor finishes, overlapping the two activities and compressing the schedule; the effective path contribution of this relationship becomes the predecessor duration minus 5 days B The path is removed from the network C Path duration increases by 5 days D Path duration is unchanged

18 / 150

Question 19 of 150

A PM creates a project schedule with 200 activities. During review, 15 activities have no predecessors and 12 activities have no successors. Besides the project start and end milestones, is this acceptable?

A The schedule is valid as long as the critical path is defined B Only activities with no predecessors are a problem C No — every activity except the project start milestone should have at least one predecessor, and every activity except the project end milestone should have at least one successor; open-ended activities ('danglers') indicate missing logic that will produce an unreliable schedule D Yes, open-ended activities are normal in large projects

19 / 150

Question 20 of 150

A PM is evaluating whether to model a dependency as mandatory FS or discretionary SS to enable parallelism. What criteria should guide this decision?

A Always use SS to save time B If the physical or contractual nature of the work absolutely requires sequential execution, use mandatory FS; if the sequential relationship is based on best practice or preference but the work COULD overlap safely, use discretionary SS — the key question is whether overlap introduces unacceptable risk or rework C The sponsor decides which dependency type to use D Use FS for internal activities and SS for external activities

20 / 150

Question 21 of 150

A network diagram shows: Activity X has an SS relationship with Activity Y (SS + 2-day lag), and Activity Y has an FF relationship with Activity Z (FF + 1-day lag). Activity X starts on Day 1 and has a duration of 10 days. Activity Y has a duration of 8 days. When does Activity Z finish at the EARLIEST?

A Day 10 B Day 8 C Day 15 D Day 12 — Activity Y starts on Day 3 (SS + 2-day lag from Day 1) and finishes on Day 10 (3 + 8 - 1 = 10); Activity Z must finish no earlier than Day 10 + 1-day lag = Day 11; however recalculating: Y starts Day 3, lasts 8 days, so Y finishes end of Day 10; FF + 1-day lag means Z finishes end of Day 11

21 / 150

Question 22 of 150

A PM identifies that painting interior walls (Activity B) can start 2 days before plastering (Activity A) finishes, because the plaster in earlier rooms will be dry by then. The PM models this as FS with a 2-day lead. A risk event occurs and plastering takes 5 extra days. How does this affect painting?

A Painting is not affected since it already started B Painting finishes 5 days early to compensate C The lead automatically adjusts to absorb the delay D Painting may need to pause or rework may occur — the lead assumed plaster would be dry on schedule; the 5-day delay means rooms that were expected to be dry are not ready, potentially requiring the painting crew to idle or repaint rooms where plaster was not fully cured

22 / 150

Question 23 of 150

A PM builds a network diagram and notices a circular dependency: Activity A depends on Activity B, which depends on Activity C, which depends on Activity A. What does this indicate?

A A logical error — circular dependencies (loops) are invalid in PDM because they create an infinite cycle with no calculable start or finish dates; the PM must break the loop by redefining the relationship, splitting an activity, or identifying which dependency is incorrect B Circular dependencies are acceptable in agile scheduling C All three activities should be merged into one D A valid iterative process that the scheduling tool will handle

23 / 150

Question 24 of 150

A PM has a project with 50 activities and needs to determine if the schedule can be compressed. The PM examines all discretionary dependencies. Why are discretionary dependencies specifically targeted for schedule compression?

A Mandatory dependencies cannot be visualized in scheduling tools B Discretionary dependencies have zero float by definition C Discretionary dependencies are always on the critical path D Discretionary dependencies represent preferred but not mandatory sequences — they can be modified, relaxed, or removed to enable fast-tracking (parallel execution of previously sequential activities) without violating physical or contractual constraints

24 / 150

Question 25 of 150

A PM presents a network diagram to the sponsor. The sponsor asks why some arrows are thicker than others. The PM explains that thick arrows represent the critical path. The sponsor then asks: 'What happens if we add a 15-day lag to a non-critical path activity?' What is the PM's BEST response?

A Lag can only be added to critical path activities B Nothing happens because it is not on the critical path C Adding a 15-day lag to a non-critical path activity consumes float — if the lag exceeds the available total float on that path, the path becomes the new critical path, potentially extending the project's overall duration; lag always needs to be evaluated against available float D The sponsor cannot modify the network diagram

25 / 150

Question 26 of 150

What is the critical path in a project network?

A The longest path through the network diagram that determines the shortest possible project duration — any delay to a critical path activity directly delays the project finish date because critical path activities have zero total float B The path chosen by the project sponsor C The path with the most activities D The path with the most expensive activities

26 / 150

Question 27 of 150

A PM performs a forward pass through the network diagram. What does the forward pass calculate?

A The cost of each activity B The total float for each activity C The earliest start (ES) and earliest finish (EF) for each activity — the forward pass moves from the project start to the project end, calculating the earliest each activity can begin and complete based on its predecessors and durations D The latest start and finish dates for each activity

27 / 150

Question 28 of 150

A PM performs a backward pass through the network diagram. What does the backward pass calculate?

A The latest start (LS) and latest finish (LF) for each activity — the backward pass moves from the project end to the project start, calculating the latest each activity can begin and complete without delaying the project end date B The budget allocation per activity C The earliest start and finish dates D The resource requirements for each activity

28 / 150

Question 29 of 150

Given the following network: A(3d) -> B(5d) -> D(4d) and A(3d) -> C(2d) -> D(4d). All FS with zero lag. What is the critical path and project duration?

A A-B-C-D with duration 14 days B A-B-D with duration 12 days — Path A-B-D = 3+5+4 = 12 days; Path A-C-D = 3+2+4 = 9 days; the longest path (12 days) is the critical path and determines the minimum project duration C A-C-D with duration 9 days D B-D with duration 9 days

29 / 150

Question 30 of 150

In a network with ES=5, EF=12, LS=8, LF=15 for Activity X, what is Activity X's total float?

A 7 days B 3 days — Total Float = LS - ES = 8 - 5 = 3 days (or equivalently LF - EF = 15 - 12 = 3 days); this means Activity X can be delayed up to 3 days without affecting the project end date C 20 days D 0 days

30 / 150

Question 31 of 150

A project has the following network (all FS, zero lag): Start -> A(4) -> C(6) -> End; Start -> B(3) -> C(6) -> End; Start -> B(3) -> D(5) -> End. What is the critical path?

A B-C at 9 days B B-D at 8 days C A-B-C-D at 18 days D A-C at 10 days — Path A-C = 4+6 = 10 days; Path B-C = 3+6 = 9 days; Path B-D = 3+5 = 8 days; the longest path (10 days) is the critical path

31 / 150

Question 32 of 150

During project execution, Activity E on the critical path is completed 2 days early. What happens to the project end date?

A The project end date moves 2 days earlier automatically B Only the successor activity benefits, not the project end date C The project end date never changes regardless of activity performance D The project end date MAY move earlier, but only if no other path has become critical — saving 2 days on the original critical path may cause a previously near-critical path to become the new critical path, limiting the actual schedule benefit

32 / 150

Question 33 of 150

Can a project have more than one critical path simultaneously?

A No, there can only be one critical path B Yes — when two or more paths through the network have the same longest duration, the project has multiple critical paths; this increases project risk because a delay on ANY of these paths will extend the project end date C Multiple critical paths cancel each other out D Only agile projects can have multiple critical paths

33 / 150

Question 34 of 150

A PM calculates that the critical path is 60 working days. The sponsor requires project completion in 50 working days. What is the schedule variance?

A The project schedule shows a 10-day gap — the critical path (60 days) exceeds the required deadline (50 days) by 10 days; the PM must compress the critical path by at least 10 days through crashing, fast-tracking, scope reduction, or a combination B The variance is zero because the project has not started C The project is ahead of schedule by 10 days D Schedule variance cannot be calculated before execution begins

34 / 150

Question 35 of 150

A PM performs a forward pass and calculates ES=0 for the first activity. At a merge point where Activity B (EF=10) and Activity C (EF=14) both feed into Activity D, what is Activity D's Early Start?

A 14 days — at a merge point, the Early Start of the successor is the LATEST Early Finish among all predecessors; since Activity C finishes later (Day 14 > Day 10), Activity D must wait for C and cannot start until Day 14 B 12 days (average) C 10 days D 0 days

35 / 150

Question 36 of 150

During a backward pass, Activity E feeds into both Activity F (LS=20) and Activity G (LS=15). What is Activity E's Late Finish?

A 15 days — at a burst point during the backward pass, the Late Finish of the predecessor is the EARLIEST Late Start among all successors; Activity E must finish in time for its earliest successor (G at Day 15) B 17.5 days (average) C The backward pass does not apply at burst points D 20 days

36 / 150

Question 37 of 150

A network has 6 paths. Path durations are: 22, 25, 25, 18, 20, 24 days. How many critical paths exist and what is the project duration?

A Two critical paths at 25 days each — both 25-day paths are critical because they share the longest duration; activities on both paths have zero float and any delay on either path extends the project beyond 25 days B One critical path at 25 days C Six critical paths D Three near-critical paths

37 / 150

Question 38 of 150

A PM identifies a 'near-critical path' with only 2 days of total float while the critical path has zero float. Why should the PM monitor this near-critical path?

A Near-critical paths automatically become critical paths B Near-critical paths do not exist in CPM C With only 2 days of float, any delay exceeding 2 days on the near-critical path would make it the new critical path, potentially extending the project; near-critical paths represent high schedule risk because small variances can shift the critical path D Near-critical paths only matter in agile projects

38 / 150

Question 39 of 150

A PM calculates the critical path using CPM but does not consider resource constraints. The schedule shows a 40-day duration. After resource leveling, the duration extends to 52 days. What explains this increase?

A CPM calculates the critical path based on activity durations and logical dependencies only — resource leveling introduces resource constraints that may delay activities because the same resource is needed for parallel activities, creating a 'resource critical path' that is longer than the logical critical path B CPM calculations were incorrect C The PM should ignore resource constraints D Resource leveling always doubles the project duration

39 / 150

Question 40 of 150

A PM uses the formula EF = ES + Duration - 1 in one schedule and EF = ES + Duration in another. Why might these differ?

A The formulas apply to different activity types B The difference depends on the scheduling convention: if ES is the start of the first day (day-number convention), EF = ES + Duration - 1 (e.g., start Day 1, 5-day activity, finish Day 5); if ES represents elapsed time from zero, EF = ES + Duration (e.g., start time 0, 5 days, finish time 5) C The minus-one version is only for agile projects D One formula is incorrect

40 / 150

Question 41 of 150

A network diagram has: A(3) -> B(4) -> E(2); A(3) -> C(6) -> E(2); D(5) -> E(2). All FS, zero lag. What is the critical path?

A A-C at 9 days B A-C-E at 11 days — Path A-B-E = 3+4+2 = 9; Path A-C-E = 3+6+2 = 11; Path D-E = 5+2 = 7; the longest path is A-C-E at 11 days C A-B-E at 9 days D D-E at 7 days

41 / 150

Question 42 of 150

A PM presents the critical path analysis to the team. A team member asks: 'Does the critical path ever change during the project?' What is the correct answer?

A The critical path only changes if the scope changes B Yes — the critical path can shift during execution when activities finish earlier or later than planned, when changes are approved, or when risks materialize; the PM must recalculate the network regularly and monitor near-critical paths for potential critical path shifts C No, the critical path is fixed at planning D Critical path changes require sponsor approval

42 / 150

Question 43 of 150

A project has three parallel paths merging into a final activity. Path A = 20 days (critical), Path B = 18 days (2 days float), Path C = 15 days (5 days float). A risk event adds 4 days to Path B. What happens?

A All three paths become critical B Path B becomes the new critical path at 22 days — the 4-day delay exceeds Path B's 2-day float, making Path B (22 days) longer than Path A (20 days); the project duration extends from 20 to 22 days and the PM must now focus on compressing Path B C Path B absorbs the delay with its float D Nothing changes since Path A is still critical

43 / 150

Question 44 of 150

A PM is asked to calculate the Early Start (ES) for Activity H. Activity H has three predecessors: E (EF=12), F (EF=15), G (EF=9). All are FS with zero lag. What is H's ES?

A 36 (sum of all predecessors) B 9 (earliest of all predecessors) C 12 (median value) D 15 — Activity H cannot start until ALL predecessors are complete; the ES at a merge point equals the MAXIMUM Early Finish among all predecessors: max(12, 15, 9) = 15

44 / 150

Question 45 of 150

After performing forward and backward passes, a PM finds that Activity J has ES=10, EF=16, LS=10, LF=16. What can be concluded about Activity J?

A Activity J is on the critical path — Total Float = LS - ES = 10 - 10 = 0 days; activities with zero total float are on the critical path because any delay will directly impact the project end date B Activity J has 6 days of float C Activity J has been completed D Activity J is not on the critical path

45 / 150

Question 46 of 150

A PM calculates that Activity K has a total float of -3 days. What does negative float indicate?

A The activity has 3 extra days of flexibility B Negative float is impossible and indicates a calculation error C The activity should be removed from the schedule D Negative float means the project is already behind schedule by 3 days relative to a constraint — the project's calculated end date exceeds a mandatory deadline by 3 days; the PM must compress the critical path by at least 3 days to meet the constraint

46 / 150

Question 47 of 150

A PM uses the Critical Path Method on a project with high uncertainty in activity durations. A colleague suggests using PERT instead. What advantage does PERT offer over CPM for uncertain durations?

A PERT is only used for cost estimation B PERT uses three-point estimates (optimistic, most likely, pessimistic) to calculate a weighted average duration and standard deviation for each activity, providing a probabilistic range for the project duration rather than CPM's single deterministic estimate C PERT eliminates the need for a network diagram D PERT uses the same single-point estimates as CPM

47 / 150

Question 48 of 150

Using PERT, an activity has optimistic duration = 4 days, most likely = 7 days, pessimistic = 16 days. What is the PERT expected duration?

A 8 days — PERT expected duration = (O + 4M + P) / 6 = (4 + 4x7 + 16) / 6 = (4 + 28 + 16) / 6 = 48 / 6 = 8 days; the formula weights the most likely estimate four times because it is most probable B 9 days C 7 days D 27 days

48 / 150

Question 49 of 150

Using PERT, the critical path has a total expected duration of 50 days with a path standard deviation of 5 days. What is the probability that the project will finish in 55 days or less?

A 100% B 50% C Approximately 84% — 55 days is one standard deviation above the mean (50 + 5 = 55); using the normal distribution, approximately 84.1% of outcomes fall at or below one standard deviation above the mean D 95%

49 / 150

Question 50 of 150

A PM creates a schedule with 12 activities. After CPM analysis, only 3 activities are on the critical path. The sponsor says: 'Since 9 activities are non-critical, we can cut their resources.' Why is this a risky approach?

A Cutting resources on non-critical activities increases their durations, which consumes float — if enough float is consumed, these activities become critical, potentially creating new critical paths and extending the project; non-critical activities still need adequate resources to maintain their float buffer B Only the PM can allocate resources, not the sponsor C Resource cuts do not affect activity durations D Non-critical activities don't need resources

50 / 150

Question 51 of 150

A PM is asked to crash the project schedule. Activity L is on the critical path with a normal duration of 10 days (cost $5,000) and a crash duration of 7 days (cost $8,000). What is the crash cost per day?

A $5,000 per day B $1,000 per day — Crash cost per day = (Crash cost - Normal cost) / (Normal duration - Crash duration) = ($8,000 - $5,000) / (10 - 7) = $3,000 / 3 = $1,000 per day C $3,000 per day D $800 per day

51 / 150

Question 52 of 150

A PM must reduce the project duration by 5 days. Three critical path activities can be crashed: X (cost $800/day, max 3 days), Y (cost $1,200/day, max 4 days), Z (cost $600/day, max 2 days). What is the optimal crashing sequence?

A Crash Z first (2 days at $600/day = $1,200), then X (3 days at $800/day = $2,400) for a total of 5 days at $3,600 — always crash the lowest cost-per-day activity first until its maximum reduction is reached, then move to the next cheapest B Crash X first because it has moderate cost and availability C Crash all three equally D Crash Y first because it has the most available days

52 / 150

Question 53 of 150

After crashing Activity Z by 2 days on the critical path, the PM recalculates the network and discovers that a previously non-critical path is now the critical path. What should the PM do?

A Continue crashing Activity Z B Reverse the crashing of Activity Z C Ignore the new critical path D Stop and reassess — the critical path has shifted, so further crashing on the original path will not reduce the project duration; the PM must now crash activities on the NEW critical path, and may need to crash activities on BOTH paths simultaneously if they are now equal in length

53 / 150

Question 54 of 150

What is the difference between crashing and fast-tracking as schedule compression techniques?

A They are the same technique with different names B Crashing is used only in waterfall and fast-tracking only in agile C Crashing increases the schedule and fast-tracking decreases it D Crashing adds resources to critical path activities to reduce their duration (increases cost), while fast-tracking performs sequential critical path activities in parallel by modifying dependencies (increases risk) — crashing trades cost for time, fast-tracking trades risk for time

54 / 150

Question 55 of 150

A PM fast-tracks two critical path activities by changing their FS relationship to SS with a 3-day lag. The activities originally had a combined sequential duration of 20 days (Activity M = 8 days, Activity N = 12 days). What is the new combined duration for this portion of the path?

A 12 days B 20 days (unchanged) C 8 days D 15 days — with SS + 3-day lag, Activity N starts 3 days after Activity M starts; Activity N finishes on day 3 + 12 = day 15; since Activity M finishes on day 8 (which is before day 15), the path duration for this segment is 15 days, saving 5 days compared to the original 20-day sequential plan

55 / 150

Question 56 of 150

What is the fundamental difference between Total Float and Free Float?

A They are two names for the same concept B Free Float is always greater than Total Float C Total Float is the amount of time an activity can be delayed without delaying the PROJECT END DATE, while Free Float is the amount of time an activity can be delayed without delaying any SUCCESSOR activity's early start — free float is always less than or equal to total float D Total Float applies to critical activities and Free Float applies to non-critical activities

56 / 150

Question 57 of 150

How is Free Float calculated for an activity?

A Free Float = LS - ES B Free Float = Earliest ES of all immediate successors - EF of the current activity — it measures the gap between when the activity finishes and when the earliest successor needs to start C Free Float = LF - LS D Free Float = Total Float minus 1

57 / 150

Question 58 of 150

Activity P has ES=5, EF=12, LS=9, LF=16. Its only successor Activity Q has ES=15. What are Activity P's Total Float and Free Float?

A TF = 4, FF = 3 — Total Float = LS - ES = 9 - 5 = 4 days; Free Float = ES(Q) - EF(P) = 15 - 12 = 3 days; Activity P can slip 3 days without affecting Q, and up to 4 days without affecting the project end date B TF = 3, FF = 4 C TF = 0, FF = 0 D TF = 4, FF = 4

58 / 150

Question 59 of 150

On a non-critical path, three sequential activities each have Total Float = 8 days. A team member assumes each activity can be independently delayed by 8 days. Why is this assumption incorrect?

A Total Float cannot be 8 days for three activities B Sequential activities always have zero float C Total Float on a sequential path is SHARED among all activities on that path — if the first activity uses all 8 days of float, the remaining activities on the path have zero float remaining and become critical; the 8 days is a path-level budget, not an activity-level budget D The assumption is correct; each activity has independent float

59 / 150

Question 60 of 150

Why is Free Float particularly important for resource scheduling decisions?

A Free Float determines the critical path for resources B Free Float determines which activities need the most resources C Free Float is not used in resource scheduling D Free Float represents the delay an activity can tolerate without affecting ANY other activity — resource managers can safely delay activities within their free float without cascading impacts, making free float the 'safe' buffer for resource optimization decisions

60 / 150

Question 61 of 150

A network has: A(4) -> C(3) and B(6) -> C(3). A starts Day 1, B starts Day 1. What is Activity A's Free Float?

A 2 days — A finishes Day 4 (EF=4), B finishes Day 6 (EF=6); C's ES = max(4,6) = 6; A's Free Float = ES(C) - EF(A) = 6 - 4 = 2 days; A can slip 2 days without delaying C because C must wait for B anyway B 4 days C 6 days D 0 days

61 / 150

Question 62 of 150

In the same network as the previous question, if Activity A has Total Float = 2 days and Free Float = 2 days, what does it mean when TF equals FF?

A The activity has no float B The calculation must be wrong C The activity is on the critical path D All of Activity A's float is 'private' — delaying A by up to 2 days affects neither its successors nor the project end date; when TF = FF, the activity's delay is fully absorbed without any downstream impact

62 / 150

Question 63 of 150

Can an activity on the critical path have Free Float greater than zero?

A No — critical path activities have zero Total Float, and since Free Float cannot exceed Total Float (FF <= TF), critical path activities also have zero Free Float B Free Float does not apply to critical path activities C Yes, critical path activities always have high free float D Only the last critical path activity can have free float

63 / 150

Question 64 of 150

A PM analyzes the schedule and finds Activity R with TF = 10 days and FF = 0 days. What does this tell the PM about Activity R's position in the network?

A Activity R is on the critical path B Activity R is on a non-critical path (TF=10) but is immediately followed by its successor with no gap (FF=0) — any delay to R will immediately push its successor, even though the path has 10 days of shared float before the project end date is affected C The calculation is incorrect because FF cannot be 0 when TF is 10 D Activity R can be delayed 10 days without any impact

64 / 150

Question 65 of 150

A PM is resource leveling and needs to delay one of two parallel activities. Activity S has TF=5, FF=5. Activity T has TF=5, FF=0. Which activity should the PM delay and why?

A Delay both activities equally B Delay either one since both have TF=5 C Delay Activity T because it has more successors D Delay Activity S because its Free Float of 5 days means it can be delayed without affecting any successor — delaying Activity T (FF=0) would immediately push T's successor, potentially causing a cascade of delays even though the project end date has buffer

65 / 150

Question 66 of 150

What is 'Project Float' (also called Project Buffer or Project Slack)?

A The float of the longest activity B Project Float is the difference between the externally imposed project completion date and the calculated project end date from the critical path — it represents the overall schedule buffer available to the entire project before missing the deadline C The sum of all activities' total float D The average float across all paths

66 / 150

Question 67 of 150

A PM uses Critical Chain Method (CCM) instead of traditional CPM. How does CCM handle float differently?

A CCM removes individual activity safety buffers and aggregates them into project buffers at the end of the critical chain and feeding buffers where non-critical chains merge — this prevents Parkinson's Law (work expanding to fill available time) and Student Syndrome (starting late because of perceived buffer) B CCM doubles all float values C CCM eliminates all float from the schedule D CCM and CPM handle float identically

67 / 150

Question 68 of 150

In Critical Chain scheduling, what is a 'feeding buffer' and where is it placed?

A A buffer for feeding resource information to the team B A feeding buffer is placed at the point where a non-critical chain of activities merges into the critical chain — it protects the critical chain from delays in non-critical paths, similar to how total float on a non-critical path prevents it from delaying the project in CPM C A buffer added to every activity on the critical chain D A buffer added at the beginning of the project

68 / 150

Question 69 of 150

Activity U has TF = 6 and FF = 4. If Activity U is delayed by 5 days, what is the impact?

A No impact at all since 5 < 6 (within total float) B Only the project end date is delayed, not the successor C The project end date is NOT affected (5 days < TF of 6), but Activity U's immediate successor IS delayed by 1 day (5 days delay - 4 days FF = 1 day push to successor) — the successor must now use 1 day of its own float D Both the successor and project end date are delayed

69 / 150

Question 70 of 150

A schedule shows Path 1 (critical): A(5)-B(8)-C(6) = 19 days. Path 2: D(4)-E(3)-C(6) = 13 days. What is the Total Float and Free Float for Activity D?

A TF = 6, FF = 0 — TF = 19 - 13 = 6 days for the entire non-critical path; Activity D's FF depends on its successor E; since D feeds directly into E with no gap (both on the same sequential chain), FF = ES(E) - EF(D); E starts immediately after D, so FF = 0 B TF = 6, FF = 6 C TF = 0, FF = 6 D TF = 6, FF = 3

70 / 150

Question 71 of 150

In the same network, what is Activity E's Free Float?

A 3 days B 6 days — Activity E finishes on Day 7 (ES=4, duration=3, EF=7); Activity C's ES is determined by the critical path predecessor B which finishes on Day 13; so FF(E) = ES(C) - EF(E) = 13 - 7 = 6 days; E can slip 6 days without delaying C because C waits for B C 13 days D 0 days

71 / 150

Question 72 of 150

A PM notices that the last activity before a merge point on a non-critical path often has the highest Free Float. Why is this?

A The last activity before a merge point absorbs all the float between when it finishes and when the merge successor can start (constrained by the critical path predecessor) — earlier activities on the same path have zero free float because they directly feed the next activity in the chain B Free Float accumulates from the beginning of the path C It is a coincidence with no structural explanation D All activities on a non-critical path have equal free float

72 / 150

Question 73 of 150

A PM uses a scheduling tool that shows a 'float histogram' — a bar chart showing the distribution of float across all activities. Most activities have zero float, and a few have large float values. What does this distribution suggest about the schedule?

A Float histograms provide no useful information B Activities with large float should be removed from the schedule C The schedule is well-balanced D The schedule has a dominant critical path with few parallel alternatives — most activities are critical or near-critical (zero or low float), indicating high schedule risk; a healthier schedule would show more activities with moderate float, suggesting multiple parallel paths provide buffer

73 / 150

Question 74 of 150

A team lead asks: 'If I start my activity on its Late Start date instead of its Early Start date, what happens to its float?' How should the PM respond?

A Float is unaffected by when the activity actually starts B The float doubles because late start gives extra flexibility C Starting late increases float for other activities D The activity's remaining total float becomes zero — starting on the Late Start date means the activity has consumed all its float; any further delay will push the project end date; the activity has effectively joined the critical path in terms of urgency

74 / 150

Question 75 of 150

A PM calculates float for all activities but forgets to account for a 5-day lag on one FS relationship. How does adding this lag affect float calculations?

A Lag only affects free float, not total float B Lag does not affect float calculations C Adding a 5-day lag increases the effective duration of that path segment by 5 days, which reduces the total float of all activities on that path by 5 days — lag consumes float just like increased activity duration does, potentially making a non-critical path critical D Lag increases float by 5 days

75 / 150

Question 76 of 150

A PM applies resource leveling to the schedule. Before leveling, Activity V had TF=8 and FF=3. After leveling, Activity V is delayed to resolve a resource conflict. How are Activity V's float values affected?

A Resource leveling always increases float B Float is irrelevant after resource leveling C Resource leveling may reduce or eliminate Activity V's float — if V is delayed to resolve a resource conflict, its actual start moves later, consuming float; the PM must recalculate the network after leveling because float values change whenever activities are rescheduled D Float values are unchanged after resource leveling

76 / 150

Question 77 of 150

A schedule baseline shows 45 activities. Of these, 12 are on the critical path (zero float), 8 have TF between 1-5 days, 15 have TF between 6-15 days, and 10 have TF > 15 days. The PM wants to assign a schedule risk rating. Which metric provides the best risk indicator?

A The ratio of critical and near-critical activities to total activities — 20 of 45 activities (44%) have 5 days or less of float, indicating high schedule risk because nearly half the schedule has minimal flexibility; this 'criticality index' is more informative than counting only zero-float activities B The maximum float value in the schedule C The average float across all activities D The number of critical path activities only

77 / 150

Question 78 of 150

A PM reports that the project's 'schedule sensitivity index' for a particular path is 0.85. What does this mean?

A The path is critical 85% of the time in Monte Carlo simulation runs — a sensitivity index of 0.85 means that in probabilistic schedule analysis, this path was the longest (critical) path in 85% of simulation iterations, indicating it is a high-risk path even if it is not always the deterministic critical path B The path has 85% of the project's total float C 85% of the path's activities are on the critical path D The path is 85% complete

78 / 150

Question 79 of 150

A PM is explaining float to a non-technical sponsor. The sponsor asks: 'If we have 10 days of float on Activity W, can we reassign Activity W's resources to another project for 10 days and then bring them back?' What should the PM advise?

A Yes, 10 days of float means complete flexibility B Resources cannot be moved between projects C The PM should caution against this — while 10 days of TF means the project end date is safe, the PM must check FF (which may be less than 10, causing successor delays), consider resource remobilization costs and risks, and recognize that using all float eliminates schedule buffer for future uncertainties D The sponsor should add 10 more days to the project

79 / 150

Question 80 of 150

A project has Activities A(5), B(3), C(7), D(4). Dependencies: A->C, B->C, C->D. All FS zero lag. What is Activity B's Total Float and Free Float?

A TF = 2, FF = 0 B TF = 0, FF = 0 C TF = 5, FF = 3 D TF = 2, FF = 2 — Critical path: A(5)->C(7)->D(4) = 16 days; Path B->C->D = 3+7+4 = 14 days; B's TF = 16-14 = 2; B's FF: C's ES = max(EF_A, EF_B) = max(5,3) = 5; FF(B) = 5-3 = 2; B's total and free float are equal because B is the only activity before the merge

80 / 150

Question 81 of 150

A PM needs to reduce the project schedule by 8 days. The critical path has 5 activities. After crashing the cheapest critical activity to its maximum (saving 4 days), the PM recalculates and finds two paths are now tied as critical. What must the PM do to save the remaining 4 days?

A The remaining 4 days cannot be recovered B Continue crashing only the original critical path C Switch to fast-tracking for the remaining days D Crash activities on BOTH critical paths simultaneously — since two paths are now tied, reducing only one path will not shorten the project; the PM must find activities to crash on both paths (or shared activities on both paths) to achieve further schedule compression

81 / 150

Question 82 of 150

A PM evaluates crashing options. Activity A: crash cost $500/day, max 3 days, on critical path. Activity B: crash cost $400/day, max 5 days, NOT on critical path (has 2 days float). What should the PM crash?

A Activity B because it is cheaper per day B Both activities equally C Activity A — only critical path activities should be crashed because only critical path compression reduces the project duration; crashing Activity B (non-critical) would waste money since it has float and does not constrain the project end date D Neither activity needs crashing

82 / 150

Question 83 of 150

A PM fast-tracks two critical path activities by overlapping them. The original sequence was: Design (20 days) -> Build (15 days) = 35 days total. After fast-tracking with SS + 10-day lag, what is the new duration and what risk is introduced?

A 25 days with no additional risk B 20 days C 25 days with increased rework risk — Build starts when Design is 10 days in (50% complete); if Design changes after Day 10 affect Build's inputs, significant rework may be needed; the PM saves 10 days but accepts the risk that partially-complete design outputs may change D 35 days (unchanged)

83 / 150

Question 84 of 150

A PM considers both crashing and fast-tracking for the same critical path segment. Crashing would cost $15,000 to save 5 days. Fast-tracking would save the same 5 days at no direct cost but introduces a 30% probability of 10 days of rework. Which option has a lower expected cost?

A Fast-tracking always costs less B Both have identical costs C Crashing at $15,000 D The expected cost of fast-tracking is $0 direct + 30% x (cost of 10 days rework); if 10 days of rework costs more than $50,000 (expected rework cost = 0.30 x $50,000 = $15,000), then crashing is equal or cheaper; the PM must calculate the expected rework cost to compare

84 / 150

Question 85 of 150

A PM has exhausted all crashing options on the critical path (all activities are at their crash duration). The schedule is still 3 days too long. What options remain?

A Add more resources to already-crashed activities B Only fast-tracking remains as an option C Nothing can be done; accept the delay D Remaining options include: fast-tracking (overlapping sequential critical path activities), reducing scope (remove or defer lower-priority deliverables), substituting resources (use more experienced or specialized resources), reducing quality requirements (if acceptable), or negotiating the deadline with the sponsor

85 / 150

Question 86 of 150

A PM fast-tracks the project by starting Phase 2 before Phase 1 is complete. Six weeks later, a Phase 1 deliverable is rejected, requiring Phase 2 work to be partially redone. What type of risk did the PM fail to adequately manage?

A The PM failed to adequately manage the fast-tracking rework risk — fast-tracking creates a dependency on intermediate (incomplete) deliverables; when predecessor outputs change, successor work built on those outputs must be redone, potentially negating the schedule savings and adding cost B This outcome was unavoidable C Schedule risk only D Budget risk only

86 / 150

Question 87 of 150

A PM applies crashing to Activity X, adding 3 extra team members. Activity X's duration decreases from 10 days to 7 days. However, the PM notices that communication overhead has increased. What principle explains why adding resources does not produce proportional time savings?

A Brooks's Law and the law of diminishing returns — adding people to a task increases communication channels (n(n-1)/2), requires ramp-up time, and creates coordination overhead; at some point, additional resources produce diminishing schedule benefit and may even slow the activity B Resources never reduce duration C Crashing always reduces duration proportionally D Communication overhead is only relevant in agile projects

87 / 150

Question 88 of 150

A PM needs to decide between crashing Activity Y at $2,000/day and crashing Activity Z at $3,000/day. Both are on the critical path and can each be crashed by up to 3 days. The PM needs to save 3 days. Which approach minimizes cost?

A Crash Activity Y by 3 days at a total cost of $6,000 — since only 3 days are needed and Y is the cheapest option at $2,000/day, crashing Y fully achieves the target at minimum cost; there is no need to crash Z at all B Crash both by 3 days each for maximum safety C Crash Z by 3 days at $9,000 D Crash Y and Z equally (1.5 days each)

88 / 150

Question 89 of 150

A PM considers fast-tracking by changing a Finish-to-Start relationship to Start-to-Start. The predecessor activity has a high degree of design uncertainty. Why should the PM be cautious about fast-tracking in this situation?

A Uncertainty does not affect fast-tracking decisions B Fast-tracking only works with FS relationships C SS relationships are not allowed in project scheduling D High design uncertainty means the predecessor's outputs are likely to change significantly — if the successor starts in parallel based on early outputs, those outputs may be substantially revised, causing extensive rework that could delay the project more than the time saved by fast-tracking

89 / 150

Question 90 of 150

A PM presents two schedule compression options to the sponsor. Option 1: Crash 5 critical activities (cost: $45,000, saves 12 days, low risk). Option 2: Fast-track 3 activity pairs (cost: $5,000, saves 12 days, medium-high risk with 40% chance of 8 days rework at $4,000/day). Which option should the PM recommend and why?

A Always choose the cheapest option B Option 2 because it saves money C The PM should not present options to the sponsor D The PM should present both options with full analysis: Option 1 costs $45,000 with certainty. Option 2 expected cost = $5,000 + (0.40 x 8 x $4,000) = $5,000 + $12,800 = $17,800 expected, but with a 40% chance of losing 8 days of the 12 saved — the recommendation depends on the organization's risk tolerance and schedule criticality

90 / 150

Question 91 of 150

A PM uses resource leveling and discovers that it extends the critical path from 40 to 48 days. The sponsor refuses to accept the 8-day extension. What technique can the PM use to compress the resource-leveled schedule without adding cost?

A Resource leveling cannot be reversed B Remove resource constraints entirely C Fast-track the resource-leveled schedule D Resource smoothing — instead of resource leveling (which resolves ALL overallocations even if it extends the schedule), resource smoothing adjusts resource assignments only within existing float, keeping the project end date fixed while reducing resource peaks where possible

91 / 150

Question 92 of 150

A PM identifies that crashing Activity M saves 2 days at $3,000/day. However, crashing M causes a previously non-critical path to become critical. To maintain the 2-day savings, the PM must also crash Activity N on the new critical path at $2,500/day for 2 days. What is the true total cost of saving 2 days?

A $3,000 total B $5,000 (only Activity N) C $11,000 — crashing M costs $6,000 (2 x $3,000) and crashing N costs $5,000 (2 x $2,500); both crashes are necessary to achieve the 2-day reduction because the critical path shifted; the effective cost is $5,500 per day saved, not the original $3,000 per day D $6,000 (only Activity M)

92 / 150

Question 93 of 150

A PM applies fast-tracking and crashing simultaneously to different portions of the critical path. Fast-tracking saves 6 days on one segment while crashing saves 4 days on another. Can the PM claim a total schedule reduction of 10 days?

A The savings would be 24 days (6 x 4) B Not necessarily — the PM must verify by recalculating the entire network; fast-tracking and crashing on different segments may create interactions (new critical paths, changed float values) that prevent the full 10-day savings from materializing; the actual reduction could be less C Yes, all schedule compression is additive D No, you can only use one compression technique at a time

93 / 150

Question 94 of 150

A PM fast-tracks by converting mandatory FS dependencies to SS. A quality auditor flags this as a violation. Why is the auditor concerned?

A SS dependencies are prohibited by quality standards B Quality auditors cannot review schedule dependencies C All dependencies can be fast-tracked regardless of type D Mandatory (hard) dependencies represent physical or contractual constraints that CANNOT be safely overlapped — converting mandatory FS to SS violates the inherent nature of the work and may result in physically impossible or unsafe work sequences; only discretionary dependencies should be candidates for fast-tracking

94 / 150

Question 95 of 150

A PM uses schedule compression to meet a deadline. After crashing and fast-tracking, the project schedule meets the target but with 15% less total float than the original baseline. What should the PM communicate to stakeholders?

A The schedule meets the deadline; no further communication needed B The PM should add buffer activities to restore float C Float reduction is irrelevant if the deadline is met D The compressed schedule meets the deadline but has significantly reduced float, meaning the project has less ability to absorb delays and risks — stakeholders should understand that the schedule is 'tighter' with less margin for error, and risk monitoring must be more vigilant

95 / 150

Question 96 of 150

A construction PM uses a technique called 'schedule compression by substitution.' Instead of crashing or fast-tracking, the PM replaces a 15-day concrete curing process with a rapid-cure concrete that takes 5 days. What type of compression is this?

A Fast-tracking B Crashing C This is a form of schedule compression through technology or method substitution — replacing a slower approach with a faster one that achieves the same result; it differs from crashing (same method, more resources) and fast-tracking (overlapping activities) by changing the approach itself D This is not a valid compression technique

96 / 150

Question 97 of 150

A PM has compressed the schedule as much as possible but the critical path is still 5 days too long. All crashing options are exhausted, fast-tracking is too risky, and scope cannot be reduced. What negotiation strategy should the PM use with the sponsor?

A Tell the sponsor the schedule is achievable and hope for the best B Resign from the project C Present the full analysis to the sponsor: the constraints attempted, costs incurred, and remaining 5-day gap; propose alternatives such as extending the deadline by 5 days, accepting increased risk through aggressive fast-tracking, phased delivery (deliver core scope on time and remaining scope 5 days later), or increased budget for premium solutions D Accept the delay without informing the sponsor

97 / 150

Question 98 of 150

A PM is evaluating whether to fast-track 'System Integration Testing' by starting it before 'Unit Testing' is complete. 80% of modules have passed unit testing but 20% are still being tested. What factor is MOST critical in this fast-tracking decision?

A Whether the 80% of modules that passed unit testing are sufficiently independent to be meaningfully integration-tested without the remaining 20% — if the untested modules are critical integration points, starting integration testing early may produce misleading results or require complete retesting B Whether the PM has approval from the change control board C The number of integration testers available D The cost of the integration testing resources

98 / 150

Question 99 of 150

A PM applies schedule compression iteratively. In round 1, crashing saves 3 days at $2,000/day. In round 2, crashing saves 2 more days but at $4,500/day (because cheaper options were exhausted and a new critical path emerged). What trend does this illustrate?

A The second round should be reversed since it is too expensive B Schedule compression exhibits increasing marginal cost — each additional day saved costs progressively more because the cheapest options are used first, critical paths multiply, and diminishing returns set in; the PM should present a cost curve showing cumulative cost per day to help the sponsor decide when to stop compressing C Crashing costs decrease with each round D All crashing rounds cost the same

99 / 150

Question 100 of 150

A PM is asked to create a 'time-cost trade-off curve' for the project. What does this curve show and how is it used?

A A curve showing schedule vs scope trade-offs B The time-cost trade-off curve plots project duration on the x-axis and total project cost on the y-axis, showing how cost increases as duration decreases through crashing — the curve helps identify the optimal project duration where total cost (direct + indirect) is minimized C A curve showing resource utilization over time D A curve showing cost vs quality trade-offs

100 / 150

Question 101 of 150

What is velocity in agile project management and how is it measured?

A The ratio of planned to actual cost per sprint B Velocity is the amount of work (measured in story points, ideal days, or other units) a team completes in a single sprint — it is calculated by summing the estimates of all fully completed (meeting the DoD) user stories at the end of each sprint C The speed at which individual team members complete tasks D The number of hours worked per sprint

101 / 150

Question 102 of 150

A team completes the following story points over 5 sprints: 28, 32, 25, 35, 30. What is the team's average velocity and how should the PM use this for planning?

A Average velocity = (28+32+25+35+30)/5 = 30 story points per sprint — the PM should use this average (or a range based on min/max) to forecast how many sprints remain to complete the remaining backlog and when the release can be delivered B 150 total points, use 150 for the next sprint C Velocity cannot be averaged D The highest velocity (35) should be used for future planning

102 / 150

Question 103 of 150

A newly formed team has no historical velocity data. They are about to start their first sprint with a 2-week timebox. How should the PM estimate the first sprint's capacity?

A Use techniques such as: team estimation based on available hours and estimated throughput, comparison with similar teams if available, starting with a conservative commitment and adjusting after Sprint 1, or running a calibration sprint — velocity should stabilize after 3-5 sprints B Use industry-standard velocity of 40 points per sprint C Assign each team member 20 story points per sprint D Skip sprint planning until velocity is established

103 / 150

Question 104 of 150

A team's velocity over 8 sprints is: 20, 22, 24, 26, 28, 30, 32, 34. The PM notices a consistent upward trend. What does this pattern indicate and how should it affect planning?

A Story point inflation (stories are being pointed lower) B The team is sandbagging early sprints C The team is working overtime D The upward velocity trend likely reflects the team maturing — they are becoming more efficient at estimation, collaboration, and delivery; the PM should use recent velocity (last 3-4 sprints) rather than the full 8-sprint average for forecasting, as it better reflects current capability

104 / 150

Question 105 of 150

A Scrum team has a velocity of 25 story points per sprint. During sprint planning, the product owner wants the team to commit to 35 points because there is a critical release deadline. What should the team do?

A The team should commit to what they can realistically deliver based on their velocity — committing to 35 points when historical velocity is 25 sets up the sprint for failure; instead, the team should commit to approximately 25 points of the highest-priority work and communicate the capacity gap to the product owner B Extend the sprint timebox to accommodate 35 points C Split the difference and commit to 30 points D Commit to 35 points to meet the deadline

105 / 150

Question 106 of 150

A team's velocity drops from 30 to 18 over two sprints. What should the Scrum Master investigate?

A Add more team members to increase velocity B Demand the team return to 30 points immediately C Investigate root causes such as: team member departures or absences, increased technical debt making work slower, unclear or changing requirements causing rework, sprint scope changes after commitment, external dependencies or blockers, team morale issues, or the team is properly sizing stories for the first time (previous velocity was inflated) D Velocity drops are normal and require no action

106 / 150

Question 107 of 150

Management wants to compare velocity between Team A (velocity 40) and Team B (velocity 25) to determine which team is more productive. Why is this comparison invalid?

A Velocity comparisons are valid if both teams use the same framework B Velocity is a team-specific metric that cannot be compared across teams — each team has its own estimation calibration (one team's 5-point story might be another team's 8-point story), and velocity reflects the team's unique context including composition, domain complexity, and technical environment C The comparison is valid; Team A is clearly more productive D Only teams of equal size can be compared

107 / 150

Question 108 of 150

What is a sprint burndown chart and what does it show?

A A chart showing team member utilization B A chart showing total project cost over time C A sprint burndown chart plots the remaining work (in story points or tasks) on the y-axis against time (sprint days) on the x-axis — the ideal trend line decreases linearly from total committed points to zero, and the actual line shows real progress, revealing whether the team is on track to complete the sprint commitment D A chart showing cumulative completed features

108 / 150

Question 109 of 150

A sprint burndown chart shows the actual line flat for the first 5 days, then dropping sharply on days 6-10. What pattern does this indicate?

A The team is ahead of schedule B The team may be working in a 'big batch' pattern — stories are large and not broken down enough, so nothing is 'done' until late in the sprint; alternatively, the team may be working on all stories in parallel rather than completing them sequentially; this pattern increases the risk of unfinished work at sprint end C The burndown chart is malfunctioning D Excellent team performance in the second half

109 / 150

Question 110 of 150

What is the difference between a sprint burndown chart and a release burnup chart?

A A sprint burndown shows remaining work within a single sprint (zoomed in, tactical), while a release burnup shows cumulative completed work across multiple sprints against total scope (zoomed out, strategic) — the burnup also makes scope changes visible as changes in the total scope line B Burnup charts cannot show scope changes C They show the same information in different formats D Burndown charts are for agile and burnup charts are for waterfall

110 / 150

Question 111 of 150

A team has a velocity of 20 points per sprint. The release backlog has 100 story points. Using velocity-based forecasting, when will the release be ready?

A Cannot be determined from velocity alone B 5 sprints — Release sprints = Total remaining story points / Average velocity = 100 / 20 = 5 sprints; if each sprint is 2 weeks, the release is approximately 10 weeks away; the PM should also provide a range using optimistic and pessimistic velocity estimates C 1 sprint (100/100) D 20 sprints

111 / 150

Question 112 of 150

A team uses sprint mapping to plan a 6-sprint release. They allocate Sprint 1-2 for architecture and infrastructure stories, Sprint 3-5 for feature stories, and Sprint 6 for hardening and bug fixes. What concern should the Scrum Master raise about this plan?

A The plan is well-structured with no concerns B Six sprints is too many for a single release C Sprint 6 should be first, not last D This plan resembles a mini-waterfall (architecture -> features -> testing) rather than truly iterative delivery — each sprint should produce a potentially shippable increment; mixing architecture, features, and hardening across sprints enables continuous validation and reduces integration risk

112 / 150

Question 113 of 150

A team's velocity for the last 6 sprints is: 22, 28, 18, 30, 24, 26. The PM calculates an average of 24.7. A team member says the average is misleading because of the high variance. What additional metric should the PM provide?

A The PM should also report the velocity range (18-30), standard deviation (approximately 4.3 points), and possibly a confidence interval — this communicates the uncertainty in forecasts; a team with average 25 and range 18-30 has different predictability than a team with average 25 and range 23-27 B Only the median matters C Variance in velocity is irrelevant for planning D The PM should only report the most recent sprint's velocity

113 / 150

Question 114 of 150

A Scrum team uses 'yesterday's weather' to plan sprint capacity. What does this mean?

A 'Yesterday's weather' means using the previous sprint's velocity as the best predictor of the next sprint's capacity — the team commits to approximately the same amount of work they completed last sprint, based on the empirical assumption that recent performance best predicts near-term performance B The team reviews yesterday's standup notes before planning C Historical project data from other teams is used D The team adjusts the sprint schedule based on weather conditions

114 / 150

Question 115 of 150

A team finishes a sprint with 5 of 7 committed stories done (velocity = 24 points out of 35 committed). Two stories (11 points) are 80% complete. Should the PM count partial credit toward velocity?

A Count them as done if the product owner approves B Estimate the remaining 20% and add it to the next sprint C No — velocity only counts fully completed stories that meet the Definition of Done; the 2 incomplete stories (11 points) return to the backlog and are counted in a future sprint when they are fully done; counting partial credit undermines the transparency and reliability of velocity as a planning metric D Yes, count 80% of the incomplete stories (8.8 points)

115 / 150

Question 116 of 150

A PM asks the team to increase velocity by 20% for the next quarter. How should the Scrum Master respond to this request?

A Velocity is an OUTPUT of the team's process, not an INPUT to be mandated — artificially increasing velocity leads to gaming (inflating estimates, cutting quality); the Scrum Master should instead focus on removing impediments, improving practices, and reducing waste, which may naturally increase velocity B Velocity cannot be improved under any circumstances C Direct the team to work faster and take on more points D Add more team members to increase velocity

116 / 150

Question 117 of 150

What is a sprint goal and how does it relate to sprint planning and velocity?

A Sprint goals are optional in Scrum B The sprint goal is the total number of story points committed C The sprint goal is a concise statement of the business objective the sprint aims to achieve — it provides focus and flexibility; the team selects stories from the backlog that support the sprint goal, guided by velocity for capacity, and can negotiate scope within the goal if stories prove larger than expected D The sprint goal is set by the project sponsor

117 / 150

Question 118 of 150

A team uses Kanban instead of Scrum. They do not have fixed sprints. How do they measure and forecast delivery without velocity?

A Kanban teams use throughput (number of items completed per time period) and cycle time (time from start to completion of an item) for forecasting — they can use Monte Carlo simulation with historical throughput data to predict when a set of items will be completed with various confidence levels B Kanban teams use velocity the same way Scrum teams do C Kanban teams cannot forecast delivery D Kanban teams must adopt sprints to forecast

118 / 150

Question 119 of 150

A team has a velocity of 30 points per 2-week sprint. Management asks the PM to convert this to a traditional schedule (weeks). How should the PM translate agile velocity into a timeline for a 180-point release?

A 180 points / 30 points = 6 days B Velocity cannot be converted to calendar time C 180 points / 30 points per sprint = 6 sprints x 2 weeks per sprint = 12 weeks — the PM should add buffer for sprint ceremonies, unforeseen impediments, and any hardening or release preparation work; presenting a range (11-14 weeks) is more realistic than a single date D 180 points is 6 weeks of work

119 / 150

Question 120 of 150

A team tracks both velocity (story points completed) and throughput (stories completed). Velocity is stable at 30 points/sprint but throughput dropped from 8 stories to 4 stories per sprint. What does this discrepancy indicate?

A Story point estimates are inflated B The team is becoming less productive C The metrics contradict each other; one must be wrong D The team is completing fewer but LARGER stories — the same total points spread across half as many stories means average story size increased from 3.75 to 7.5 points; this may indicate the team is not breaking stories down enough, or they are tackling more complex work

120 / 150

Question 121 of 150

A PM creates a 'sprint mapping' view that shows which features will be delivered in which sprints over the next 4 sprints. A stakeholder treats this as a commitment. What should the PM clarify?

A Sprint mapping guarantees exact feature delivery dates B Sprint mapping IS a commitment C The PM should not share sprint mapping with stakeholders D Sprint mapping is a FORECAST based on current velocity, priorities, and known scope — it will change as the team learns more, priorities shift, and requirements evolve; only the current sprint's commitment is a firm plan; future sprints are increasingly uncertain and should be treated as projections

121 / 150

Question 122 of 150

A team uses 'capacity-based sprint planning' instead of velocity-based planning. How does capacity-based planning work?

A It uses the same approach as velocity-based planning B Only the Scrum Master uses capacity-based planning C Capacity planning ignores individual availability D Capacity-based planning calculates available team hours for the sprint (accounting for vacations, meetings, and overhead), then selects stories whose estimated effort fits within that capacity — it is useful for new teams without velocity history or teams with highly variable availability

122 / 150

Question 123 of 150

A Scrum team has a WIP (Work In Progress) limit of 3 for the 'In Development' column on their board. Currently, 3 stories are in development and a developer finishes one. Instead of pulling a new story, they help another developer with a struggling story. Why is this behavior encouraged?

A Focusing on finishing existing work rather than starting new work reduces cycle time and increases throughput — helping a struggling story get to done faster is more valuable than starting a new story; this 'stop starting, start finishing' principle optimizes flow and reduces context switching B WIP limits prevent developers from starting new work C Developers must always help each other before starting new work D WIP limits are only suggestions, not rules

123 / 150

Question 124 of 150

A team uses story points but a new developer says they are 'just guessing.' How should the Scrum Master explain the purpose and method of story point estimation?

A Story points are RELATIVE estimates that compare the size of stories to a reference story — the team uses techniques like Planning Poker to build consensus; they are intentionally imprecise because precise estimation of knowledge work is unreliable, and relative comparison is faster and more consistent than absolute estimation B Story points must equal the number of hours a story takes C Story points are exact measurements of effort D Story points should be estimated by the project manager

124 / 150

Question 125 of 150

A PM tracks the team's velocity trend and notices it has stabilized around 25 points per sprint for the last 8 sprints. The team suggests they should stop tracking velocity since it does not change. What is the PM's best response?

A Increase the sprint length to change velocity B Stable velocity is valuable — it enables highly reliable forecasting; the team should continue tracking to detect future changes (team member departure, technical debt accumulation, scope complexity increase) that would alter capacity; velocity is both a planning tool and an early warning system C Agree and stop tracking velocity D Repoint all stories to create velocity variation

125 / 150

Question 126 of 150

What is release planning in agile and how does it differ from sprint planning?

A Release planning is only done in waterfall projects B Sprint planning replaces the need for release planning C Release planning and sprint planning are the same activity D Release planning determines WHICH features will be included in a release and approximately WHEN the release will occur (multi-sprint horizon), while sprint planning determines which specific stories the team will complete in the next sprint (single-sprint horizon) — release planning is strategic, sprint planning is tactical

126 / 150

Question 127 of 150

A PM uses two approaches to release planning: date-driven and feature-driven. What is the difference?

A There is no difference between the two approaches B Date-driven plans have no scope and feature-driven plans have no date C Date-driven release planning fixes the date and varies scope (determine how many features velocity allows by the fixed date), while feature-driven release planning fixes the scope and varies the date (determine when velocity will deliver all required features) — the constraint determines the approach D Date-driven is for waterfall and feature-driven is for agile

127 / 150

Question 128 of 150

A PM creates a release plan showing 8 sprints to complete 200 story points (velocity = 25/sprint). After Sprint 3, velocity is averaging 22 and the backlog has grown to 220 points (20 points added). What is the revised release forecast?

A Cannot be recalculated until the release is complete B 7 sprints C Still 8 sprints D 10 sprints — remaining work = 220 - (3 x 22) = 220 - 66 = 154 points; at velocity 22, remaining sprints = 154 / 22 = 7 sprints; total = 3 completed + 7 remaining = 10 sprints; the release is now 2 sprints (4 weeks) later than originally planned due to lower velocity AND increased scope

128 / 150

Question 129 of 150

A PM is managing a hybrid project where the backend (predictive) uses a CPM schedule and the frontend (agile) uses sprints and velocity. A backend activity on the critical path is a predecessor to frontend Sprint 4 work. How should the PM manage this cross-methodology dependency?

A Manage each methodology independently B Convert the entire project to either CPM or agile C Create an integrated schedule that maps the backend CPM milestone to the frontend sprint timeline — the PM should ensure the backend activity finishes before Sprint 4 begins, build buffer for the dependency, and monitor both the CPM float on the backend activity and the frontend team's sprint plan for Sprint 4 D Dependencies between methodologies are not possible

129 / 150

Question 130 of 150

A PM uses Monte Carlo simulation for release forecasting. After 10,000 simulations using historical velocity data, the results show: 50th percentile = Sprint 8, 85th percentile = Sprint 10, 95th percentile = Sprint 12. What should the PM communicate to stakeholders?

A Monte Carlo results are unreliable and should not be shared B The release will be in Sprint 12 (worst case) C Present the probabilistic forecast: 'There is a 50% chance we will finish by Sprint 8, an 85% chance by Sprint 10, and a 95% chance by Sprint 12' — recommend committing to the 85th percentile (Sprint 10) for external commitments, as it provides reasonable confidence without being overly conservative D The release will be in Sprint 8

130 / 150

Question 131 of 150

A team uses the 'Program Increment (PI) Planning' ceremony from SAFe. How does PI Planning relate to traditional release planning and sprint mapping?

A PI Planning is identical to sprint planning B PI Planning is a large-scale, face-to-face planning event where multiple agile teams collaborate to plan the next 8-12 weeks (typically 5 sprints) — it combines elements of release planning (scope and timeline across sprints), sprint mapping (which features in which iterations), and dependency management across teams C PI Planning replaces all other planning activities D PI Planning is only used for hardware projects

131 / 150

Question 132 of 150

A PM manages a project with a fixed delivery date (immovable external deadline) and a prioritized backlog of 150 story points. The team's velocity is 25 points/sprint with 2-week sprints. There are 5 sprints until the deadline. What should the PM communicate to the product owner?

A The deadline should be extended B The team can deliver approximately 125 story points (5 sprints x 25 velocity) by the deadline — the product owner should identify which 125 points represent the highest-priority scope; the remaining 25 points must be deferred to a post-deadline release or descoped entirely C The team should increase velocity to 30 points per sprint D All 150 points will be delivered

132 / 150

Question 133 of 150

A PM uses a 'cumulative flow diagram' (CFD) to monitor schedule health in a Kanban/agile context. What does the CFD show and what patterns indicate schedule risk?

A CFD shows velocity over time B CFD shows resource allocation over time C CFD is only used in waterfall projects D A CFD shows the count of work items in each workflow state (to do, in progress, testing, done) over time as stacked area bands — widening bands indicate growing WIP and longer cycle times (schedule risk), while consistent band widths indicate stable flow and predictable delivery

133 / 150

Question 134 of 150

A PM is asked to create a 'schedule baseline' for a project that uses both CPM (for infrastructure) and agile sprints (for software). What should this hybrid schedule baseline include?

A Agile projects cannot have schedule baselines B The hybrid baseline should include: the CPM network schedule with critical path for predictive components, the release plan with velocity-based sprint mapping for agile components, cross-methodology dependencies and integration milestones, and agreed-upon measurement criteria for tracking progress against both approaches C Two completely separate baselines with no integration D Only the CPM schedule counts as a baseline

134 / 150

Question 135 of 150

A PM notices that the project's SPI (Schedule Performance Index) is 0.9 and the agile team's velocity trend is declining. Both metrics suggest the project is falling behind. The PM decides to fast-track the CPM portion and add capacity to the agile team. What should the PM verify FIRST?

A Whether the budget supports both interventions B Whether the CPM delay and the agile velocity decline share a common root cause — if both are caused by the same issue (e.g., a shared dependency, resource constraint, or requirement churn), addressing the root cause may fix both problems more effectively than treating symptoms separately C Whether the quality plan needs to be updated D Whether the sponsor approves the interventions

135 / 150

Question 136 of 150

A PM builds a project schedule and identifies 4 paths with durations of 45, 42, 44, and 38 days. The project deadline is 46 days. What is the project float and which paths require monitoring?

A Project float is 1 day (46 - 45 = 1); ALL paths with less than 5 days of float should be monitored — Path 1 (TF=1), Path 2 (TF=4), and Path 3 (TF=2) are all near-critical and pose schedule risk; only Path 4 (TF=8) has comfortable float B Project float is 8 days; only the critical path needs monitoring C Project float is 46 days D All paths have the same float

136 / 150

Question 137 of 150

A PM schedules a project using CPM and establishes the baseline. During execution, a stakeholder asks: 'What is the difference between the schedule baseline, the schedule model, and the project schedule?' How should the PM explain?

A The schedule model is the computational framework (network logic, durations, constraints, calendars); the project schedule is the output of the model (dates, Gantt charts, milestones); the schedule baseline is the approved version of the project schedule that serves as the reference point for measuring performance — the model produces the schedule, and the baseline freezes a version of it B They are three names for the same thing C The baseline is always updated while the model is fixed D Only the schedule baseline is used during execution

137 / 150

Question 138 of 150

A team is transitioning from waterfall to agile. They previously used detailed Gantt charts with 500 tasks. Management still wants to see Gantt-style reporting. How can the PM bridge both worlds?

A Gantt charts are incompatible with agile B Create a high-level milestone Gantt chart that maps sprint boundaries and release milestones to a timeline view — this gives management the timeline-based visualization they expect while the team works internally with backlogs, sprint boards, and velocity charts; the Gantt shows WHAT and WHEN, the agile tools show HOW C Abandon Gantt charts entirely D Force the team to maintain both a 500-task Gantt and a backlog

138 / 150

Question 139 of 150

A project has a critical path of A(5)->B(8)->C(6)->D(4) = 23 days. The PM identifies a risk that Activity B may take 12 days instead of 8 (50% probability). Using expected value analysis, what is the expected project duration?

A 25 days — Expected duration of B = (0.50 x 8) + (0.50 x 12) = 4 + 6 = 10 days; expected critical path = 5 + 10 + 6 + 4 = 25 days; the risk-adjusted schedule is 2 days longer than the deterministic schedule B 12 days C 27 days D 23 days

139 / 150

Question 140 of 150

A PM needs to report schedule status to different audiences: the team, the sponsor, and the steering committee. What schedule visualization should each audience receive?

A Use the network diagram for all audiences B All audiences should see the same detailed Gantt chart C Team: sprint board and burndown chart (daily tactical view); Sponsor: milestone chart and release burnup (strategic progress view); Steering committee: RAG status dashboard with key milestones and SPI trend (executive summary view) — each audience needs a different level of detail matched to their decision-making needs D Only the sponsor needs schedule reports

140 / 150

Question 141 of 150

A PM identifies that 3 activities on the critical path can each be performed by one of two resources: a senior (costs $200/hr, works 50% faster) or a junior ($100/hr, normal speed). The critical path is 30 days. Using the senior resource for all 3 activities would reduce the critical path to 25 days. What analysis should the PM perform?

A Always use the senior resource since the critical path determines the project end date B Compare the cost of using the senior resource (additional cost for faster completion) against the value of finishing 5 days earlier (reduced indirect costs, earlier revenue, opportunity cost) — the decision should be based on whether the schedule benefit justifies the cost premium C Resource selection does not affect the critical path D Always use the junior resource to minimize cost

141 / 150

Question 142 of 150

A PM uses the 'Schedule Risk Assessment' technique and identifies that Activity E (critical path, 15-day duration) has no float, high complexity, a single-point-of-failure resource, and an external dependency. What risk response should the PM implement?

A Reduce Activity E's duration estimate B Implement multiple risk responses: cross-train a backup resource (mitigate single-point-of-failure), build a schedule buffer after Activity E (contingency reserve), monitor the external dependency proactively with early warning triggers, and consider splitting Activity E into smaller deliverables to reduce the impact of disruption C Remove Activity E from the critical path D Accept the risk since the activity is already on the critical path

142 / 150

Question 143 of 150

A project schedule shows 150 activities. The PM runs a schedule quality check and finds: 12 activities have no predecessors (excluding the start milestone), 8 activities have no successors (excluding the finish milestone), and 20 activities have only FS+0 relationships with over 30 days duration. What schedule quality issues exist?

A The schedule passes all quality checks B Three quality issues: (1) Open-ended predecessors (12 danglers) mean logic gaps. (2) Open-ended successors (8 danglers) mean the finish milestone may not capture all work. (3) Long activities (30+ days) should be decomposed further for better progress tracking and more accurate CPM calculations — all three issues reduce schedule reliability C Long activities are acceptable in all cases D Only the danglers are problems

143 / 150

Question 144 of 150

A PM uses 'schedule reserves' in the project schedule. What are the two types of schedule reserves and who controls each?

A Only one type of schedule reserve exists B Schedule reserves are not allowed in project scheduling C Contingency reserve (owned by the PM) covers identified risks with estimated time impacts; management reserve (owned by the sponsor/management) covers unknown-unknowns and scope changes; the PM can use contingency reserve independently but must request authorization for management reserve D Both reserves are controlled by the PM

144 / 150

Question 145 of 150

A team completes Sprint 5 and the release burnup chart shows 120 points completed with 80 points remaining. Average velocity is 24 points/sprint. But the product owner just added 20 new points to the backlog. What does the updated release forecast show?

A 80/24 = 3.3 more sprints (ignore new scope) B The release cannot be recalculated C 100/24 = 4.2 more sprints D The remaining work is now 100 points (80 remaining + 20 added); at velocity 24, the team needs approximately 4.2 more sprints (100/24); total release = Sprint 5 + 4.2 = approximately Sprint 9-10; the burnup chart visually shows the scope line jumping, making the scope change impact immediately visible to stakeholders

145 / 150

Question 146 of 150

A PM uses lead time and cycle time metrics from Kanban to forecast delivery. The team's average cycle time is 4 days per story with a standard deviation of 2 days. A stakeholder needs 10 stories completed. What is a reasonable forecast?

A If the team works on stories in parallel (e.g., WIP limit of 3), throughput is approximately 3 stories per 4 days; 10 stories would take roughly 14-16 days; the PM should use throughput-based forecasting rather than multiplying cycle time by count, and include a range based on cycle time variability B 40 days (10 x 4 days) C 10 days (one story per day) D Cycle time cannot be used for forecasting

146 / 150

Question 147 of 150

A PM manages a project with 3 phases. Phase 1 uses agile (8 sprints), Phase 2 uses predictive CPM (45 days), and Phase 3 uses agile (4 sprints). Sprints are 2 weeks. What is the estimated project timeline?

A 45 days total (only the CPM phase matters) B 8 + 45 + 4 = 57 days C Phase 1 = 8 sprints x 2 weeks = 16 weeks (80 working days); Phase 2 = 45 working days (9 weeks); Phase 3 = 4 sprints x 2 weeks = 8 weeks (40 working days); Total = approximately 33 weeks (165 working days), assuming sequential phases with no overlap — the PM should look for overlap opportunities between phases to compress the timeline D 12 sprints = 24 weeks total

147 / 150

Question 148 of 150

A PM presents a schedule to the sponsor that shows the project finishing 2 weeks early. The sponsor asks the PM to add those 2 weeks as buffer. Where should this buffer be placed in the schedule?

A Buffer cannot be added to a schedule B Distribute the 2 weeks equally across all activities C Place the 2-week buffer at the end of the critical path (or as a project buffer in Critical Chain terminology) — this centralizes the protection where it matters most; distributing buffer across activities encourages Parkinson's Law (work expanding to fill available time) and Student Syndrome (procrastination) D Add the buffer to the first activity

148 / 150

Question 149 of 150

A PM is asked: 'Which is better for schedule management — CPM or agile sprints?' What is the most accurate answer from a PMBOK 7 perspective?

A CPM is always better because it is more structured B Neither is universally better — the choice depends on the project's characteristics; CPM is better for well-defined scope with predictable durations, while agile sprints are better for evolving requirements with uncertain scope; PMBOK 7 emphasizes tailoring the approach to the project context rather than prescribing a single method C Agile sprints are always better because they are more flexible D Both approaches produce identical results

149 / 150

Question 150 of 150

A PM reviews the complete schedule management approach for a large hybrid project. The approach includes: PDM network for infrastructure, CPM for critical path analysis, crashing/fast-tracking for compression, velocity-based sprint planning for software, release burnup for forecasting, and integrated milestone reporting. A senior stakeholder says this is too complex. How should the PM respond?

A Simplify to only use a Gantt chart B Remove the agile components to simplify C Each technique serves a specific purpose: PDM provides dependency logic, CPM identifies the critical constraint, compression techniques address schedule gaps, velocity enables empirical agile planning, burnup provides visual forecasting, and milestones integrate the whole picture — the PM should demonstrate how each element contributes to schedule confidence and offer to simplify reporting while maintaining analytical rigor behind the scenes D The stakeholder is right; only one technique is needed

150 / 150

PMBOK 7 - Schedule Management