Comments on: Defining Scope using Deliverables

By: Howard Vaughan

Howard Vaughan — Mon, 20 Jun 2011 10:30:19 +0000

Thanks Justin – I fully concur.
There is an art to writing clearly and concisely and using simple but powerful tools to assist, especially when the mind is full of thoughts and ideas.
I believe this is a critical PM skill.

By: Justin

Justin — Sun, 19 Jun 2011 16:47:03 +0000

This is a really helpful article. Sometimes I find it hard to define my project and find it most annoying to reading project scopes that are flowered by adjectives and doesn’t really give insight as to what the project can realistically deliver. Awesome guide. Thanks!

By: isabella

isabella — Wed, 11 May 2011 14:14:09 +0000

I haven’t encountered deliverables since I am not involved in project management. But this post clearly emphasized how to clarify the scopes. It is also interesting how deliverable could bridge any gaps of SOW and WBS.

By: Howard Vaughan

Howard Vaughan — Sun, 08 May 2011 01:43:26 +0000

Thanks Justin – in a complex world its gratifying (and a relief!) that simple concepts still offer profound, positive impact in defining, planning and managing projects.

By: Justin

Justin — Sat, 07 May 2011 20:13:58 +0000

Great information. I particularly like point number two where you mentioned about the is/is not formula. This simple formula is a great way to highlight the benefits and also let people know exactly what this plan is not intended to do. Also point number three is a very valid point as well. I think having little checkpoints along the way to show the tasks have been completed is a great way to operate any project. Thanks for the info.

By: Nürnberg

Nürnberg — Sat, 23 Apr 2011 21:44:50 +0000

Diese Webseite hat mich ernsthaft exzellent auf eine gute Idee gebracht und ist prima geschrieben .

By: A Checklist for Team Readiness « lightkeeper54.com

A Checklist for Team Readiness « lightkeeper54.com — Mon, 08 Nov 2010 13:27:37 +0000

[...] Have the team agreed on who owns which deliverables? [...]

By: pm-lotus | A Checklist for Work Breakdown Structures

pm-lotus | A Checklist for Work Breakdown Structures — Fri, 06 Aug 2010 10:47:48 +0000

[...] the project scope fully reflected in the WBS tasks? – The scope definition of each deliverable should be reflected in all tasks that accomplish that [...]

By: nick gogerty

nick gogerty — Wed, 10 Feb 2010 14:15:04 +0000

An excercise that may help test the efficacy of scope is to test falsifiability. Like a good science a good scope document should be falsifiable in the Baconian scientific tradition. Testing this should be simple and be done before signing off on the scope document. Testing a few statements or potential scope creep litmus tests should be used, so that a loose scope isn’t signed off on. Happy statements are antithetical to effective scope statements that all agree on. Many may at first be uncomfortable stating the negatives used in the test, but it is a good item to check off before signing off on the scoping document. Without constraints in scope, things are open ended wish lists.