PROCESS IMPROVEMENT PROJECT
My Role
Project Manager
Tools Used
Google Slides
Google Sheets
Google Docs
Project Goal
Process Improvement of Inherited Project
Duration
1 week
2020
*This project was performed for educational purposes within the Technical Project Manager Boot Camp Course I completed (Aug - Dec 2020).
The client had hired a consulting company's project manager to manage a project that involved customizing their internal software as to allow the firm to better manage and analyze their financial and accounting company data. However, the client was unhappy with their original hire's performance and initial results, so they decided to change project managers.
This project was transitional in nature so required reviewing project artifacts that were inherited from the client's original hire. The original project manager fell short in some key project planning aspects. The client was unhappy with the list of requirements as well as the risk and communications plans they were given, and saw that they were filled with errors and missing information. As a result, the goal of this project was to fix what the client was given and present to them an improved set of project artifacts.
First, we evaluated the original documents at determined what was correct or incorrect, and what we can conserve.
Next, we chose a suitable methodology that suited the project based off the client's needs and preconditions. We decided that the hybrid methodology, Agifall, would be best suited for this project and provided our justifications to the client.
Then, after analyzing the requirements already drafted by the previous manager, we were able to provide detailed requirements to the client in the form of epics and user stories that were composed correctly .
Next, in order to layout the scope of the project, we put together a hybrid work breakdown structure that would involve a total of six sprints, two for each epic. We also provided a project schedule in the form of a Gantt chart, and a project budget that quickly estimates the cost based off the schedule.
Finally, both the project communications and risk management plans were drafted. For the risk management plan, we included three documents: the roles and responsibilities document, the risk matrix, and the risk register. Keeping it simple for the communications plan, we chose a more Agile approach to communications and provided a some points as to how general communication was to happen between everyone involved in the project.
Evaluated planning documents for a disorganized project.
Recommended an SDLC based on project characteristics.
Critiqued and revised user requirements.
Broke down project scope into deliverable increments.
Created a project budget.
Created a project schedule.
Rewrote a risk management plan.
Rewrote a communications management plan.
Reviewed a peer's comprehensive project plan and provided constructive feedback.
Evaluated the process of correcting a disorganized project, and recommended improvements for future project clean-up experiences.