Any unauthorized change to the scope that results in project delays is known as scope creep. When something is overlooked and not covered in the initial requirements document, it needs to be itemized and added to the project scope. This process is known as scope creep, and it can result in budget overruns whenever problems arise with the acquisition of more staff members or other resources, like equipment. The timeline and schedule of the project could be affected due to scope creep (Sipes & Faan, 2019).

When an institution implements an electronic health record (EHR) or modifiesalready-established EHRs to implement new interventions or process improvements, it's critical to identify and involve the appropriate stakeholders. According to research, when a team tried implementing Quit Connect Healtha QI intervention that links smokers to state-sponsored tobacco cessation linesit was delayed due to stakeholder creep. In May 2015, Quit Connect Health began working with leaders of the health system with the goal of becoming online in January 2016. However, the real launch date was in late April 2016, which was three months over the target. The number of parties involved exceeded projections, resulting in more work and time than planned for the project. The root cause analysis carried out after implementation is like "EHR IT is a single group," "all EHR IT members know the full scope of EHR functionality," "changes to an EHR need the input of just a single EHR IT member," and "the technological complexity of a project mirrors the clinical complexity" (Panyard et al., 2018).

What is your comment/feedback on this statement. Please add 1 reference. Thank you.

FYI, this is the question of this answer: What are some of the downstream implications for a change in scope on a project? Provide a specific scenario to support your answer.