Plan a project according to project management best practices

 

 

Scenario
You have been hired as a project manager for a software company, ABC Solutions. Their business development team has received a product request from a new client, XYZ Financial Services. They need a custom software solution to streamline some workflows and processes that will be implemented in their offices worldwide. Your company has developed a similar software solution, but the client requires additional features and customization. The new software needs to be ready for a test run at two of the offices in about six months and worldwide rollout in another three months. Your boss, the project director, has asked you to manage this product development project.

ABC Solutions uses the traditional waterfall method for software development. The proposed project schedule should include the following major tasks: determine the software requirements, design, code test, system test, address issues with software, and deliver the prototype. You have been asked to assemble a team with the skills and expertise to perform these tasks.

Before initiating the project, you, the project director, and a software architect meet with the IT director and product manager of XYZ Financial Services to understand their requirements. They explain that the custom software should include three new features, five feature customizations, and a new interface design to match the client’s brand colors and logo.

Later, you and some key team members analyze the scope and requirements to arrive at some critical decisions and conclusions. These have been summarized in two project documents:

The project charter PDF that includes the project objectives and other important details
A document with the efforts estimated PDF for each development task
You will need to choose and allocate resources from the following available team members: a user interface (UI) designer, UI developers, a software architect, technical team leads, software developers, and software testers. You will also have access to two team members from the development team of the original software, who will act as consultants for your team. However, these members are only available part time since they are also busy on other projects.

Directions
Project Planning
Use the information from the scenario, including the project charter and effort estimates, to create a single file that includes the following components: stakeholder register, risk register, work breakdown structure (WBS), and responsibility matrix. You can also make reasonable assumptions to help you complete these tasks. But, be sure to explain your assumptions. Address each of the tasks outlined below.

Stakeholder register: Identify and list the stakeholders for this project. Ensure it includes the following details:

Their names
Their role in the project
Their influence on the project and its outcomes
Risk register: Identify and describe at least four individual project risks, including the risks identified in the project charter. The register should include the following details for each risk:

The description of the risk
The probability the risk may occur
The impact the risk can have on the project
The response plan if the risk occurs
The person responsible for handling the risk
The status of the risk
Work Breakdown Structure (WBS): Create a WBS and Networking Diagram for the project. It should include the major milestones and all tasks arranged in the order they should be completed in the project. Also, be sure to indicate any dependencies between tasks.
Responsibility Assignment Matrix: Create a responsibility matrix with a responsible, accountable, consulted, and informed (RACI) chart that shows how the tasks in the project are assigned to the respective team members. Also, include a RACI chart for all stakeholders you identified earlier.
What to Submit
To complete this project, you must submit the following:

Project Management Plan
Create a project management plan that includes the stakeholder register, the risk register, the WBS, and a responsibility matrix. Combine all four components into a single file. Remember to cite any references in the

Sample Solution

Stakeholder Register

Stakeholder Role Influence Notes
XYZ Financial Services IT Director Client High The IT Director is the main decision-maker for the project. They will need to approve all major decisions and changes.
XYZ Financial Services Product Manager Client High The Product Manager is responsible for the overall product vision. They will need to provide input on the features and functionality of the new software.
ABC Solutions Project Director Executive High The Project Director is responsible for the overall success of the project. They will need to ensure that the project is completed on time, within budget, and to the client’s satisfaction.
ABC Solutions Software Architect Technical High The Software Architect is responsible for the overall design of the new software. They will need to ensure that the software meets the client’s requirements and is technically feasible.
ABC Solutions UI Designer Visual High The UI Designer is responsible for the overall look and feel of the new software. They will need to ensure that the software is user-friendly and visually appealing.
ABC Solutions Software Developers Technical Medium The Software Developers are responsible for the development of the new software. They will need to ensure that the software is coded correctly and meets the client’s requirements.
ABC Solutions Software Testers Technical Medium The Software Testers are responsible for testing the new software. They will need to ensure that the software is free of defects and meets the client’s requirements.

Risk Register

Risk Probability Impact Response Plan
Client changes requirements High High Regularly meet with the client to discuss their requirements and ensure that they are still aligned with the project goals.
Software is not completed on time Medium High Create a detailed project schedule and track progress closely. Have contingency plans in place in case of delays.
Software does not meet the client’s requirements Medium High Regularly meet with the client to gather feedback and make sure that the software is meeting their needs. Be prepared to make changes to the software if necessary.
Software has defects Low Medium Have a thorough testing process in place to identify and fix defects.
Software is not secure Low Medium Use secure coding practices and implement security measures to protect the software from unauthorized access.

Work Breakdown Structure (WBS)

Project Phase Task Estimated Effort
XYZ Financial Services Software Development Requirements Gather requirements 20 hours
XYZ Financial Services Software Development Requirements Create use cases 40 hours
XYZ Financial Services Software Development Design Create design documents 80 hours
XYZ Financial Services Software Development Development Develop software 240 hours
XYZ Financial Services Software Development Testing Unit testing 40 hours
XYZ Financial Services Software Development Testing System testing 80 hours
XYZ Financial Services Software Development Deployment Deploy software 20 hours

This question has been answered.

Get Answer
WeCreativez WhatsApp Support
Our customer support team is here to answer your questions. Ask us anything!
👋 Hi, Welcome to Compliant Papers.