Project Activities and Sequencing Scenario
Order ID:89JHGSJE83839 Style:APA/MLA/Harvard/Chicago Pages:5-10 Instructions:
Project Activities and Sequencing Scenario
Samantha Kelleigh
University of Phoenix
CPMGT/301
08/24/2020
Gary Denney
Project Activities and Sequencing Scenario
In order to have a successful outcome for a project, utilizing a Work Breakdown Structure and a project schedule is crucial. This allows a project to follow a proper timeline based on the Work Breakdown Structure so that crucial tasks and milestones are met during every step of the way. The Work Breakdown Structure is especially important because it breaks each task and milestone into finer, more detailed information that gives a project manager and their team the proper knowledge to continue carrying out their project. From the Work Breakdown Structure we are able to produce a project schedule that keeps the project manager and team members on track and gives them the information they need to successfully complete their tasks of the project in a timely manner.
Project Scope
For my company, a small shipping company and warehouse, we need to update our fifteen computers in order to make them more efficient in tracking, shipping, receiving, and inventory. The catch is, the computers will be down for about 5.5 hours and there are only two employees who are trained in updating the software on these computers. These employees are also under the direction of a different manager. In order to generate a faster working system in a timely manner, the project needs to extend the original business hours of the shipping company from 7am to 7pm Monday through Saturday and adding on 11am to 7pm on Sundays. This added day will allow the employees to update these computers which at the same time not affecting the current business of the company. One other thing the project manager should consider is training one of their own employees on updating the software to allow for more people to work on the computers at a time, thus making the project end date a bit sooner.
Project Stakeholders
There are three major stakeholders in this project. The first one, of course, is the shipping and warehouse company. They will be directly affected by the fail or success of the project and they are relying on this project to create a more efficient and quicker process for tracking, shipping, receiving, and inventory. The next stakeholder is the customers who demand product and services from the company. During the project they will be affected by possible computer downtime, as well as being affected from the fail or success of the project. With success they will be able to use those services and purchase those products with ease and in a shorter amount of time. Lastly, our final stakeholder would be the project manager. Their input directly affects the fail or success of the project. While they do collect data, information, and opinions from their team members, ultimately they are the ones who make the final decisions.
Necessary Tools
The necessary tools needed for this project is minimal but important. First, you need a contract from the vendors who supply the fifteen software updates. This contract will allow the company to use the software update to the fullest while also having a warranty in case the system update doesn’t work properly. You also need the trained employees to be willing to work out from under their current management and spend additional hours doing the updates. Another tool this project needs is the utilization of a Work Breakdown Structure and a project schedule.
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 Have 15 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? Project Milestones
The milestones of a project are much different than the tasks that are to be accomplished. In this project there are five milestones. The first milestone is the project conception and initiation. During this milestone the project goals and initial plan are brought together. Next is the planning of the project. This includes creating the scope, the budget, a Work Breakdown Structure, a project schedule and identifying the risks. Third, we have the project launch. 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 work space is ready. Fourth, the project is well underway and the software is being installed. And lastly is the project close-out which involves testing each updated computer’s working ability, it’s efficiency, and the comparison of data to acknowledge if the project goals were met.
Project Schedule
(When copying the table I created in excel and pasting it here, it stretched out the formatting making it ineligible. I have attached the table as well.)
References
A guide to the project management body of knowledge (PMBOK guide). (2017). Newtown Square, PA, EE. UU.: Project Management Institute.
Levin, G. (2015). Portfolio management: A strategic approach. Boca Raton: CRC Press.