This is an old link ... let me redirect you ...

(... or click here if the page does not automatically redirect)

Tactics for Controlling Project Scope

I wrote about ways to "cheat" at project prioritization [aka trying to figure out what to work on next, when there is more demand (projects) than supply (people to work on them)]. One significant tool you have at your disposal is controlling scope - can you do 20% of the work to get 80% of the benefits?

Easier said than done, sometimes you need tactics, that help identify an opportune place to stop, a run-on project, or a design that is"simple enough".

Click on the picture for a full-size image!

The folks at Big Contacts liked the idea so much, they tout it as a feature ...

With Big Contacts there is no user manual. Because once you create a user manual, you are admitting your application is too difficult and that people need a book to use it.

Let's steal that idea for our projects. No documentation required, because the deliverables (process, technology) are simple and common sense enough that people don't need a manual, a training class, etc.

Ok, maybe it's not "practical", but it's a Worthy Goal that could help keep scope down to a dull roar ...

Previously ...

Technorati Tags: , , , , ,

Labels: , , , ,