A project manager is moving from a predictive life cycle project to a new agile project. How should the project manager manage and control scope for the new project?

In an agile project, scope is managed through continuous prioritization and adaptation, rather than a fixed baseline. Estimating the team's delivery capacity and defining story sizes (e.g., using story points) allows the team to understand how much work they can realistically complete in an iteration and helps control the flow of work. This approach aligns with agile principles of iterative development and responding to change. Spending a short time defining scope and building prototypes is part of agile, but it's more about refining requirements than the primary mechanism for controlling scope throughout the project. Developing a plan to complete more work in less time is a general efficiency goal, not a specific agile scope control mechanism. Creating a scope baseline and placing remaining work in the backlog is a hybrid approach; agile primarily uses the backlog as the evolving scope, not a fixed baseline.