Scope spread and progressive details of software requirements

There is such a PMP test simulation question:

Which of the following statements is incorrect:
A. Scope spread is a function or service that is added without evaluating the impact on time and cost.
B. Out-of-control changes usually refer to the spread of scope.
C. There is no essential difference between scope spread and progressive details of functional requirements.
D. Scope spread does not always increase customer satisfaction.
The correct answer is C.

It is very important and difficult to grasp the customer's software requirements for software projects and especially manage software projects. Project requirements are easy to change and spread. It is difficult for customers to clarify their own needs at the beginning, and the requirements are difficult to confirm. the requirements after confirmation often change, changes in requirements can easily lead to project cost improvement, progress delays, and quality risks.

Many of the project-related consequences, the customer problems, and the service provider problems are unclear. The software service provider said, "You are not certain about your requirements. We cannot start development .", The customer said, "It is impossible for me to clarify all the requirements at the beginning. You should do this first and then improve it later ."; After the software is developed, the customer says that it is not in line with their needs. To change it, the software service provider says "your requirements have changed." The customer said, "My requirements have not changed, it is more refined than before ".

One of the inspirations of this PMP question is that it is necessary to establish a conceptual difference between "Scope spread" and "progressive details" with the customer. In "scope management" of a project, "Scope spread" is essentially different from "progressive details" of the scope:

"Progressive details" is normal, that is to say, the scope of the project cannot be very clear at the beginning, and it needs to be supplemented, refined, and improved continuously. This is an objective rule.

However, "spread of scope" is abnormal and dangerous. It is "a function or service added without evaluation of its impact on time and cost" (answer ), it is a "out-of-control Change" (Answer B), which is an important issue frequently encountered during project implementation.
First, because the demand requires "progressive details", the project cannot guarantee that after the requirement analysis report is signed and confirmed, all requirements will be locked, in essence, the customer cannot undertake this responsibility in essence. But what we need to clarify with the customer is: which new demands are classified as "progressive details" (which have not been clearly stated before, but are now refined ), which of the following are "Scope spread" (beyond the original scope framework) and need to be included in "demand change"Program.

In real projects, this is really difficult, and too many demands are unclear. If such a problem occurs, the project manager must fully communicate with the customer. As long as the facts and principles can be put in place, the Project Manager can achieve a win-win effect. Most customers are reasonable. The key lies in how facts are arranged? Why? This will test the business capabilities of the Project Manager (not only can accurately understand the original needs of the customer, but also want to be ahead of the customer), technical capabilities, project management capabilities, and communication skills.

In addition, the project manager must always be alert to the spread of scope, which is an extremely important role of the Project Manager! Even if it is troublesome, do not promise the customer easily. Remember that "Scope spread does not always increase customer satisfaction" (Answer D )! Because the customer's requirements or solutions are likely to be incorrect or inappropriate, and then rework will not only be costly for the service provider, but also seriously delay the project progress, it is not good for customers.

When a customer proposes a new demand for scope spread, it must evaluate its impact on progress, cost, and quality (scope, progress, cost, and quality constraints ); if it is a major issue, make sure to follow the "formal" change process as much as possible. The change should be approved by the CCB (Change Control Board), including the customer and our key stakeholders. (According to PMP, all changes are formal and written. Although it is difficult to achieve this in reality, this is the direction ).