Following Planned Strategies and Frameworks

Once a plan or framework exists — a communication plan, a risk response plan, any named strategy a project has already agreed to — the expectation is that the team actually follows it, and that deviations are deliberate, documented choices rather than accidents. A communication plan that says "sponsor gets a weekly written status" isn't a suggestion; a PM who instead gives the sponsor a surprise verbal update once a month, with no record, is failing to execute the planned strategy, regardless of how good the update itself is.

Project initiation is the point where a project is formally authorized to begin — typically marked by a project charter — and it's paired here with benefit planning: being explicit, from day one, about what business value the project is meant to deliver and how that value will actually be measured once the project is over. A project can finish on time and on budget and still be judged a failure if nobody defined what benefit it was supposed to produce in the first place.

Study focus: this task is really about consistency between what was planned and what gets executed. Exam scenarios tend to describe a plan or framework already in place, then ask whether a described action is following it, deviating from it without documentation, or correctly adapting it through a proper change process.