Scope Change Request Essay

1057 Words3 Pages

Another scope change request arrived this week. And how many of them have already arrived so far? 4, 10, ...? Why do customers constantly change their requirements? Is it indecision, lack of definition or the result of a bad requirements elicitation? In this blog, I will present some tips that we use at Intraway for a good requirements elicitation and thus, to get a clear definition of the scope of a project. Why do scope change requests arise? Every project is born from a "stimulus", such as the need for a business, market demand, profit, technological advances, legal and social requirements, among others. The reason of life of a project, however, may be subject to change over time. In three months, for example, there may be a new technology that requires us to adapt the direction that we had planned. In this context, changes are completely valid, substantiated and necessary to ensure that the product/service we are building has value to the customer. But, what happens with those requirements that were not gathered at first, but that already existed in the client's head, those hidden requirements that come to light after the project has advanced? These are the changes that we must avoid, because all change has an associated cost. The aim of a good Requirements Elicitation, and our goal as functional analysts, is to …show more content…

It is necessary that the client understands the benefits of a good Requirements Elicitation. We must put an end to the poses: "The Requirements Elicitation is a loss of time. Starting to develop as soon as possible is better" (even if it means not having clear what we have to develop) or "With a session of Requirements Elicitation is enough, I have no time" (when the time and cost of implementing a change after will be higher). Customers must have an active role in the search and decomposition of their needs in

More about Scope Change Request Essay

Open Document