Assignment Instructions:Using the Human Resources Plan template located in the P

Assignment Instructions:Using the Human Resources Plan template located in the Project Management Documents.zip file complete aplan for the project use chose in Unit 2.• Complete a Responsibility Assignment Matrix as described in your readings.• Create a staffing plan that addresses the following:o Names or job titles of assigned personnel.o Number of man-hour per time unit (day, week, month) or work package.o Create an organizational chart of your conceptual project that graphically displays reportingrelationships.• Finish the detail of your plan with the following:o Risk assessment if unable to staff project as desired.o Roles and responsibilities of each job position.o Training requirements, if staff does not have the required skill sets.o Your staff acquisition actions to staff internally first or to outsource based on availability ofrequired skill sets.• Create a Project Team Directory with Name, Title, and Contact NumberHUMAN RESOURCE PLAN<PROJECT NAME>TABLE OF CONTENTSINTRODUCTION…………………………………………………………………………………………………………………..2ROLES AND RESPONSIBILITIES………………………………………………………………………………………………2PROJECT ORGANIZATIONAL CHARTS………………………………………………………………………………………3STAFFING MANAGEMENT…………………………………………………………………………………………………….41INTRODUCTIONThis section explains the purpose and importance of having a human resources managementplan. It should provide a general description of what the plan includes and explain how theproject manager and project team can use the plan to help them manage the project effectively.ROLES AND RESPONSIBILITIESRoles and responsibilities of team members and stakeholders must be clearly defined in anyproject. Depending on the organizational structure, project team members may represent manydifferent groups/departments and act in the interest of different functional managers.Additionally, team members may have varying degrees of authority and responsibility. Whenlisting roles and responsibilities the following should be included:Role description of the portion of the project for which the member is accountableAuthority the level at which the member may make decisions, apply project resources,or make approvalsResponsibility the work a team member must perform to complete assigned workactivitiesCompetency the skill(s) required to complete assigned project activitiesProject Manager (PM), (1 position): responsible for the overall success of the SoftwareUpgrade Project. The PM must authorize and approve all project expenditures. The PM is alsoresponsible for approving that work activities meet established acceptability criteria and fallwithin acceptable variances. The PM will be responsible for reporting project status inaccordance with the communications management plan. The PM will evaluate the performanceof all project team members and communicate their performance to functional managers. ThePM is also responsible for acquiring human resources for the project through coordination withfunctional managers. The PM must possess the following skills: leadership/management,budgeting, scheduling, and effective communication.PROJECT ORGANIZATIONAL CHARTSThis section provides a graphic display of the project tasks and team members. The purpose ofthis is to illustrate the responsibilities of team members as they relate to the project tasks. Toolssuch as responsible, accountable, consult, inform (RACI) or responsibility assignment matrix(RAM) may be used to aid in communicating roles and responsibilities for the project team.Additionally, organizational or resource breakdown structures may be used to show howresponsibilities are assigned by department or by type of resource respectively. It should benoted that the level of detail may vary depending on project complexity.2The following RACI chart shows the relationship between project tasks and team members. Anyproposed changes to project responsibilities must be reviewed and approved by the projectmanager. Changes will be proposed in accordance with the projects change control process. Aschanges are made all project documents will be updated and redistributed accordingly.RequirementsGatheringCoding DesignCoding InputSoftwareTestingNetworkPreparationImplementationConductTrainingProjectManagerADesignEngineersRImplementationManagerRAAARRRAAATrainingLeadsCFunctionalManagersCDepartmentManagersICCICIICRIICRCCCCCRKey:R Responsible for completing the workA Accountable for ensuring task completion/sign offC Consulted before any decisions are madeI Informed of when an action/decision has been madeSTAFFING MANAGEMENTThis section contains information on several areas including: when and how human resourcerequirements will be acquired, the timeline for when resources are needed and may be released,training for any resources with identified gaps in skills required, how performance reviews willbe performed, and the rewards and recognition system to be used. It is important to note thatdepending on the scope of the project there may be other items included in staffing management(government and/or regulatory compliance, organizational health and safety, etc).3Software Project Upgrade Resource Histogram9080Work Hours per Week7060Design Engineers (2 employees)50Implementation Manager (1 employee)40Training Lead (1 employee)3020100Week 1Week 2Week 3Week 4TimelineTraining:Performance Reviews:Recognition and Rewards:4Week 5SPONSOR ACCEPTANCEApproved by the Project Sponsor:___________________________________________<Project Sponsor><Project Sponsor Title>5Date:____________________Running Head: WBS OF CMS WEBSITEWORK BREAKDOWN STRUCTUREOFCUSTOMER MANAGEMENT SYSTEM WEBSITEJENNIFER BLACKMONKAPLAN UNIVERSITYPROFESSOR: STEVEN LONGIT-301APRIL 7, 2015INTRODUCTIONThis WBS will give a complete view of the entire required task that will be part of this customermanagement system website project. It will represent all the work that should be completed inorder to complete the project and to launch it for the customers.OUTLINE VIEWHere is the completed outline for the project 1. Customer Management System Website1.1 Initiation1.1.1 Evaluation & Recommendations1.1.2 Develop Project Charter1.1.3 Deliverable: Submit Project Charter1.1.4 Project Sponsor Reviews Project Charter1.1.5 Project Charter Signed/Approved1.2 Planning1.2.1 Create Preliminary Scope Statement1.2.2 Determine Project Team1.2.3 Project Team Kickoff Meeting1.2.4 Develop Project Plan1.2.5 Submit Project Plan1.2.6 Milestone: Project Plan Approval1.3 Execution1.3.1 Project Kickoff Meeting1.3.2 Verify & Validate User Requirements1.3.3 Design System1.3.4 Procure Hardware/Software1.3.5 Install Development System1.3.6 Testing Phase1.3.7 Install Live System1.3.8 User Training1.3.9 Go Live1.4 Control1.4.1 Project Management1.4.2 Project Status Meetings1.4.3 Risk Management1.4.4 Update Project Management Plan1.5 Closeout1.5.1 Audit Procurement1.5.2 Document Lessons Learned1.5.3 Update Files/Records1.5.4 Gain Formal Acceptance1TABULAR VIEWLevel 11 CustomerManagementSystemWebsiteLevel 21.1 InitiationLevel 31.1.1 Evaluation & Recommendations1.1.2 Develop Project Charter1.1.3 Deliverable: Submit Project Charter1.1.4 Project Sponsor Reviews Project Charter1.1.5 Project Charter Signed/Approved1.2 Planning1.2.1 Create Preliminary Scope Statement1.2.2 Determine Project Team1.2.3 Project Team Kickoff Meeting1.2.4 Develop Project Plan1.2.5 Submit Project Plan1.2.6 Milestone: Project Plan Approval1.3 Execution1.3.1 Project Kickoff Meeting1.3.2 Verify & Validate User Requirements1.3.3 Design System1.3.4 Procure Hardware/Software1.3.5 Install Development System1.3.6 Testing Phase1.3.7 Install Live System1.3.8 User Training1.3.9 Go Live1.4 Control1.4.1 Project Management1.4.2 Project Status Meetings1.4.3 Risk Management1.4.4 Update Project Management Plan1.5 Closeout1.5.1 Audit Procurement1.5.2 Document Lessons Learned1.5.3 Update Files/Records1.5.4 Gain Formal AcceptanceHIERARCHICAL STRUCTURE2Level1233333233333323333333332333323333WBS Code11.11.1.11.1.21.1.31.1.41.1.51.21.2.11.2.21.2.31.2.41.2.51.2.61.31.3.11.3.21.3.31.3.41.3.51.3.61.3.71.3.81.3.91.41.4.11.4.21.4.31.4.41.51.5.11.5.21.5.31.5.4Element NameCustomer Management System WebsiteInitiationEvaluation & RecommendationsDevelop Project CharterDeliverable: Submit Project CharterProject Sponsor Reviews Project CharterProject Charter Signed/ApprovedPlanningCreate Preliminary Scope StatementDetermine Project TeamProject Team Kickoff MeetingDevelop Project PlanSubmit Project PlanMilestone: Project Plan ApprovalExecutionProject Kickoff MeetingVerify & Validate User RequirementsDesign SystemProcure Hardware/SoftwareInstall Development SystemTesting PhaseInstall Live SystemUser TrainingGo LiveControlProject ManagementProject Status MeetingsRisk ManagementUpdate Project Management PlanCloseoutAudit ProcurementDocument Lessons LearnedUpdate Files/RecordsGain Formal Acceptance3WBS DICTIONARYFor each work element there is a definition is available in this section .This definition gives abrief idea to the reader that what is the actual task and what it contains. Here is the completedefinition for all the elements for this website development project Level1WBSCode1231.11.1.1Customer Management SystemWebsiteInitiationEvaluation & Recommendations31.1.2Develop Project Charter31.1.331.1.431.1.5Deliverable: Submit ProjectCharterProject Sponsor Reviews ProjectCharterProject Charter Signed/Approved21.231.2.13Element NameDefinitionAll work to implement a new customermanagement system website.The work to initiate the project.Working group to evaluate solution setsand make recommendations.Project Manager to develop the ProjectCharter.Project Charter is delivered to theProject Sponsor.Project sponsor reviews the ProjectCharter.The Project Sponsor signs the ProjectCharter which authorizes the ProjectManager to move to the PlanningProcess.The work for the planning process forthe project.Project Manager creates a PreliminaryScope Statement.The Project Manager determines theproject team and requests the resources.The planning process is officiallystarted with a project kickoff meetingwhich includes the Project Manager,Project Team and Project Sponsor(optional).Under the direction of the ProjectManager the team develops the projectplan.Project Manager submits the projectplan for approval.The project plan is approved and theProject Manager has permission toproceed to execute the project accordingto the project plan.Work involved executing the project.PlanningCreate Preliminary ScopeStatement1.2.2Determine Project Team31.2.331.2.4Project Team Kickoff MeetingDevelop Project Plan31.2.5Submit Project Plan321.2.61.3Milestone: Project Plan ApprovalExecution4Level3WBSCode1.3.131.3.231.3.331.3.431.3.531.3.631.3.731.3.8321.3.91.431.4.1331.4.21.4.331.4.4231.51.5.1Element NameDefinitionProject Manager conducts a formal kickoff meeting with the project team,project stakeholders and projectProject Kickoff Meetingsponsor.The original user requirements isreviewed by the project manager andteam, and then validated with theVerify & Validate Userusers/stakeholders. This is whereRequirementsadditional clarification may be needed.The technical resources design the newDesign Systemwidget management system.The procurement of all hardware,software and facility needs for theProcure Hardware/Softwareproject.Team installs a development system fortesting and customizations of userInstall Development Systeminterfaces.The system is tested with a select set ofTesting Phaseusers.The actual system is installed andInstall Live Systemconfigured.All users are provided with a four hourstraining class. Additionally, managersare provided with an additional twoUser Traininghours class to cover advanced reporting.Go LiveSystem goes live with all users.The work involved for the controlControlprocess of the project.Overall project management for theProject Managementproject.Project Status MeetingsWeekly team status meetings.Risk management efforts as defined inRisk Managementthe Risk Management Plan.Project Manager updates the ProjectManagement Plan as the projectUpdate Project Management Plan progresses.CloseoutThe work to close-out the project.An audit of all hardware and softwareprocured for the project ensures that allprocured products are accounted for andAudit Procurementin the asset management system.5Level3WBSCode1.5.231.5.33Element NameDefinition1.5.4Project Manager along with the projectteam performs a lessons learnedmeeting and documents the lessonslearned for the project.All files and records are updated toreflect the widget management system.The Project Sponsor formally acceptsthe project by signing the acceptancedocument included in the project plan.Document Lessons LearnedUpdate Files/RecordsGain Formal AcceptanceGLOSSARY OF TERMSLevel of Effort:Level of Effort (LOE) shows how much work or tasks are needed tocomplete the project.WBS Code:A unique identifier assigned to each element in a WBS.Work Package:It is a deliverable at the lowest level of its WBS branch.WBS Component: A component of a WBS which is located at any level. It can be a WorkPackage or a WBS Element as there’s no restriction on what a WBSComponent is.WBS Element:A WBS Element is a single WBS component and its associated attributeslocated anywhere within a WBS.6ReferencesProject Management Institute (2008) A Guide to the Project Management Body of Knowledge(PMBOK Guide). Retrieved from http://collection.safaribooksonline.com/7