Based on lecture materials for the course thus far and your previously completed homework assignments, create two items:

(1) a complete work breakdown structure (all project work packages) and

(2) a traceability matrix for your case study project.

For your WBS, your MS Project file must contain, at a minimum, the following features:

1. ALL work packages related to your project (your WBS should apply the “100% rule”, and don’t forget to include any work packages related to verifying requirements, as you identified in your scope statement last week!)

2. At least three WBS levels, not including the overall project level. So your WBS (at a minimum) should look like this:

OVERALL PROJECT NAME

1.0 WBS level 1

1.1 WBS level 2

1.1.1 WBS level 3

3. A “code of accounts” (numbering scheme) for each WBS line item. Note: MS Project will number your WBS items automatically if you insert a column entitled “WBS”, but automatic numbering can be tricky to manage. You may want to assign numbers to your WBS as your final step.

4. You MUST complete your WBS using MS Project. Either MS Project 2007, 2010 or 2013 is acceptable.

Your Traceability Matrix should contain, at a minimum, the following features:

1. A list of the business requirements you identified in your business case in course week 1

2. A list of the solution requirements you identified in your scope statement in course week 4

3. Your WBS

4. Keep in mind the purpose of a Traceability Matrix is to show how each line item from your WBS supports at least one of your solution requirements AND at least one of your business requirements. (Hint: if you can’t determine which business or solution requirement an item in your WBS supports, are you sure you need that WBS item?)

5. Similarly, each solution requirement should support at least one business requirement.

6. You do NOT have to use MS Project to complete your Traceability Matrix, so long as you do use Microsoft-compatible software. If you choose to include your traceability matrix as part of your MS Project file, you may find inserting additional columns to identify the business and solution requirement that pertains to each task a useful way to show this link.

Since this is not a project scheduling class, you are NOT required to identify:

1. Task durations

2. An overall project start date, or calendar start and finish dates for tasks

3. Resources assigned to each task

4. Dependencies between tasks, or the project’s critical path

As with your other written assignments, this assignment is to be completed individually.

Once completed, save your file(s) using the following filename convention:

Lesson 5 HW – [your last name]