Performance compensation and rewards presentation

Performance, Compensation, And Rewards Presentation

Hello

This week I am in need of assistance with this assignment. As you can see below it needs to be DETAILED DETAIL DETAILED. I have provided an example of a previous assignment and my last week's paper.

If you have any questions please let me know. Thanks again!

Create a 7- to 9-slide presentation using the scenario from your Week 2 Individual assignment (this is total slides for everything in the submission do not go over 9 total slides!!!!...Let me Repeat that, there should be no more than 9 Slides submitted)

· Intro and summary slide are required....note the intro slide is not your title slide. The Intro slide tells me what the presentation will contain/the outline.

· Discuss three measurements you would use to measure performance for the project. NOTE: These are performance measures to be used as measurements during the project...not after the project has been delivered. There is no "book" answer for these, it is what you come up with as to how you would measure performance on your project. Recommend you have a slide for each of the measurements so you can show enough details on the items.

· Determine appropriate financial compensation/rewards for the project team AND explain your rationale for selecting the financial compensation and rewards. As a hint, do not just tell me you would give a raise...that is not detailed enough....how much? Why was that selected over other options? Etc.

· Outline a human resource plan for the project in the scenario. Do not just show me a diagram of an HR Plan on the internet, this needs to be specific to your project and explained.

· Include typed (not audio) speaker notes on each slide....speakers notes are also not a "note bubble"...use the MS Powerpoint speaker notes.

· The presentation includes relevant media/visuals/pictures/etc that are consistent with the content. In other words, do not just have words on the slides....make it look good.

Also when you put words on slides use bullets; do not use sentences/paragraphs on a slide. Also even though you are using Notes Pages you have to have some content on the slides....for example, in the past, some students give me a slide with just the header "HR Plan" and a picture of an HR office....that is not a good slide since it does not show the audience any information....yes you will have detailed information when you speak to the slide but you have to show something of value on the slide itself.

I can't emphasize enough here...the information must be detailed and specific to the project that you selected

Running Head: PROJECT ACTIVITIES AND SEQUENCES

Project Activities and Sequences Scenario Paper

Qiana Reynolds

University of Phoenix

Project Management/CPMGT-301

December 7, 2020

Instructor: Gary Denney

Project Activities and Sequencing Scenario
Work Breakdown Structure and a project schedule are crucial to have a successful outcome for the Acme Shipping and Warehouse company. The Work Breakdown Structure is fundamental because it breaks each task and milestone into more refined, more detailed information that gives a project manager and their team the proper knowledge to continue carrying out their project. Acme Shipping and Warehouse is a company that has outdated software that needs to be updated. This includes the software within the tracking, shipping, and receiving database. Within this paper, we will identify the project's scope, define the needs of the stakeholder, create the Work Breakdown Structure schedule, and list the tools and milestones necessary to complete the project.

Project Scope

Within the operation area, Acme Shipping and Warehouse's focus is to install the new software updates for the company called Roadrunner software. This software ensures tracking, receiving, shipping, and even inventory is being tracked correctly. The computers will be down for about 5.5 hours, and there will be five employees who will be trained in updating the software on the computers. To generate a faster working system on time, the project needs to extend the shipping company's original business hours from 7 am to 7 pm Monday through Saturday and add 11 am to 7 pm on Sundays. In this case, only the trained employees will have the chance to undertake the Roadrunner software and administer the updates company-wide.

Project Stakeholders

The first stakeholder is Acme Shipping and Warehouse company Operations Managers, who are directly affected by the project's success or failure. Next are the customers who acquire products and services, which will cause computer downtime. As presented by SEBoK authors, there is a need from the stakeholders for requirements that will be represented in terms of the individual's view within the business enterprises level of operations (SEBoK authors.2015). The last stakeholder is the project team, who will directly collect the data, oversee the project's execution, and opinions from all involved in its comprehensive software update.

Work Breakdown Structure

Work Breakdown Structure

Setup

Prep

Install

Test

Train additional employee

Confirm computers are in

Allow time for delays.

Greater efficiency?

good working condition

Extend store hours

Software updates

Confirm contract with

All components in

on hand

software company

Working order?

Schedule employees

Make working space at

Install software

Meets project goals?

central loading station

Find funding for Sunday pay.

Specify operating

Meets stakeholders

requirements

Expectations?

Necessary Tools

According to Levin, PMP, PgMP, and Wyzalek, PfMP (2015), launching the strategic plan involves using the organization's many departments and resources in the form of projects" (Chapter 3). First, you need a contract from the vendors who supply the Roadrunner software. You also need to get the approval from the department manager of the trained employees to be willing to release them from their regular duties and spend additional hours administering the updates.

The techniques involved in the issue of the aspects affected are inclusive of the methodology associated with the development of a work breakdown structure. There are two simple stages within the phase to make for the elements of the following topics.

The tools that are available include the example of the instrument which are used for the actualization of the needed process, in this case, include the likes of

1. WBS template

2. Tree diagrams

3. Table

4. Microsoft project

Project Milestones

The milestones of a project are like significant trail markers you insert in your project schedule. Milestones are different than tasks that are scheduled to be accomplished. In this project, there are five milestones. "Each of those five deliverables—initiation, planning, execution, control, and closeout—branch of the main deliverable" ("The Ultimate Guide To... Work Breakdown Structure", 2020). The first milestone is the project conception and initiation, which included the project charter created and developed. During this milestone, the project goals and initial plan are brought together. Next is the planning of the project, for example, the software purchase. This milestone is also created and developed within the platform of operation. Under this segment is needed to develop a training schedule to charter for the affected issues, which is the software update.

Third, we have the project launch of the computer software update. During this time, the computers are prepped and confirmed that they have the requirements needed for the update, the software is in hand, and the workspace is ready. Fourth, the project is well commenced, and the software is being installed. Lastly is the project closeout, which involves testing all computers to make sure it's working correctly.

Project Tasks/Subtask Diagram

Programs

Roadrunner software update

01-00-00

Projects 1

Software

01-01-00

Task

Purchase

01-01-01

Task

Software update evaluation

01-01-02

Project 2

Training

01-02-00

Task

Training timetable

01-02-01

Task

Training documentation

01-02-02

Projects 3

Communication

01-03-00

Task

Communication plan

01-03-01

Task

Communication templates

01-03-02

Project 4

Computer software update

01-04-00

Task

Backup critical files

01-04-01

Task

Update computer software

01-04-02

Task

Verify software update

01-04-03

Task

Remedies and solutions

01-04-03

References

The Ultimate Guide to... Work Breakdown Structure (2020). https://www.projectmanager.com/work-breakdown-structure

Levin, PMP, PgMP, Dr. G., & Wyzalek, PfMP, J. (2015). Portfolio Management, a Strategic Approach. https://portal.phoenix.edu/library.html.

SEBoK authors. (2015). Stakeholder Needs and Requirements. Retrieved from http://sebokwiki.org/w/index.php?title=Stakeholder_Needs_and_Requirements&oldid=51430