Discussion on:

Define project scope to include deliverables, boundaries, and requirements

Dear,

Just want to say may be we can't discuss some articles because of time limit but most of articles whatever its simple, its good to read and review.

Thanks!

Although it's implicitly mentioned in the article, I'd reiterate and reinforce the need to define explicitly what is OUT of scope as well as what is in scope.

Asking the question as to what the project is not covering makes scope more definitive, and also helps to correctly set boundaries by asking questions such as: "If not for non-USA locations, what are they doing to do for x process?"

Out of scope definitions will often save your bacon further into the project. Further into a project, in-scope only definitions can be ambiguous when more about the project is defined and known.

For example, US territories may not be explicitly in or out. The project has assumed out, the customer has assumed in.

Clearification is direct and well directed. I think the examples are fantastic.

"Once the project starts, however, you generally do not have a lot of requests to change boundaries and deliverables"

I'd take issue with this comment, I find users frequently try to add to the deliverables list after the project starts. Maybe its just the nature of creating software products, but they think nothing of requesting just "one" more piece of functionality. Heck, sometimes they ask for entire new departments to be included in the project scope.

People always want to add "just one more item/feature" to the project. One of the project manager's tasks is to make sure the project stays within the scope and does not suffer from scope creep. This is not to say that the folks wanting the new feature do not have a great idea--it is just not great for the present project--however it could make for another project down the road.

I have never came across a software project where requirements didn't change or new ones were not added once customer requirements have been agreed and signed off. Despite the fact that new added requirements are mostly the cause for project scope changes but very often we see the same requirements being modified few times before they get finaly implemented.

would be great to have an example of a software development project


thank you all

Good article for all having to write Scope documents.

Learn how to define project charter - learn the proper method :

http://www.innovativeprojectguide.com/business-case-project-charter-project-plans/14-business-case-project-charter-project-plans-/94-how-to-define-project-charter.html