As we know, project planning is a very important component to setting the project up for success. Every project, regardless of the project size should incorporate different project planning activities. The result of these activities is the creation of a well-formed project management plan. Project control then builds off the plan as a means for monitoring that the project is staying within the parameters set forth within each plan (e.g. scope, timeline, allocated resources, costs, etc.). Project close also has important project activities in order to validate that a project is completed successfully to the customer's expectations.

Build out a WBS that you can later embed into your project for project planning and project close activities. You may want to search the internet to find different examples of each. You should have things that pertain to building out the schedule, budget, resources, stakeholders, etc for project planning and different activities for project close such as lesson learned, project close report, and client hand-off, etc. Provide the WBS using either as a bulleted list or as a graphic showing a hierarchy of deliverables and work packages. You should include at least five (5) project planning deliverables, five (5) project control deliverables, and three (3) project close deliverables with 2-3 work packages each.

Example (note this is a general idea - it does not follow the requirement of needing 2-3 work packages per deliverable):

1. Planning Deliverables & Activities:

1.1 Complete X Plan

1.1.1 Info Gathering Meeting

1.1.2 Workshop

1.1.3 Building Plan

1.1.4 Sign-off of Plan

1.2. Complete Y Plan

1.2.1 Info Gathering Meeting

1.2.2 Workshop

1.2.3 Building Plan

1.2.4 Sign-off of Plan

2. Project Control

2.1 Complete EVM week

2.1.1 Compute Data

2.1.2 Complete EVM Metrics

2.1.3 Interpret Results

2.2 Conduct Risk Workshop weekly

2.3 Communicate Project Status weekly

3. Close Deliverables & Activities:

3.1 . Complete Z

3.1.2 xx activity

3.1.2 xx Sign-off