Project cap 4
Kinsley Foster
July 27, 2019
PM 430
Software Implementation Portfolio Project
Abstract/Executive summary:
The purpose of this project is to implement new software into the company to increase productivity. The company uses its current software to create logos, labels, and many other things for large companies. The other goals are to update the protection on the software because in the past there have been a few problems with the security of the software and the information on the software. Another important goal is to have the computers and memory updated to work more efficiently that before. The software has been slow and has not been able to keep up with the new graphics needed for the current projects. The software will crash and then be down for days or longer. This is causing loss of customers and over all bad for the company.
The overall goal for this project is for the new software to be installed, working properly, and producing the power needed to create the projects for the company. I, as the project manager have decided to do agile methodology for the project. There have been multiple projects prior to this one done the same way and it seemed to go well for the company. The project is set to start August eight, so in just a few days and everything is going as planned. The deadline for this project is December twelfth. The project should be about one hundred days long from begging to end. The budget for this project is two hundred fifty thousand dollars and it is being estimated at just over two twenty-four thousand dollars. There is a continuity budget of twenty thousand dollars.
Work Breakdown Structure
Activity/Network Diagram:
Due to space the rest of the Network diagram will be submitted in MS project form. To view critical path, logical relationships, lead/lag, and ES/EF/LS/LF will be easier to view in MS project as well.
Schedule and Budget:
To look at the schedule and budget more in depth and to view the rest of it please view microsoft project.
Change Management Plan:
This project will be an agile project methodology. Since this projec is agile methodology there will be a lot of change and will need to be processes in place to manage the changes. One important tool that will be used to keep up with changes is a change request form. This form will help state what is needed and why and all of the details for the change. Anther important tool is managing the triple constraint of the scope, budget, and quality of the project. When changes come these things will change too. Manging these things can help keep the project from risks and other problems.
The process that will be used for this project is the John Kotters eight-step change process. It consists of eight steps to guide and lead change in a project. The first step is creating urgency. This is basically like triaging the changes by determinng which ones are most important and need to happen sooner than less important changes. Forming a team for the change is the next step. This step is important because without a team to make the change happen. The next step is creating a vision. This step is to help everyone vision the change and what it can do and why it is neccascry. Removing obstabcles is the next step. This step is important because every project will have problems come up and having the team come together to fix these things is very important. Creating short-term wins is the next step and this one is about showeing the group what rewards can come out of the project change that is happening. Repeating the steps is the next step. This step is to simply repeat the steps to ensure that the change was effective and nothing was missed. Finally, is to embed the change into the project and let it function as normal now.
Communication Mangement:
Every project has to have commuication within it. During this project there will be progress report meetings, quailty report meetings, risk report meets, staff meetings, change meetings, budget meetings, resource meetings, and many more types of meetings that are important to all staff.
Communication Diagram:
Who: How:
|
Vendor communication: |
Software selection meetings, email, video confrences for ordering materials |
|
Contractor communication: |
Quality report meetings, risk meetings, weekly report meetings, and emails. |
|
Stakeholders |
Quality report meetings, risk meetings, change request meetings, weekly report meetings, emails, phone calls, conference and calls. |
|
Customers |
Quality report meetings, risk meetings, change request meetings, weekly report meetings, emails, phone calls, conference and calls. |
|
Employees: |
Quality report meetings, risk meetings, change request meetings, weekly report meetings, emails, phone calls, conference calls, morale meetings, and morning start up meeting. |
Risk Management plan:
Quality control and management:
Controlling and managing quality for a project is very important and challenging for a project. You want to be able to ensure quality throughout the project to make sure that the products that are being delivered are to the quality standard needed and promised. One thing that can be done is to do audit the quality of the project. This is done by auditing different departments on its progress and quality and it helps you determine the quality. Anther thing that can be done is to do quality assurance on certain things like the processes the project. For example, if you needed to measure quality on the installation of the software you could test the software to ensure that it is working properly and to its full limits. If not, then you know that there was something wrong with the install. Controlling quality is important and can be done by using the tools to ensure they are to the right standards. For example, if the tools are used and it is determined that the quality is low or not to standard then that gives you the information you need to fix the problem. If you do not measure or monitor quality, then the products produced will not meet the customers needs.
Procurement Plan:
The Procurement plan for a project is about purchasing items from outsources or external companies or people for the project. The Procurement plan is a plan about how these items were obtained and things that were done to select these items and the process of selection. Some of the steps in procurement management is managing the items ordered, reviewing the orders, reviewing the receipts, and more. Procurement can also be about physical work being done in a project.
Make or Buy Analysis: This analysis is very important to our company. This is an analysis done to analysis if it would be in the interest of the company to make (complete the task in house) or buy (outsource the work). This analysis is done by analyzing the costs for both methods, resources, materials, timeline, scheduling, and workload.
Statement of work:
Purpose: The reason this project is needed for our company is because the current software we have is not strong enough to handle the new graphics needed to make our products.
Scope: This software implementation project is for the implementation of new software in our company. The overall deliverable is to have a functioning software application able to produce our high quality adds, logos, and more. There is an overall budget of two hundred fifty thousand dollars. The scheduled work time is at ninety-nine days.
Deliverables: The overall deliverable is to have functioning software on all computers in our company.
Location: Green Dot Company 1234 Perters Street Greenburg MI, 56998
Payments: Vendor will be paid up front for costs of the project and their personal pay
Project Period dates: August 1, 2019- December 17, 2019
Selection Criteria: This helps our company choose the correct vendor for your project by seeing which vendor can meet your requirements best for our project.
1: Not able to perform much of the criteria
5: Able to give the best performance for the Criteria
|
Criteria: |
Vendor A |
Vendor B |
Vendor C |
|
Able to upgrade all computers with new software |
4 |
3 |
1 |
|
Able to deliver the finished product on time |
4 |
1 |
4 |
|
Able to deliver the finished product on budget |
5 |
1 |
4 |
|
Able to produce the product with acceptable quality Past experience with software implementation |
3 |
5 |
2 |
|
Overall Rating |
16 |
10 |
11 |
Stakeholder Register:
|
Role: |
Contacts |
Category: |
Influence: |
Interest: |
Expectations: |
|
Project Sponsor |
Blake Smith Phone: 858-858-8585 Email:bfgreendot.com |
Internal |
High |
High |
Keep project strategies allgined |
|
Project Manager |
Kinsley Foster Phone: 656-656-6565 Email:kfgreendot.com |
Internal |
High |
High |
Project to be delivered on time and on budget |
|
PMO |
Samuel Barnes Phone: 959-959-9595 Email: sbgreendot.com |
Internal |
High |
Moderate |
Software implementation done successfully |
|
CEO |
Ashely Green Phone: 787-787-7878 Email:aggreendot.com |
Interanl |
Moderate |
Moderate |
New software to help increase company’s customers and maintain |
|
Productions manager |
Bellamy Barker Phone: 656-656-6565 Email:bbgreendot.com |
Internal |
Low |
Moderate |
To product high quality products |
Stakeholder Engagement Assessment Matrix:
|
Stakeholder |
Unaware |
Resistant |
Nuetral |
Supportive |
Leading |
|
Project sponsor |
|
|
|
C |
D |
|
Project Manager |
|
|
|
|
C |
|
PMO |
|
|
|
C |
D |
|
CEO |
|
|
|
|
C |
|
Productions Manager |
|
C |
D |
|
|
References:
Wale, S., Wale, S. (2017, May 09). Stakeholder Register Template. Retrieved July 26, 2019, from https://www.techno-pm.com/2017/05/stakeholder-register-excel-template.html
(n.d.). Reitrieved July 25, 2019, from https://www.projectengineer.net/3-types-of-stakeholder-matrix/
(n.d.). Retrieved July 26, 2019, from https://tenstep.com/Procumentmanagementplan
Communication Matrix How-to & Template. (n.d.). Retrieved July 26, 2019, from https://www.teamgantt.com/communication-matrix-template
Manage and Control Quality. (n.d.). Retrieved July 24, from https://www.greycampus.com/opencampus/project-management-professional/perform-quality-assurance
Quality Assurance. (n.d.). Retrieved July 24, 2019, from https://aim.landscapetoolbox.org/quality-assurance-quality-control/quality-assurance/
How to Lead a Change Management Process. (n.d.). Retrieved July 26, 2019, from https://www.projectmanager.com/software/use-cases/change-management
Harrin, E. (2019, January 22). Manage Changes On your projects while keeping it all moving forward. Retrieved July 26, 2019, from https://www.thebalancecareers.com/managing-changes-on-project-4041353
6 Strategies for your software implementation plan. (2019, February 13). Retrieved July 26, from https://lab.getapp.com/software-implementation-plan/