What is the solution scope and why is it required?

Let's start by defining the term solution in this context. The term solution here simply refers to the outcome or result once a change has been implemented in order to meet a particular business need.

Whereas the solution scope defines the new capabilities and functionality that will be included as part of the change. It also includes a description of how it will solve any identified current state issues or problems and how it will meet the goals set for the desired future state.

The solution scope can often also include descriptions of aspects that are not included in the scope and are deemed out-of-scope components. 

Let's now consider a real-world example: An architectural design company's stakeholders have identified that the company website is not generating the number of leads they need to grow the business effectively. They have determined that there is a need to improve the number of leads that are generated by the website and that a change needs to be made to the website to facilitate this change.

A website development company is briefed on the current problems they are experiencing with the current website and asked to come back with a solution scope of what they believe needs to be changed in order to achieve the desired future state (more good leads). When the website development company provides the documented solution scope, they include the following:

• The look and feel aspects of the website to generate more leads
• Additional lead tracking software
• Additional online marketing options
• A better-structured website to assist in lead generation as part of the solution scope

In addition, they have suggested documenting internal business processes that should be enhanced to be able to process the incoming leads more effectively.

This example illustrates that the solution scope can be described in different ways and can include change aspects such as capabilities, technology, processes, and so forth.