Free CAPM flashcards

What development approach suits a project with stable, well-understood requirements and a fixed deadline?

A predictive approach front-loads detailed planning of scope, schedule, and cost because requirements are known and stable, letting the team commit to a plan and a fixed deadline with confidence.

Repeatedly refining one whole product across cycles is the same thing as incremental delivery.

Incremental delivery adds new completed pieces each cycle, but repeatedly refining one whole product rather than shipping separate finished slices is iterative, not incremental.

What must a needs assessment establish before any solution is chosen?

The needs assessment exists to establish why change is warranted. Defining the business problem or opportunity first ensures every later decision, including whether a solution is even the right one, traces back to a real organisational gap rather than an assumption.

Drafting the mobile app's solution requirements is a good way to start a needs assessment.

Writing solution requirements assumes the mobile app is the right answer, which skips the needs assessment and commits to a solution not yet justified by a defined business need.

Why does the Agile Manifesto favour welcoming a client's requested change during an iteration over holding to the signed requirements document?

The Manifesto ranks responding to change above following a fixed plan. Feedback from a working increment is a signal to adapt, so treating the document as fixed authority inverts the value the Manifesto asks teams to hold.

A signed requirements document is the team's contract, so it should govern the current iteration and later changes should wait.

This treats comprehensive documentation and the original plan as fixed authority, which inverts the Manifesto value that prioritises responding to change over following a plan.

What determines the earliest possible finish date in a project schedule network?

The critical path, the longest continuous chain of dependent activities from start to finish, sets the earliest finish because any delay to an activity on it delays the whole project. In a network where one path totals 16 days and the alternative totals 15 days, the 16-day path is critical.

A path is the critical path because it starts with the single longest activity in the network.

Starting with the longest single activity does not make a path critical; the sum of the whole path does. A path that starts with a 6-day activity but totals 15 days is only near-critical, carrying 1 day of float, while a longer path elsewhere at 16 days is the true critical path.