PM3000 Unit 4 Assignment 1

User Generated

CnzOraargg

Computer Science

Description

Project Management Plan and Project Schedule

There are two parts to this assignment:

Part 1: Project Management Plan
  • Develop a completed project plan for the business or IT project that you selected in Part 1 of Assignment 2.
  • Use the Project Management Plan Template provided in the Resources.
Part 2: Project Schedule
  • Complete the Project Schedule section of the Project Management Plan Template.
  • Use MS Project 2016, which is available through the Toolwire Virtual Desktop.
  • Develop an MS Project plan for your project schedule. Include an introduction and link into the Project Schedule section of the Project Management Plan.
    • Create a Gantt chart showing:
      • Project tasks, milestones, and other measurable, tangible, and verifiable outcomes or results that must be produced to complete the project.
      • Predecessors to tasks.
      • Resources assigned to each task.
    • Note: You should limit project tasks to 10 business days or less. Shorter task durations make it easier to assess project progress. Provide additional amplifying information about the schedule in your Project Plan, as applicable.

Reminder: Examples of business or IT project types:

  • Examples of business projects include (but are not limited to): planning a company event, planning a traditional wedding, construction, or other projects with a business-oriented focus.
  • Examples of IT projects include (but are not limited to): ERP implementation, Web site development, WAN design, IT security, et cetera.

Additional Requirements

  • Written communication: Ensure written communication is free of errors that detract from the overall message.
  • Documents: Submit the following 2 documents:
    • Completed Project Management Plan (using the Project Management Plan Template).
    • Completed MS Project Plan.
  • List of references: Include a list of references, including books, Web sites, articles, and other resources.
  • Formatting: Resources and citations are formatted according to current APA guidelines for style and formatting.
  • Font and font size: Times New Roman, 12 point.
  • Submission: Be sure to include all parts in your submission.

Unformatted Attachment Preview

[Year] [Type in Project Plan Title] [Type the document subtitle] [Type a brief summary of what the project plan is all about. Example: A Plan that will improve our IT infrastructure.] [Learner Name] Course number [Pick the date] 1 [Type in Project Plan Title] Executive Summary [Overview of Executive Summary E xecutive Summaries are exactly what they imply, a brief description of the project that 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.] Insert Executive Summary narrative here. Course number | Confidential 2 [Type in Project Plan Title] Table of Contents Executive Summary....................................................................................................................................... 1 Version Control ............................................................................................................................................. 5 Project Charter .............................................................................................................................................. 6 Preliminary Scope Statement ....................................................................................................................... 9 Project Scope .............................................................................................................................................. 13 Work Breakdown Structure (WBS) ......................................................................................................... 14 Budget ......................................................................................................................................................... 17 Communications Matrix.............................................................................................................................. 18 Risk Matrix .................................................................................................................................................. 19 Project Schedule ......................................................................................................................................... 21 Project Quality Plan .................................................................................................................................... 22 Introduction ............................................................................................................................................ 22 Plan Quality Management Processes: .................................................................................................... 22 Inputs: ................................................................................................................................................. 22 Tools & Techniques: ............................................................................................................................ 22 Outputs: .............................................................................................................................................. 22 Perform Quality Assurance: .................................................................................................................... 22 Inputs: ................................................................................................................................................. 22 Tools & Techniques: ............................................................................................................................ 22 Outputs: .............................................................................................................................................. 22 Control Quality: ....................................................................................................................................... 22 Inputs: ................................................................................................................................................. 22 Tools & Techniques: ............................................................................................................................ 22 Outputs: .............................................................................................................................................. 22 Project Human Resource Plan..................................................................................................................... 23 Introduction ............................................................................................................................................ 23 Plan Human Resource Management ...................................................................................................... 23 Inputs: ................................................................................................................................................. 23 Course number | Confidential 3 [Type in Project Plan Title] Tools & Techniques: ............................................................................................................................ 23 Outputs: .............................................................................................................................................. 23 Acquire Project Team.............................................................................................................................. 23 Inputs: ................................................................................................................................................. 23 Tools & Techniques: ............................................................................................................................ 23 Outputs: .............................................................................................................................................. 23 Develop Project Team ............................................................................................................................. 23 Inputs: ................................................................................................................................................. 23 Tools & Techniques: ............................................................................................................................ 23 Outputs: .............................................................................................................................................. 24 Manage Project Team ............................................................................................................................. 24 Inputs: ................................................................................................................................................. 24 Tools & Techniques: ............................................................................................................................ 24 Outputs: .............................................................................................................................................. 24 Project Procurement Plan ........................................................................................................................... 24 Introduction ............................................................................................................................................ 24 Plan Procurement Management............................................................................................................. 24 Inputs: ................................................................................................................................................. 24 Tools & Techniques ............................................................................................................................. 24 Outputs: .............................................................................................................................................. 24 Conduct Procurement Management ...................................................................................................... 24 Inputs: ................................................................................................................................................. 24 Tools & Techniques ............................................................................................................................. 24 Outputs: .............................................................................................................................................. 24 Control Procurement Management........................................................................................................ 25 Inputs: ................................................................................................................................................. 25 Tools & Techniques ............................................................................................................................. 25 Outputs: .............................................................................................................................................. 25 Close Procurement Management ........................................................................................................... 25 Inputs: ................................................................................................................................................. 25 Course number | Confidential 4 [Type in Project Plan Title] Tools & Techniques ............................................................................................................................. 25 Outputs: .............................................................................................................................................. 25 References .................................................................................................................................................. 26 Appendices.................................................................................................................................................. 27 Course number | Confidential 5 [Type in Project Plan Title] Version Control Version Number 1.0 Assignment Number Date [OVERVIEW OF VERSION CONTROL: Any change should be documented. For example if I (the instructor) send this document back to you for revisions, the revision should be number 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.] Course number | Confidential 6 [Type in Project Plan Title] Project Charter [OVERVIEW OF PROJECT CHARTER: C harters establish the project within the organization and recognize the project manager as the person in charge of resources (Human Resources, Money, Procurement, etc.) 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.] Course number | Confidential 7 [Type in Project Plan Title] SWOT Analysis (Strengths, Weaknesses, Opportunities, & Threats) [General statement about the critical success factors (CSFs) that will make the project a success] • Strengths: [What things is the organization very good at? Examples: well-trained staff, previous project management experience, leadership in the field.] • Weaknesses [What things is the organization need improvement on? Examples: running over budget, talent skill sets not up to par, little or no project management experience.] • Opportunities [What market forces is the organization taking advantage of? Examples: First to market, new technology, one of a kind.] • Threats [What outside market forces are threats to the organization? Examples: A competitor developing the same product or service, new technology that is a “game changer”, does not comply with government mandates.] Known Project Risks, Constraints, & Assumptions • Risks [What types of Risks are known at the beginning of this project?] • Constraints [What resources (Human, materials, capital) are limited for this project?] • Assumptions [What can we assume to be a standard part of this project?] Roles and Responsibilities: [Description on the how the roles and responsibilities have been divided amongst the project team members.] Name Role Position Contact Information Course number | Confidential 8 [Type in Project Plan Title] [GUIDANCE: Moving Towards Distinguished Performance on the Project Charter 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: • • • • • 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 etc.) Assigning authority to the project manager so she/he may expend organizational assets (human resources, money, equipment, software etc.)] Course number | Confidential 9 [Type in Project Plan Title] Preliminary Scope Statement [OVERVIEW OF TEAM CONTRACT: T eam Contracts define how the team members interact with each other. In other words, these are the rules of engagement for the team. For larger size teams this document may become quite extensive in order to make sure everyone understands meeting etiquette so that the team meetings flow smoothly. Beyond the rules of a meeting it may show delegation of authority to Subject Matter Experts (SME) or group leaders who are responsible for a part of the project. Bear in mind that the project manager is ultimately responsible for the success or failure of a project. This outlines the Project Manager’s expectations of the team members and may also include the Project Sponsor, the client or customer and other stakeholders who may be impacted or have a concern with the project’s deliverables.] Project Name: Project Manager: Team Members. A. Commitments. 1. As a project team we will: 1. B. Team Meeting. The participation ground rules include: 1. The communication ground rules include: 1. The problem-solving ground rules include: 1. The decision-making ground rules include: 1. Course number | Confidential 10 [Type in Project Plan Title] The conflict-handling ground rules include: 1. C. Meeting Guidelines. 1. Meetings will be held every number days/weeks/months. 2. Meetings will be called by Name of Person. 3. Agendas will be issued every number days/weeks in advance by Name of Person. 4. Meetings will be facilitated by Name of Person. 5. Evaluations of meetings will be conducted every number of meetings. 6.Name of Person will issue minutes within number days of the meeting. D. Meeting Procedures. 1. Team Member Signatures: _______________________________________________________ Project Manager: [Enter Your Name Here] _______________________________________________________ [Title: Name] _______________________________________________________ [Title: Name] _______________________________________________________ Course number | Confidential 11 [Type in Project Plan Title] [Title: Name] Course number | Confidential 12 [Type in Project Plan Title] [GUIDANCE: Moving Towards Distinguished Performance on the Team Contract 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: • • • • • • • • • • • • Team Members Names AND Job Title AND Department/Area Code of Conduct (New Section) Collaboration Tools (New Section) Collaboration Skills (New Section) War Room (New Section) o Separate Team Room for Project o Features o Availability Add an overview of the team goals Will there be any offsite meetings? If so, what are the rules? Is there a need for training? o On a new tool? o On new equipment? o Certification? Are there sub groups or smaller teams feeding into the main project? Are there contractors? How do they fit into the team contract? What are the team rules when dealing with outside contacts? o Clients? o Vendors? o Other Organizations? Adding additional information about each section in the document. (Example: Commitments and what that means within the context of the project.)] Course number | Confidential [Type in Project Plan Title] 13 Project Scope [OVERVIEW OF PROJECT SCOPE S cope Statements succinctly define what exactly is going to be achieved in the project. They also define what is NOT going to be done as well. For example, a computer lab at a university may upgrade the operating system of the computers but will not be upgrading the machines. ] Project Overview GUIDANCE: Describe the background and context for the project and why it is being undertaken. Discuss the business value of the work being performed. Project Scope GUIDANCE: This section is where you clearly define the logical boundaries of your project. These statements are used to define what is within the boundaries of the project and what is outside those boundaries. Data, processes, applications, or business areas are items that could be examined. The following might be helpful to include: • • • • • • The types of deliverables that are in scope and out of scope (business requirements, current state assessment). The major life-cycle processes that are in and out of scope (analysis, design, testing). The types of data that are in and out of scope (financial, sales, employee). The data sources (or databases) that are in scope and out of scope (billing, general ledger, and payroll). The organizations that are in scope and out of scope (human resources, manufacturing, vendors). The major functionality that is in scope and out of scope (decision support, data entry, management reporting). The scope of this project includes and excludes the following items: In scope: • • • • Deliverable that will be performed in this project. Deliverable that will be performed in this project. Deliverable that will be performed in this project. Deliverable that will be performed in this project. Examples: Click here to enter text. Out of scope: Course number | Confidential 14 • • • • [Type in Project Plan Title] Deliverable that will NOT be performed in this project. Deliverable that will NOT be performed in this project. Deliverable that will NOT be performed in this project. Deliverable that will NOT be performed in this project. Examples: Click here to enter text. Work Breakdown Structure (WBS) [OVERVIEW OF WORK BREAKDOWN STRUCTURE 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, inserted into this Word document)] The second view is a list view or outline of the WBS. Course number | Confidential 15 [Type in Project Plan Title] Project: Building a Garage 1.0 2.0 3.0 4.0 5.0 Initiate 1.1 Need a Garage? 1.2 Etc. Plan 2.1 What Type of Garage? 2.2 Etc. Execute 3.1 Pour the Foundation 3.2 Etc. Monitor & Control 4.1 Observe the Cement Workers 4.2 Etc. Close 5.1 Inspect Garage 5.2 Etc. 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 MS VISIO, MS Word (Draw Feature), or MS PowerPoint Organization Template. Course number | Confidential 16 [Type in Project Plan Title] [GUIDANCE: Moving Towards Distinguished Performance on the Project Scope 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: • • • • A thorough explanation of o What is in Scope o What is NOT in Scope 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. Project Deliverables also include project documentation (Team Contract, Project Charter, Scope Document, etc.) Course number | Confidential [Type in Project Plan Title] 17 Budget Microsoft Excel Worksheet [OVERVIEW OF PROJECT BUDGET 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 Budget 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 the Budget Items Use Formatting Features in the Tool. Example, highlighting a Line Item that may be Critical to the Budget. Change the Title of the Budget Template Document to Reflect the Name of the Project] Course number | Confidential 18 [Type in Project Plan Title] Communications Matrix [OVERVIEW OF COMMUNICATIONS MATRIX C ommunications Matrix assists the project manager in making sure all information is being distributed to the correct personnel whether it is the project team, sponsor, upper management, customer or stakeholders. Usually this section has a glossary of terms and definitions of TLA’s (Three Letter Acronyms.) so that everyone understands the terminology being used on the project. For example, a NIC stands for Network Interface Card which is a common piece of hardware used on personal computers.] Information Status Report Provider PM Recipient(s) Sponsor Frequency Bi-weekly Medium Email Location SharePoint Glossary [GUIDANCE: Moving towards Distinguished Performance on the Communications Matrix 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: • • • Perform a stakeholder communication analysis Determine best communication medium for project (Media Choice Table) Include an Expectations Management Matrix Course number | Confidential [Type in Project Plan Title] 19 Risk Matrix [OVERVIEW OF RISK MATRIX R isk Matrices are at the core of solving problems before they have an impact on the project scope, cost, schedule, and product quality. Clearly one may categorize risks on what they are going to impact or the type of risk. For example there may be risks because of the personnel on the team (They may need training on a new technology or if one team member is sick, his/her contribution/expertise will be lost.) or there has been problems in the past with a certain vendor and so forth. However another way of looking at it is whether the risks may fit into three different scenarios: • • • Known, knowns (It is known when the risk may occur and what it is.) Unknown, knowns (It is unknown when the risk may occur but it is a known entity.) Unknown, Unknowns (Neither the timing nor the risk is known, a surprise.) There are many ways to categorize and order risks so that the project manager and the team will be on top of the situation and will be able to mitigate or control the risks when they occur. The important part of the Risk Matrix is to make sure that most of the risks are identified and that there are defined actions to deal with them.] Risk Probability (L,M,H) Severity (L,M,H) Mitigation Approach Team skill sets not up to par M H Train team members on new technology Course number | Confidential 20 [Type in Project Plan Title] [GUIDANCE: Moving towards Distinguished Performance on the Risk Matrix 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: • • • • • • • • • • General Overview of the Risk Matrix Table and the Main Purpose for the Project. New Column – Category (Personnel, Budget, Equipment, Software, Logistics, Time, Technical, PMbok ® Knowledge Areas, etc.) Color Code (Show Intensity of Risk: Yellow = Low, Orange = Medium, Red=High) o Have a Key stating what the colors mean Color Code (Show Status of Risk: Green = O.K., Yellow = Look At, Red = In Trouble) New Column – Risk Owner (Who has to watch out for what and report the risk occurring.) Add general information outside of the risk matrix table such as who to contact in case of a severe risk occurring. What is the chain of command? New Column – Rank the risk New Column – Number the risk New Column – Description of Loss (or Gain) from the risk occurring Categorize Risks that will need attention and those on a “watch list”] Course number | Confidential 21 [Type in Project Plan Title] Project Schedule [OVERVIEW OF PROJECT SCHEDULE S chedules are used throughout the project. Usually a project manager is told how much time is available to complete a project. Many times a project manager has to make the project “fit” into the time allotted. However, when a detailed schedule is created the project manager may have to go back to the sponsor to discuss a more realistic schedule to achieve the product of the project. A detailed schedule is not put in place until the Scope Statement and Work Breakdown Structure (WBS) is discussed and created by the project team. The schedule emanates from the Scope Statement and Work Breakdown Structure. Part of the reason for introducing students to Microsoft Project software is to enable them to use this tool to effectively create a project schedule for their assignment. Do not be afraid to use features introduced in the MS Project Labs such as hyperlinks to relevant websites or using notes or comments to clarify the milestones or tasks. Embedded below is a blank Microsoft Project document:] Microsoft Project Document [GUIDANCE: Moving towards Distinguished Performance on the Project Schedule 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: • • • • • • • • • Separate Word Document explaining and clarifying the schedule. If the Task is Greater than 8-10 Working Days, it May Need to Be Broken Down Into Smaller Tasks Schedule Shows Predecessors to Tasks. Use of the Note Feature in MS Project. Use of the Comment Feature in MS Project. Use of the Hyperlink Feature in MS Project. Add Resources to the Tasks. Customize the Look of the Gantt chart. Create a Callout on a Specific Task that will need Attention.] Course number | Confidential 22 [Type in Project Plan Title] Project Quality Plan [OVERVIEW OF PROJECT QUALITY PLAN Project quality management are the process and activities used in managing a project to ensure the product, services and results meet or exceed quality standards. Project quality management includes activities to review and ensure that project requirements are met. Project Quality Management has three main sections including Plan Quality Management, Perform Quality Assurance and Control Quality. Please review the PMBOK, Chapter 8, for additional inputs, tools & techniques and outputs] Introduction Plan Quality Management Processes: Inputs: Tools & Techniques: Outputs: Perform Quality Assurance: Inputs: Tools & Techniques: Outputs: Control Quality: Inputs: Tools & Techniques: Outputs: Course number | Confidential 23 [Type in Project Plan Title] Project Human Resource Plan [OVERVIEW: The Project Human Resource plan includes processes that organize, manage and lead the project team. This plan includes documentation pertaining to organizational structure, skill identification, resource selection and availability, team building activities, collaboration and participation activities and performance management]. Introduction Plan Human Resource Management Inputs: Tools & Techniques: Outputs: Acquire Project Team Inputs: Tools & Techniques: Outputs: Develop Project Team Inputs: Tools & Techniques: Course number | Confidential 24 [Type in Project Plan Title] Outputs: Manage Project Team Inputs: Tools & Techniques: Outputs: Project Procurement Plan [OVERVIEW: This plan includes the activities for purchasing products, services or results from outside the company. The Project Procurement plan includes contract management processes.] Introduction Plan Procurement Management Inputs: Tools & Techniques Outputs: Conduct Procurement Management Inputs: Tools & Techniques Outputs: Course number | Confidential 25 [Type in Project Plan Title] Control Procurement Management Inputs: Tools & Techniques Outputs: Close Procurement Management Inputs: Tools & Techniques Outputs: Course number | Confidential 26 [Type in Project Plan Title] References Course number | Confidential 27 [Type in Project Plan Title] Appendices Course number | Confidential
Purchase answer to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

�...


Anonymous
Excellent resource! Really helped me get the gist of things.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4

Similar Content

Related Tags