Dissecting an Agile project from Hell

TalkBack 1 of 19:

Next »

• Thread View
• Flat View

SOWs and Scope

Just read it - very nice. I have often found a desire by some consultants to keep the scope very broadly defined in the SOW. The project is Agile so scope is variable and this is perfect, right? I've seen the anti-pattern you described so well before.

Having mid-level scope *and* the business drivers/objectives that define the scope in the contract is critical. Agreement on the objectives helps frame push-back conversations that should have taken place (customers can be dismissive of the project team otherwise).

Also, contracts are often signed and then shelved. Not that I'd advocate constantly reminding a customer of the contractual terms, but it should be a living document and everyone on the team should have at least a cursory understanding of what was agreed to.

Posted by: candrasick   Posted on: 10/27/08 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• CDW Services Overview: Unified Communications CDW Businesses that utilize unified communications solutions empower employees ... Download Now
• The True Costs of Virtual Server Solutions VMware In an economic environment that is repeatedly heralding the message "do ... Download Now
• Server Consolidation and Containment With Virtual Infrastructure VMware To meet the constant demand to deploy, maintain and grow a broad array of ... Download Now