Scale
| Topic | Criteria | Max | Your Points | Comments |
| Organization | Hierarchical - level of detail | 15 | 15 |
| | Use of Summary tasks | 10 | 10 |
| | Organized by component, deliverable, or phase | 10 | 10 |
| Completeness | Product Deliverables
Project Deliverables
PM Deliverables - Plans, Status, Quality, Communication, M&C
| 20 | 20 |
| | Decomposition toward work packages | 15 | 15 |
| | Milestones | 10 | 10 |
| Clarity | Presentation -
Noun (functionality, components), Verb (SDLC methodology, phases, objectives)
Logical group (Location, Function) | 10 | 10 |
| | Work "flow" start to end
No obviously missing work | 10 | 10 |
| Penalty | | | | Comment |
| Assignment total | | 100 | 100 |
Create a Work Breakdown Structure for your selected project
Using the information provided in the Ambriz and Wysocki books, along with the handout posted in the Additional Resources section of this unit, create a WBS for your selected project. At a minimum, you should identify summary tasks, detail tasks, and milestones.
You want to provide the appropriate level of detail while maintaining a reasonable number of tasks since you will be expanding on the same project schedule through the semester. While there is no minimum or maximum number of tasks, the expectation is that most students will have somewhere between 50 - 100 tasks in their WBS which will then be entered into Microsoft Project next week.
Post to forum link below and using the texts and the handout, describe the process that you used to build your Work Breakdown Structure.
Prepare your Work Breakdown Structure and upload it using the link below. You can use any format you would like (Word document, Excel worksheet, Visio diagram, Project file).
Sample Work Breakdown Structure (in Excel format)