Project Management Central

Please login or join to subscribe to this thread

Topics: Communications Management, Scope Management, Stakeholder Management
At customer's time to pay
Network:987



How many times has it happened to you that when the customer pays you start a process: "It was not in scope ... it was in scope"?
How did you solve these situations?
Sort By:
Network:1624



Luis -

Why are you waiting till the customer pays?

Defining the scope of the project to an appropriate level of detail should be done well before we are "settling up". Between that and having disciplined requirements management & change management processes you should be able to reduce the back & forth with the customer.

If the project deliverables are very conceptual or complex, using an adaptive lifecycle in place of a predictive one might also help to reduce this challenge.

Kiron
...
1 reply by Luis Branco
Sep 25, 2019 10:41 AM
Luis Branco
...
Dear Kiron
It is exactly in a situation corresponding to an adaptive life cycle that this situation is happening
Network:987



Sep 25, 2019 7:10 AM
Replying to Kiron Bondale
...
Luis -

Why are you waiting till the customer pays?

Defining the scope of the project to an appropriate level of detail should be done well before we are "settling up". Between that and having disciplined requirements management & change management processes you should be able to reduce the back & forth with the customer.

If the project deliverables are very conceptual or complex, using an adaptive lifecycle in place of a predictive one might also help to reduce this challenge.

Kiron
Dear Kiron
It is exactly in a situation corresponding to an adaptive life cycle that this situation is happening
...
1 reply by Kiron Bondale
Sep 25, 2019 4:54 PM
Kiron Bondale
...
If so, then it depends on what we mean by "scope". If we are referring to a key feature or major need, then normal change control might still be required in an adaptive context. If we are referring to a detailed requirement, then changes to those is expected in an adaptive context and then the only consideration should be what lower priority requirements might not get delivered if we are dealing with a fixed funding or time envelope.

Kiron
Network:1624



Sep 25, 2019 10:41 AM
Replying to Luis Branco
...
Dear Kiron
It is exactly in a situation corresponding to an adaptive life cycle that this situation is happening
If so, then it depends on what we mean by "scope". If we are referring to a key feature or major need, then normal change control might still be required in an adaptive context. If we are referring to a detailed requirement, then changes to those is expected in an adaptive context and then the only consideration should be what lower priority requirements might not get delivered if we are dealing with a fixed funding or time envelope.

Kiron
Network:596



Very interesting observation.I think sometimes it depends on the type pf customer you have and particularly their payment culture in regard to promptness.Where you have a customer who delays payment or you have to do several follow ups for payment to be made......then you may be inclined not to commit so much resources on the project during the period of delay.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Only those who have been in the frying pan are really qualified to talk about the heat."

- Winston Churchill

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events