592W2

Component Deliverable

Tasks

Scope Statement

1. Create the project scope statement, which is an extended version of your project proposal. It primarily aims to clarify two aspects of the project—setting the acceptance criteria so you can have a smooth closure at the end of the project and rules and regulations to decrease the ambiguity in the team while managing the project. For your convenience, the Project Scope Statement Sample document is available in the Project Resources and Naming Conventions section.

2. Submit the scope statement in a one- to two-page Word document.

Detailed Resource Loaded Baseline WBS and Schedule

1. This is the part to extend the preliminary tasks (approximately 10 lines) you had in Part 1. Using your scope statement, input your work packages into MS Project. The WBS should be created in MS Project, following standard indent and hanging indent practices used in WBS creation. The WBS and schedule must have proper grouping, indenting, and coding for approximately 25 to 40 line items. Review the Project Sample in the Project Resources and Naming Conventions section for an example of a well-developed work breakdown structure

a. Create the WBS column. Hover on the Task Name column and right-click for the drop-down menu so you can select Insert Column, and then type in WBS manually and select the WBS to have your outline numbers.

b. Review your duration. (Hint: Please remember, do not touch the bold task. Manage the content of the bold, also known as summary tasks, because those tasks are aggregated automatically.)

c. Review your predecessors. This is to mimic the conditional tasks we have in real-life. As seen in the following screenshot, if you put the number 4 as a predecessor for line 5, line 5 cannot start before line 4 finishes first.

d. Create the critical path by selecting Gantt Chart Format>Critical Tasks. This is to know which tasks of yours (usually color coded in red bars on the Gantt Chart) are more critical (that means zero free or slack time) so you can be more cautious (with contingency plans) about them.

2. Baseline Resource Plan

a. Define your resources by selecting Resource>Team Planner>Resource Sheet. You do not fill each cell. Some are being used as-is. You may want to work on the blue zone. Also, 100% means one person, 200% means two people, so forth. Once you are done, you may want to go back by selecting on Team Planner>Gantt Chart.

b. Assign your resources task by task. Hover on the task (not summary task, which are the bold ones) and right-click to select Assign Resources. Then review the units. You will see the cost will be populated automatically. Then select Assign or just close the window.

3. Submit the WBS and Schedule in either a MS Project file or as a screenshot.

RACI Chart

1. Develop a RACI chart, responsibility assignment matrix, for the project according to the description in Section 10: Tools and Techniques and illustrated in Figure 10-18 of the  Process Groups: A Practice Guide.

2. Submit the RACI Chart in a Word or Excel document.

Project Name

Project Number

Project Manager

Prioritization

Owner(s)

Statement of Work—Project Description and

Project Product

This section is a detailed amplification of the project statement of work (SOW) and mission from the project charter. This also includes how you intend to accomplish the project. “We intend to do this… And here are the steps we intend to use to accomplish the project.”

This section is a detailed amplification of the SOW product description from the project charter. What will the product of the project look like, or what should it be able to do when completed?

Project Deliverables

What are the tangible outputs or services of this project? What big picture items will have to be created or performed in order to accomplish the statement of work? These are the deliverables to be found in the work breakdown structure (WBS).

Project Objectives

What are the cost, schedule, and quality objectives of this project?

Project Assumptions

What are the assumptions on which the project is based on?

Project Constraints

What are the major limiting factors that affect the project?

Exclusions

What are the boundaries of the project? What is to be included, and what is to be excluded from the project?

Acceptance Criteria

What must the product be able to do when completed to be acceptable to the customer? What standards or regulations must the product meet? What performance specifications must the product meet to be acceptable to the customer?

Approvals