Tell me more ×
Project Management Stack Exchange is a question and answer site for project managers. It's 100% free, no registration required.
up vote 2 down vote favorite

They are not projects, as one project contains more groups of deliverables. Is milestone a correct term?

I hope the chart below explains it a little.

share|improve this question
1  
WBS has levels. Between the top level and the "deliverables" there could be multiple levels, so each of those levels should have a name. If you search for a general term for items in levels, consider "scope elements". – Bartosz Rakowski Apr 17 '12 at 10:14

3 Answers

up vote 2 down vote accepted

As Bartosz writes in the comments, there can be multiple levels between the top and the lowest level of your WBS, and the number of levels of each sub-tree depends upon the deliverable itself.

Now, the first level often depends upon how you wish to structure your WBS: it could be by project phase (if each phase has distinct deliverables) or by product. We often use the release number, if the project contains multiple releases, besides the other main deliverables. This makes it easier for the customer to see what they will get in each release.

We just call the first level the "main" or "major" deliverables, and it is broken down into sub-deliverables. The lowest level are called "Work packages", as normally you don't break them down any further but define the tasks needed to realise them. Tasks belong in your schedule, however. I prefer to keep the WBS free of tasks, so as to make it deliverable-focused.

So my first level would read "website" or "planning board", and it would be broken down from there up till the level that I wish to manage.

A milestone is part of a schedule, and indicates that a deliverable is completed at a certain date like "Website released" or something like that.

share|improve this answer
I am a little confused on what you mean by deliverable-focused. Is that the same thing as a product breakdown? – ONOZ Apr 19 '12 at 13:32
up vote 2 down vote

Some suggestions:

  1. Hammock
  2. Control Account
  3. Parent Deliverable / Activity
  4. Sub-project
  5. Group of deliverables
share|improve this answer
David, Do you define Control Accounts always on the first level of the WBS? We assign them further down as well. It depends upon the level of detail you or your SteerCo/Sponsor wish to manage. – Stephan Apr 17 '12 at 10:48
1  
I define a control account based on the size of the $$ and staffing (same thing, really). At that level of the WBS, I want a single leader on it, which means the span of control needs to be appropriate. So it can be anywhere in a multi-level WBS, just at that level where span of control is just right, e.g., 10 to 15 resources?? – David Espina Apr 17 '12 at 11:06
OK, same thing indeed, thanks! – Stephan Apr 17 '12 at 11:22
up vote 0 down vote

Unfortunately I don't seem to be able to view your chart, but how about calling the group either a phase, stage or a work package?

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.