SensKat wrote: You know what grinds my gears? Users that send you a "signed off" Business Requirements Doc.... and then spend the next 2 weeks sending you "additional requirements", "spec updates"... and don't understand why you can't give them dev estimates.
You know what stops that?
Replies of "out of scope / no further requirements accepted other than through the formal change request process". You will get some short-term friction, but I found it worked pretty well in the longer term.
Yeah, we've tried that. Then they just refuse to sign off on UAT, and escalate through management on both sides. This particular client has probably more power than they should.
This project has been underway for 14 months now, they decided they didn't like what was delivered (even though it was on spec), and now we are in the process of redefining the requirements and starting over from scratch.
They want 7 blue lines, 2 with red ink, 2 with green ink and all perpendicular to each other?
SensKat wrote: You know what grinds my gears? Users that send you a "signed off" Business Requirements Doc.... and then spend the next 2 weeks sending you "additional requirements", "spec updates"... and don't understand why you can't give them dev estimates.
You know what stops that?
Replies of "out of scope / no further requirements accepted other than through the formal change request process". You will get some short-term friction, but I found it worked pretty well in the longer term.
Yeah, we've tried that. Then they just refuse to sign off on UAT, and escalate through management on both sides. This particular client has probably more power than they should.
This project has been underway for 14 months now, they decided they didn't like what was delivered (even though it was on spec), and now we are in the process of redefining the requirements and starting over from scratch.
SensKat wrote: You know what grinds my gears? Users that send you a "signed off" Business Requirements Doc.... and then spend the next 2 weeks sending you "additional requirements", "spec updates"... and don't understand why you can't give them dev estimates.
You know what stops that?
Replies of "out of scope / no further requirements accepted other than through the formal change request process". You will get some short-term friction, but I found it worked pretty well in the longer term.
Also, Canuck has mentioned this in person, I believe on the show too.
If Pittsburgh would have challenged the Ceci goal, they could have discussed what they did on their timeout with equal or greater time. Lack of strategy by not doing that.
