What document is essential for establishing configuration baselines?

The configuration management (CM) strategy is essential for establishing configuration baselines because it defines how configurations will be managed throughout the lifecycle of a system or project. The CM strategy outlines the processes, rules, and tools that are necessary to maintain the integrity of a system's configuration. This includes procedures for creating and maintaining baselines, which are a reference point for further development and change management.

In establishing configuration baselines, the CM strategy details what constitutes a baseline at various stages of the project, ensuring that all stakeholders have a common understanding of the system’s requirements and the configurations that are considered acceptable at that point in time. Achieving a well-defined baseline is critical for effective change control, product verification, and traceability throughout the project lifecycle.

The other options, while important in their respective contexts, do not specifically address the establishment of configuration baselines. The project charter is focused on high-level project goals and stakeholder expectations, the feasibility study assesses the viability of the project, and the risk management plan deals with identifying and mitigating potential risks. None of these directly pertain to the principles and practices of configuration management.