A scope review is an important process that all stakeholders must undertake as a strategy to build trust and deliver better value. Stakeholders are those people who will receive direct benefits from a project, such as patient care, nursing care and the provision of goods and services. Their involvement in a project is a key driver to ensure that the delivery of a project delivers the key stakeholder objectives. The objective of the review is to identify issues or challenges that may affect the delivery of the service and to identify and address these issues in order to make a business case for making the necessary changes. This article looks at the process of scope determination and scope review in nursing care and hospitals.
Over the last few years there has been a trend for hospitals and other health organisations to conduct product development budgets in line with their existing or projected budget. Product development is often a lengthy process requiring considerable planning and preparation. One of the main concerns raised by stakeholders is the risk of scope creep. Although it can be prevented by careful planning and a well thought out implementation strategy, scope creep can still occur if there is not a controlled way in which the planning is done. Scope creep can also occur due to poor communication between the stakeholders and the Product Owner.
The key stakeholders are the clinical and organizational professionals who will ultimately see the results of the project. They will need to be satisfied that the planned project meets their needs and delivers value. In order to be happy with the scope they need to know that the product scope will be delivered as part of the original agreed service plan. When communicating with the Product Owner, they need to describe the scope clearly and establish clear expectations of scope management to avoid scope creep.
The scope being reviewed is typically the first focal plane on which the organization will develop a concept map. It is important that the scope does not become overly technical causing management to misunderstand the scope as being technical in nature. The first focal plane that should be identified for scope implementation is a set of measurements on the health, safety, quality, and functional aspects of the project. This first focal plane needs to be tightly focused on the areas that will be tested or evaluated.
As part of developing the scope definition the stakeholders will also need to determine what technical features or sub-features they want to be included in the product lifecycle. The scope definition needs to define each and every feature in the scope and identify the scope-specific reporting and feedback requirements. Once all features in the scope are identified and detailed, it is time to start writing requirements according to the scope.
The next step in the process is the development of the common vision of the stakeholders. This step helps the organization to identify the areas in scope that are of highest importance to the stakeholders. Achieving the common vision results in a much more tightly defined scope, and it reduces scope creep.
Once the organization has developed and refined its common vision and the product lifecycle phase is completed, it is time to start writing the requirements. The requirements will require input from all stakeholders. Each and every stakeholder should be involved in the requirements writing process. When writing the requirements to make sure to keep in mind the impact each requirement could have on each and every stakeholder. Make sure to document each stakeholder’s opinion on the scope, which includes the impact on them as well as the other stakeholders.
Writing requirements is an important part of the process of getting a successful scope improvement contract. Remember that you need to take into consideration the opinions and feelings of all the stakeholders when you are developing a scope. Achieving the shared vision during the writing requirements process will reduce scope creep. Also remember to document all the feedback you receive throughout the project so that you can measure and improve the system over time.