A business analyst wants a new reporting field added to a project that is already in the execution phase and asks a developer directly, without looping in the project manager. What should the analyst have done instead?
- A. Submit a formal change request describing the desired addition so it can be evaluated Correct
- B. Ask the developer to complete the work quietly since it is a minor addition
- C. Wait until the project closes before mentioning the idea to anyone
- D. Edit the project scope statement directly without any review
Why A is correct
Submitting a formal change request is the entry point of the change control process: the request gets logged, assessed for impact on schedule, cost, and risk, and reviewed by the appropriate authority before any work begins. That protects the approved baseline and gives the project manager visibility into every proposed addition.
Why the others are incorrect
Asking a developer to quietly complete the work sidesteps governance entirely — it's a textbook way scope creep takes hold. Waiting until closeout just delays a conversation that should happen now. And editing the scope statement directly usurps the authority of whoever approves baseline changes, typically the Change Control Board.