avatar

To be fair, I'll add the feedback received from a friend on this article:

Quote:
Such issues with communication should be solved with scope definition, which should depict customer needs. It can be anything - a Req Spec, a Statement of Scope, etc. You should have imposed an implementation constraint: we would like to stick with our existing CMS. Based on an _agreed_ scope definition document, they should have
- drawn a solution,
- run it by you (!!!),
- created WBS,
- estimated effort (in MWH/MWD) (a huge separate topic),
- estimated duration (in Hours/Days),
- calculated costs.

This is all very general, of course. Any communication issue is "between", not just on one side. You should have explained the implementation/design constraints to the service provider, yet they should ask for it.

To which I replied that, in my opinion, our goal was explained with enough clarity. This may be subjective matter, of course, and the provider may have missed the nec...