CAPM Practice: Validate requirements through product delivery

Solution recommendations appear at pre-delivery (which option to pursue) and post-delivery (did the chosen solution work as intended?). Post-delivery, BAs revisit their recommendations: was the analysis correct? Did the solution achieve the predicted benefits? This closes the validation loop.

**Why not B:** A solution recommendation is not the same as a final requirements document produced at project close. The solution recommendation is a deliverable that evaluates options and proposes a preferred solution to meet identified needs. It is produced during analysis and is distinct from the final requirements package.

**Why not C:** A solution recommendation from a BA perspective is broader than simply recommending a specific vendor's technology. The BA evaluates potential solutions against business requirements, feasibility, and organizational constraints. It is a business-driven recommendation, not a narrow technology procurement decision.

**Why not D:** The BA's role is to recommend solutions to business problems, not to recommend a project manager. Recommending personnel assignments falls outside the scope of a solution recommendation deliverable. The BA focuses on analyzing needs and proposing solutions that address those needs.