How to keep your scope fixed and have a champion project

19 Sep How to keep your scope fixed and have a champion project

Don't let change requests knock your scope out!

One of the challenges when contracting a closed project is to make sure that the scope agreed between the parties is clear and contains everything the client needs.

There should be an effort during the pre-sales phase so that the biggest pains and needs of the customer are mapped to the original scope of the project. Thus, it is possible to set up a fixed scope of work and consequent cost and deadline, so that a proposal can be made considering a Closed Project.

Depending on the complexity of the project, Change Requests are expected to appear.

At the beginning of the project, when we start to detail the user's needs, delving into the client's business, Changes Requests may arise.

Each Change Request must be jointly analyzed by the Project managers - Manager of the Service Provider Company and the Customer Manager. At this time, the signed proposal must guide the project's decisions, so that there is no doubt whether the requested Change Request was already included in the original scope or not.

Once you've come to the conclusion that the Change Request is valid, its pros and cons should be considered: is it a business requirement or is it just a desirable aspect? Are there conditions and alternatives to implement it using standard parameterizations and programs? Can the request be implemented in a second phase of the project?

A large number of Change Requests indicate a failure during the pre-sales phase and stress the project, leaving the entire team – client and consultancy – uncomfortable.

Invest in good pre-sales and withdrawals, before signing the proposal. Present your proposal to the client, discussing each item that will be implemented.

Change Resquests are not project villains, but their quantity must be limited and their effectiveness and necessity proven.