Scope creep is the change or expansion in the project scope that occurs without proper assessment and approval. It can result in cost overruns, delays, and client satisfaction issues. Scope creep can happen due to unclear or changing requirements, lack of stakeholder involvement, poor communication, or inadequate change control. To prevent scope creep, business analysts should define the project scope clearly, manage stakeholder expectations, document and prioritize requirements, and follow a change management process.
References:
* Scope Creep: Definition, Examples & How To Prevent It - Forbes
* What is Scope Creep and 7 Ways to Avoid it [2023] * Asana
* What is the meaning of Scope Creep in Project Management?

The timing of business analysis work in this project should be defined by the overall project schedule, which is the plan that outlines the sequence and duration of project activities and tasks. The business analysis work should be aligned with the project schedule to ensure that the deliverables are completed on time and within the scope and budget of the project. The business analyst should also consider the dependencies, risks, and constraints that may affect the timing of business analysis work, such as the availability of stakeholders, the complexity of requirements, the quality of data, and the change management process. The business analyst should communicate and coordinate with the project manager and the solution consultants to ensure that the business analysis work is integrated with the project schedule and meets the expectations of the sponsor and the PGA staff.
References:
* BABOK Guide v3, Section 3.2: Plan Business Analysis Approach, p. 48-49
* CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 2: Business Analysis Planning and Monitoring, p. 51-52
* Certified Business Analysis Professional (CBAP) Specialization, Course 1: Business Analysis:
Planning and Communication, Week 2: Planning the Business Analysis Approach, Video: Planning the Business Analysis Work

According to the BABOK Guide, a change-driven approach to business analysis is characterized by frequent delivery of value to stakeholders, iterative planning and feedback, and adaptive responses to changing needs and priorities. In such an approach, communications are managed by focusing more on the frequency of communication and using face-to-face channels as much as possible. This helps to ensure that information is shared quickly and effectively, and that feedback loops are established and maintained. Formal communications are less emphasized in a change-driven approach, as they may slow down the delivery process and introduce unnecessary overhead. Ad hoc communications are not sufficient for managing change- driven projects, as they may lead to inconsistency, confusion, and missed information. References:
* BABOK Guide, section 2.5.3, page 35
* How to create a business analysis communication plan, paragraph 2
* CBAP/CCBA/ECBA Certification Practice Test, question 8

A feasibility study is a type of document that evaluates the potential solution alternatives and their expected benefits, costs, risks, and impacts on the organization and its stakeholders. A feasibility study also provides data and statistics to support the analysis and recommendations. A feasibility study helps the decision makers to select the most viable and beneficial solution for the business need.
References:
* CBAP Handbook, page 10, section 3.4.2.3
* BABOK Guide, page 100, section 6.1.5.2

The implementation approach is a component of the solution scope that describes how the chosen solution approach will deliver the solution scope. The solution approach is the method or process that will be used to implement the solution, such as a predictive or adaptive approach. The solution scope is the set of capabilities and features that the solution must provide to meet the business need1. The implementation approach explains how the solution approach will be applied to achieve the solution scope, such as the phases, activities, tasks, deliverables, and resources involved. The implementation approach also considers the risks, issues, assumptions, and constraints that may affect the implementation process23.
The other options are not correct. A. The implementation approach is not described in terms of the major features and functions that are to be included, as this is part of the solution scope, not the implementation approach. B. The implementation approach does not define major business and technical dependencies that impose constraints to the effort to deploy the solution, as this is part of the risk analysis, not the implementation approach. C. The implementation approach does not describe the new capabilities required to meet the business need, as this is part of the solution scope, not the implementation approach. References:
* Solution Scope - IIBA
* Defining the Business Analysis Approach in 2023 | Free Template
* Business Analysis Planning and Monitoring - IIBA