Project Plan Instructions Project managers work with project management plans tailored to each specific project. We will be using aProject Plan Template(linked in the Resources) to complete project...

1 answer below »

Project Plan


Instructions


Project managers work with project management plans tailored to each specific project. We will be using aProject Plan Template(linked in the Resources) to complete project management tasks throughout this course for the project you chose in Unit 1.


Using theProject Plan Template, add the elements you created in the first assignment for your presentation:



  1. Project Charter.

  2. Project Scope.

  3. Work Breakdown Structure (WBS).


This week, work though the Authess Practice activity in this unit to learn how to create risk and communications matrices. Then create those elements for your selected project, and add them to yourProject Plan Template:



  1. Risk Matrix.

  2. Communications Matrix.


Additional Requirements



  • Written communication:Ensure written communication is free of errors that detract from the overall message.

  • Length:Use theProject Plan Template.

  • Font and font size:Use Times New Roman, 12-point font.

  • Submission:Submit yourProject Plan Templatewith the sections identified above completed.




[Type in Project Plan Title] 13 [Type in Project Plan Title] Executive SummaryComment by me: Delete this Overview and comment BEFORE submitting the project management template. [Overview of Executive Summary E xecutive Summaries are exactly what they imply, a brief description of the project a busy executive may read to understand the purpose, main points, and deliverables of a project. They are tailored so upper management understands how the project fits into the mission and goals of the organization. Unlike the aforementioned templates in this document, the Executive Summary is known for its brevity. However, the importance of this template is to be able to recognize and report the most important things the executives need to know so there are no “surprises” during the project run. [NOTE: THIS WILL BE THE LAST THING YOU WILL FINISH IN THIS DOCUMENT, BUT IT USUALLY APPEARS AT THE BEGINNING OF THE PROJECT PLAN.] Table of ContentsComment by me: This document uses the MS Word Table of Contents (TOC) feature. Use the MS Word help menu to find out more if you’ve never used this feature. DELETE this comment before submitting this template. Executive Summary1 Version Control3 Project Charter4 Stakeholder Register5 Work Breakdown Structure (WBS)7 Budget9 Communications Matrix10 Risk Matrix11 Project Schedule13 References14 Appendices15 Version ControlComment by me: First Assignment Number should be associated with 1.0 Version Number and the submission date will be the date. Example: Version Number 2.0 will be associated with the second revision. (Right Click on this Comment and Delete it before submitting.) Version Number Assignment Number Date 1.0 [OVERVIEW OF VERSION CONTROL: Document any changes here. For example if I (the instructor) send this document back to you for revisions, the revision should be numbered and dated. So, if I send it back to a learner after the learner submits this template the first time, it should have a second row of 1.1, u01a1, date of submission.] Project Charter [OVERVIEW OF PROJECT CHARTER:Comment by me: Delete this overview section and comment BEFORE submitting this template. C harters establish the project within the organization and recognize the project manager as the person in charge of resources (Human Resources, Money, Procurement, et cetera) and the ability to utilize those resources. It defines what is known at the beginning of the project such as the Title, Timeframe, Starting Budget, Project Manager, Approach, and roles and responsibilities of the team members. Many projects experience “progressive elaboration,” or in other words, more is known about the project as it moves along.] Project Title: [Enter the Project Plan Title here.] Project Start Date: Click here to enter a date. Project Finish Date: Click here to enter a date. Budget: [This is an overall amount that was set at the beginning of the project. However, any known specifics should be put in as well.] Project Manager: [Your name] Project Objectives: [Put in what are the deliverables to the project. This may include the end product or service. There may be training of employees involved or other follow-ups at the end of the project. The documents and documentation of the project are deliverables as well.] Approach: [A description on HOW the Project Objectives (from above) will be accomplished.] [Individual items and how they are to be implemented.] · [Individual items and how they are to be implemented.] [Individual items and how they are to be implemented.] [Individual items and how they are to be implemented.] [Individual items and how they are to be implemented.] Stakeholder Register Stakeholder Identification NameComment by me: Add more names and roles as needed. Delete this comment BEFORE submitting the template. Role Position Contact Information Stakeholder Assessment RequirementsComment by me: Add Stakeholder Assessment details as needed. Delete this comment BEFORE submitting the template. Communication Needs Frequency of Communication Expectations Influence on the Project Interest and Power Stakeholder ClassificationComment by Randy E. Adkins: Here, you will classify the stakeholders based on various criteria.You may divide them based on their power and interest on the project, that is, whether it is high, medium, or low.You can also assign other attributes to stakeholders, such as whether a stakeholder is internal, external, positive, a supporter, a resistor, or a neutral stakeholder, et cetera. [GUIDANCE: Moving Towards Distinguished Performance on the Project CharterComment by me: Delete this guidance and comment BEFORE submitting the template. Add this additional information in the appropriate places in the body of the section above. Here are some additional things you may add to the template to customize it or elaborate on information that is known about the project: · Project Overview (General background of the project). · Key Milestones (Examples: Key deliverables such as the design of a website or the coding behind the website). · Describes a changing marketplace that justifies the project. (If we don’t do it, our competition will!). · Expansion on the roles and responsibilities of team members. (Name, role, responsibilities, delegation of authority et cetera). · Assigning authority to the project manager so they may expend organizational assets (human resources, money, equipment, software, et cetera).] Work Breakdown Structure (WBS) [OVERVIEW OF WORK BREAKDOWN STRUCTUREComment by me: Delete OVERVIEW and comment BEFORE submitting template. A Work Breakdown Structure (WBS) is included in the Scope Statement Documentation. Usually, there are TWO views. The first view is a hierarchical one that is usually worked upon by the project manager and team to discover exactly what tasks need to be done and in what order. (You will have to show more detail or levels than these examples.) WBS Hierarchy Example (Created in Microsoft Visio, saved as a .jpeg picture, and inserted into this Word document)] The second view is a list view or outline of the WBS. Project: Building a Garage 1.0 Initiate 1.1 Need a Garage? 1.2 Et cetera. 2.0 Plan 2.1 What Type of Garage? 2.2 Et cetera. 3.0 Execute 3.1 Pour the Foundation. 3.2 Et cetera. 4.0 Monitor & Control 4.1 Observe the Cement Workers. 4.2 Et cetera. 5.0 Close 5.1 Inspect Garage. 5.2 Et cetera. Note that the hierarchy view and the list view have the same tasks and are numbered the same. The graphic view may be achieved by using Microsoft Visio, Word (Draw Feature), or PowerPoint Organization Template. [GUIDANCE: Moving Towards Distinguished Performance on the Project ScopeComment by me: Delete this GUIDANCE and comment BEFORE submitting this template. Add this additional information in the appropriate places in the body of the section above. Here are some additional things that may be added to the template to customize it or elaborate on information that is known about the project: · Adding color to the WBS to further clarify a phase or layer. · Making sure the numbers match the tasks between the Hierarchy WBS and the List WBS. · Including documentation in the Project Deliverables, such as Team Contract, Project Charter, Scope Document, et cetera.] Budget [OVERVIEW OF PROJECT BUDGETComment by me: Delete OVERVIEW and this comment BEFORE submitting the template. B udgets need to be complete and detailed enough so there is no question on how the money is being spent. Organizations are different on what they include on their project budgets because many of the human resources are already on the payroll being paid for operational work. However, some organizations want a full accounting of the project and will include the costs of the personnel even though they are already on the payroll. It is expected that you will include personnel in this assignment budget or offer an explanation on why these monies are not tracked. ] [GUIDANCE: Moving towards distinguished performance on the Project BudgetComment by me: Delete OVERVIEW and this comment BEFORE submitting the template. Please add this additional information in the appropriate places in the body of the section above. Here are some additional things that may be added to the template to customize it or elaborate on information that is known about the project: · Business Segment Justification – Add Column. · Notes – Clarify the Line Items – Add Column. · Insert a Graph Showing Allocation of Funds. · Author Comments – Add Column. · Use Excel Note Feature to Clarify Line Items. · Tie Into WBS Task Items for Estimation. · By Process (Initiate, Plan, Execute, Monitor/Control, Close). · Embed Excel Spreadsheet in Word Document to Expand Upon the Explanation of
Answered Same DayOct 20, 2021

Answer To: Project Plan Instructions Project managers work with project management plans tailored to each...

Amar answered on Oct 27 2021
148 Votes
Project Destination Wedding
    13
    Project Destination Wedding
Executive Summary
This report presents a detailed planning of the key processes with respect to the proposed project for planning, designing, developing, implementing and delivering destination wedding experience. This project plan presents project charter, stakeholder register, WBS, budget planning, communications planning, risk matrix, and project schedule. The project objectives include the designing and planning a destination wedding experience for Paul and Simon, developing and underta
king the various activities entailing invitations, logistics and all other aspects to ensure wedding experience in the manner expected and agreed upon, and implementing and delivering the wedding experience the day of wedding in a successful and expected manner. The project management shall employ five phased approach spanning initiation, planning, execution, monitoring / controls, and closure by using the PMBoK framework in terms of process planning, application of required tools and approaches, and overall project management / delivery mechanisms

Table of Contents
Executive Summary    1
Version Control    3
Project Charter    4
Stakeholder Register    5
Work Breakdown Structure (WBS)    7
Budget    9
Communications Matrix    10
Risk Matrix    11
Project Schedule    13
References    16
Appendices    17
Version Control
    Version Number
    Assignment Number
    Date
    1.0
     2
    25th October 2020
Project Charter
Project Title: Project Destination Wedding
Project Start Date: 6/1/2020 Project Finish Date: 9/30/2020
Budget:
$25,000
Project Manager: Tyler Powell
Project Objectives: [1] Designing and planning a destination wedding experience for Paul and Simon, [2] Developing and undertaking the various activities entailing invitations, logistics and all other aspects to ensure wedding experience in the manner expected and agreed upon, and [3] Implementing and delivering the wedding experience the day of wedding in a successful and expected manner
Approach:
The project management shall employ five phased approach spanning initiation, planning, execution, monitoring / controls, and closure by using the PMBoK framework in terms of process planning, application of required tools and approaches, and overall project management / delivery mechanisms (Papke-Shields & Boyer-Wright, 2017; Padalkar & Gopinath, 2016; Martens & Carvalho, 2017).
Objective #1: Designing and planning a destination wedding experience for Paul and Simon
Approach: Develop Project Plan that will document process, approach and method of achieving the project using project plan, schedule, budget, risk planning, communication planning, resource allocation and other planning (Papke-Shields & Boyer-Wright, 2017; Padalkar & Gopinath, 2016; Martens & Carvalho, 2017).
Objective #2: Developing and undertaking the various activities entailing invitations, logistics and all other aspects to ensure wedding experience in the manner expected and agreed upon
Approach: Using monitoring and control processes developed in Project Plan, and employing past experiences to undertake the activities / tasks planned (Papke-Shields & Boyer-Wright, 2017; Padalkar & Gopinath, 2016; Martens & Carvalho, 2017).
Objective #3: Implementing and delivering the wedding experience the day of wedding in a successful and expected manner
Approach: Using monitoring and control processes developed in Project Plan, and employing past experiences to implement and deliver the wedding experience the day of wedding in a successful and expected manner (Papke-Shields & Boyer-Wright, 2017; Padalkar & Gopinath, 2016; Martens & Carvalho, 2017).
Stakeholder Register
Stakeholder Identification
    Name
    Role
    Position
    Contact Information
    Paul & Simon
    Project Sponsor / Client
    Individuals
    paulandsimon@wedding .com
    Tyler Powell
    Project Manager
    Freelance Wedding Event Organizer
    [email protected]
    A
    Team Member
    Executive
    [email protected]
    B
    Team Member
    Executive
    [email protected]
    
    
    
    
Stakeholder Assessment
    Role
    Requirements
    Communication Needs
    Frequency of Communication
    Expectations
    Influence on the Project
    Interest and Power
    Project Sponsor / Client
    Successful Wedding
    Progress Updates & Significant Variances
    Weekly
    On-time, within cost and high-quality delivery
    HIGH
    HIGH
    Project Manager
    Project Planning & Implementation
    NA
    NA
    Successful project delivery
    HIGH
    HIGH
    Team Member
    Support project implementation
    NA
    NA
    Successful project delivery
    Low
    Low
    Team Member
    Support project implementation
    NA
    NA
    Successful project delivery
    Low
    Low
    
    
    
    
    
    
    
Stakeholder Classification
Work Breakdown Structure (WBS)
     
    Work Breakdown Structure (WBS)
    1
    Planning
    → 1a.
    Agree on Budget
    → 1b.
    Wedding Date Finalisation
    → 1c.
    Make Guest List
    2
    Guest List
    → 2a.
    Select wedding Card design
    → 2b.
    Send Out Invitation
    → 2c.
    Arrange for guest's commute
    3
    Destination Planning - Church Bookings
    → 3a.
    Book the church
    → 3b.
    Book the priest
    4
    Destination Planning - Reception Venue Bookings
    → 4a.
    Shortlist the Property
    → 4b.
    Select the Wedding destination
    → 4c.
    Plan and finalise guest room allocation
    → 4d.
    Book the available property
    → 4e.
    Finalise reception venue decorations and seating arrangements
    5
    Catering
    6
    Attires & Ring
    → 6a.
    Select wedding dress for bride and groom
    → 6b.
    Order wedding dress
    → 6c.
    Measurements and Fittings
    → 6d.
    Dress trials
    →...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here