Objective The objective of the Course Project is to give you an opportunity to practice the skills learned in class regarding the planning methodologies of a project. These skills are directly applicable toward your senior project. Guidelines For this project you may choose one that is of interest to you or you may choose to begin planning for your senior project. When selecting a project, avoid picking one that is either too big or too small. For example, do not decide to build a new stadium for your local sports team (too big) or to plant your summer garden (too small). Here are some successful project ideas. The opening of a coffee shop An open house for a local social service agency A meditation pool and platform A redevelopment of a local playground Design and installation of a computer network for a small business Software development project A project to build a house is NOT acceptable. Milestones Due Week 2: Project Charter Due Week 3: Scope Statement Due Week 4: Work Breakdown Structure and Network Diagram Due Week 5: Risk Management Plan Due Week 6: Resource Management Plan Due Week 7: Communication Plan Due Week 8: Final Project Package Deliverables Due Week 2: Project Charter Provide a p roject c harter of your selected project in accordance with the charter template found in Doc Sharing. The project will be the project your team will use for the remainder of this course. For your new project, please develop a project team (citing names, e-mail addresses, and telephone numbers). Be certain to include the following. Project Objectives Project Statement of Work Milestones All other sections as required in the p roject c harter Please put this in proper business writing format. Consider me to be your boss. If working in a group, include a statement of participation, describing how each person contributed to this project deliverable. Please have each person sign the statement. Deliverables: Project charter (in MS Word) If working in a group, include a statement of participation, describing how each person contributed to this project deliverable. Please have each person sign the statement. Due Week 3: Scope Statement Prepare a scope statement using either the model on pages in the text as a template or the scope template in D oc S haring. Remember to be tangible, measurable, and specific. Be sure to include all sections required in the Practitioner section of the W eek 2 L ecture. Deliverables: Project scope statement (in MS Word) If working in a group, include a statement of participation, describing how each person contributed to this project deliverable. Please have each person sign the statement. Due Week 4: Work Breakdown Structure and Network Diagram According to the PMBOK® Guide, "the WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team, to accomplish the project objectives and create the required deliverables." In other words, it lists the project's tasks, the subtasks, the sub-subtasks, and so on. For this phase, you will create a work breakdown structure (WBS) for the project you selected during phase one. Remember that the WBS starts with your major deliverables (that you stated in your scope management plan) at the highest level. The lower levels have the tasks required to complete those deliverables. You should have at least three tasks under each deliverable, but you may have as many tasks as needed to ensure that the deliverables are complete. Review the textbook (and the PMBOK® Guide, if you have it) for some suggestions on how best to create a WBS. From your work breakdown structure, develop a project task list with dependencies, add durations, and then submit a network diagram (using MS Project) and a project schedule. Develop the Work Breakdown Structure Your WBS should have a minimum of 25–30 tasks and be three subtasks deep. Make sure to use verb-object task names (for example, "Develop software"). Enter tasks in MS Project. Create the predecessor relationships to create a network diagram. DO NOT LINK SUMMARY TASKS! In the Gantt Chart Tools tab, check the box marked Outline Number in the Show/Hide group. Deliverables: In MS Project, print the following: Gantt Chart Entry Table on no more than three pages, including Task Name, Duration, Start, Finish, and Predecessor columns with Gantt Chart Schedule Table on one page, including only the default columns (Task Mode, Task Name, Start, Finish, Late Start, Late Finish, Free Slack, Total Slack); make sure columns are wide enough to read completely. Network Diagram on one page, highlighting Critical Path and circling milestones. Justify why you chose your milestones. (Hint: use milestones from the scope statement or look for key merge or burst activities.) Also print the network diagram across two to three pages for clarity. Using the Resource Sheet (View > Resource Sheet), develop and print a list of resources required for your project, including Max. Units and Costs (Std. Rate, Ovt. Rate, Cost/Use). If working in a group, include a statement of participation, describing how each person contributed to this project deliverable. Please have each person sign the statement. DO NOT ASSIGN RESOURCES AT THIS TIME! Due Week 5: Risk Management Plan Establish the project's priority matrix (constrain, enhance, accept). Identify at least 10 project risks and specify when each will occur in the project life cycle. Assess their impact and probability of occurrence. Create a risk scoring matrix similar to Pinto's (Figure 7.5) and justify your chosen risk scoring approach. Rank risks based on the total risk score. Prepare the Risk Response Matrix for each risk—including details like Response, Contingency, Trigger, and Responsible Person—using the provided template or the process described in Week 3. Deliverables: Use the Risk Management Analysis Template spreadsheet (risk management analysis template.xls) or the methodology from Week 3. If working in a team, include a statement of participation; have each member sign it. Due Week 6: Resource Management Plan A comprehensive project plan is incomplete without resource assignments, including cost estimates and resource leveling to ensure feasible scheduling. Tasks: Assign resources to tasks. Print the resource sheet. Identify over-allocated resources. Print the Gantt chart and entry table, and reports showing resource costs and total project costs. Verify if costs align with the scope statement's budget. Level the project considering slack; if resources remain over-allocated, re-level without slack constraints. Assess impact on project duration and deadline adherence. Explore adding a resource at 1.5x labor cost if necessary, calculating the additional cost and total project cost, and compare to scope budget. Decide if project delay or resource addition is acceptable. Submit supporting MS Project documentation. Deliverables: A project activity journal detailing actions and results; MS Project printouts; a final time and cost report explaining how they meet scope needs; if scope changes occurred, document modifications and revised scope statement, with signatures. Due Week 7: Communication Plan According to PMBOK®, "the Communications Planning process determines the information and communications needs of the stakeholders." Create a communication plan that includes contact info, major deliverables and update methods, stakeholder identification, schedule for updates, and other relevant info using the provided template. Deliverables: Business memo summarizing the communication plan; include contribution statements with signatures if in a team. Due Week 8: Final Project Package The project plan should be fully integrated, professionally written, mistake-free, and include all revisions. It must contain: a Table of Contents, Project Charter, Scope Statement, Work Breakdown Structure, Network Diagram, Risk Management Plan, Resource Management Plan, Communication Management Plan, and the lessons learned document. Also include a project summary memo; final project plan document; lessons learned report, including reflections on project successes, improvements, team dynamics, conflicts, personal growth, and suggestions for future projects. Document each team member’s participation with signatures. The final submission should demonstrate comprehensive planning, clear organization, and professional quality throughout.