You are assigned a project for a former client who is known to request extra scope without considering impacts on schedule, cost, quality, or risks. What should you do to plan and control budget and resources?

The correct answer is to include a scope change process and review the project charter. Given the client's history of frequent scope changes, establishing a formal scope change process is crucial. This process ensures that all requested changes are properly documented, assessed for their impact on schedule, cost, quality, and risks, and approved before implementation. This proactive approach helps manage expectations and maintain project control. Reviewing the project charter is also important as it defines the project's high-level scope, objectives, and stakeholders, providing a foundational understanding to manage potential scope creep. Refusing to allow scope changes is unrealistic and uncollaborative; while lessons learned are valuable, they don't prevent future issues without a process. Decomposing deliverables and reviewing the charter are good practices but don't directly address the control aspect of managing a client prone to scope changes. Creating tight scope statements is part of good planning but, without a change control process, it won't prevent unauthorized changes.