Do you keep your client informed of progress?
  v6.0 Posted at 24/07/2015 10:41 AM by Ulysses Maclaren

A client will always prefer to be told ahead of time if a piece of functionality is going to take longer than anticipated. It gives them more control of what is going on. The other opinion is landing them with an oversized invoice with no warning.

For this reason, blowouts should be reported in the Daily Scrum, as well as any major delays being told to the client as soon as possible, so that they don't get a big surpirse in the Sprint Review. 

For big delays, it's best to tell the client as soon as the risk is identified to inform them of what's going on and ask "Do you want us to continue?".
$100k estimate. Calling the client when you reach $110k to say you have $20k to go.​
Bad Example: Not giving the client enough warning.
$100k estimate. Calling the client when you reach $80k to say you have $40k to go, and does he want to continue?
Good Example: Giving the client a warning ahead of time and asking for permission to continue.

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address:


    Note: Social Media login for Yotpo is not working in IE or Safari, please use Chrome. We are waiting for Yotpo to fix it.