The Difference Between Project Descrip-Requiremnts and Scope

[JordanR]

Hello,
I know that the answer to this question should be obvious but I am a wet behind the ears at having Project Management responsibilities so if someone could briefly explain or direct me to the answers to the following question I would be greatly appreciative.

What is the difference in a Project:
Description? Scope? and Requirements?

Thanks!

 

[johnherman]

Definition I can't help you with.

Requirements are divided into two main parts, business requirements and technical requirements. Most of the focus is on business requirements. These are specifications and features that the users (business) has demanded from their new (or improved) system. Scope is a term which defines how many (and to what degree) the business requirements will be included in a particular portion of the project. For instance, across the total length of a project, all business requirements might be in scope, but for Phase 1 (or Stage 1), only the requirements related to CRM and ERP might be in scope. These would be specifically identified as being in scope, so that any changes brought to the table by the business could be labeled as scope change or postponed to another phase/stage of the project (and might be a scope change there).


Sometimes the grass is greener on the other side because there is more manure there - original.

 

[JordanR]

To outline your response;

Project Scope
Phase/Stage 1
1.(list)Business Requirements (specifications and features demanded from their new (or improved) system
2.(list)Technical Requirements

Should there be any changes;

Project Scope (slight different from the first Scope)
Phase/Stage 2
1.(list)Business Requirements (specifications and features demanded from their new (or improved) system
2.(list)Technical Requirements

Did I capture that correctly?

 

[johnherman]

Yes, I believe so, except that the scope change (if approved by the project sponsor) would apply to the current stage/phase (stage phase 1 in this case, not 2). If the change was deferred to stage/phase 2, however, then your representation is correct.

The change in scope could be an addition , subtraction, or alteration in the way things are to be done.

Examples of technical requirements: must run on Unix (or Oracle). Must be written in corporate approved forms interface (say, Business Objects). Must have response time of less than one second per query. Etc.

Sometimes the grass is greener on the other side because there is more manure there - original.

 

[JordanR]

Thanks John!
You have been very helpful.
Jorda

 

[PDQBach]

Ask ... no INSIST ... that your company pay for a membership in PMI (about US$125). Then download the PMBOK Guide. It's dry, tedious reading but it's a well-structured document that outlines everything you have asked plus lots more.

If I were you, I'd also pony up the additional US$20 or to join a local chapter and start attending their meetings. Generally speaking, you'll find a lot of experienced people more than willing to share their knowledge.

(For the record: yes, I am a PMI member.)

 

[JordanR]

PDQBach,
Thanks for that info. I will definitely look into PMI

 

[BNPMike]

Scope is what is in, as distinct from what is outside of, your project.

The requirements are then related to what is in scope.

Description is a meaningless term.

 

[johnherman]

BNPMike did a good job of summarizing, but I need to add that scope is a relative term. In a long project with many phases, there is scope associated with the entire project as well as scope with the phases. In addition, you can even think of scope at the individual project task level.

Sometimes the grass is greener on the other side because there is more manure there - original.

 

[pnstlion]

You're not real clear on your question but here goes...

DESCRIPTION

I'm guessing you're referring to product description? If that's the case, then this is simply descriptive documentation that will evolve as the product comes to life.

There's also scope definition (not sure if this is what you meant), which is breaking down the scope into managable pieces. End result is typically a WBS.

SCOPE

Scope relates to the particular project's products and services, whether it's the creation of or enhancement of.

Keep in mind that there's product scope and project scope.

Product scope - the features and functions that characterize a product or service.

Project scope - the work that must be done to deliver a product with the specificed features and functions.

[Source: PMBoK, 2000 Edition]

REQUIREMENTS

Depending on what industry you're in, there are many types. In addition to the aforementioned requirements (i.e. business, technical), there could also be functional/non-functional, performance, design, etc...

As a rule of thumb, requirement should be written as a series of one-liners and only state WHAT needs to be done, not HOW it's done. For instance: The system shall provide a mechanism for a user to enter the customer's phone number.

--------------
Anyway, hope this helps.

-Gabe Young, MBA, MCT, PMP