DOK7_PJ

Project One: Project Plan

XYZ Business Workflow Project Plan

Stakeholder Register

To ensure a smooth running of the project, which will eventually lead to success, identifying stakeholders and engaging them in the preliminary stages of the project will help establish a strong communication strategy, meet the primary requirements, and avoid time and resources wastage. In this project, stakeholders are the individuals who are actively involved in the software development project process and whose interests may be affected by the project's success or failure. Two stakeholders will be involved in the project: the primary stakeholders involved directly in the project and the secondary stakeholders. They are involved indirectly in the project.

First, the primary stakeholders are the ones directly involved in the project and include; the project manager, who will be responsible for the planning process, project budgeting, creating the schedule, initiating execution and delivering the software. The project manager will also ensure that the project is completed and oversee the persons involved in the project. Then we have the software architect, who will build the high-level design options and frame the technical standards; the user-interface (UI) designer will create the screens through which a user will navigate while using the software. Then, the UI developer will translate the creative software concept design and ideas done by the UI designer into reality with the help of front-end technology.

The technical team leads will ensure as per their respective teams that the local context is defined and incorporated in the project and presenting it to the project manager. Then the software developers will carry out the designing and installation of the software. Finally, the software testers will ensure the quality of the software and conduct the deployment of the software. Another important stakeholder in the process is the customer, who will provide the satisfaction of the built software.

Although secondary stakeholders don't directly engage in the project, their role is not to be undermined. They indirectly affect the decisions related to the software and its reputation; this is very important, especially in identifying areas of improvement for the product. These stakeholders include the end-users, who will be engaged in the testing stage of the software and will help point out the missing features to enhance user-experience improvement.

The government, as a stakeholder, will affect the development of the software by imposing some of the minimum standards that the software should meet and can impose fines on failure to meet such regulations. Finally, competitors will introduce a new feature to the market and create new, unexpected challenges that you have to respond to them. The below shows a summary of the primary and secondary stakeholders.

Risk Register

Risk registration is essential in the project as it identifies the potential setbacks within the project, which will help in the risk management process. The table below shows four significant risks involved in the project and how the risks can be possibly mitigated to reduce the loss of resources.

Work Breakdown Structure (WBS)

The project's work breakdown structure will ensure that the step-by-step approach is made to complete the large project; this will involve breaking down the project into smaller components to incorporate the scope, cost and deliverables into a single tool (Burghate, 2018). The work breakdown structure of this project is as shown below.

Schedule Network Diagram

The schedule network diagram further breaks down the work breakdown schedule (WBS) by describing the project deliverables, the software and offers timelines. It shows how the tasks will be carried out and the logical relationship between the functions. This is simply giving a picture of the "What", "When", and "Who" of the project

The SND diagram is a valuable tool for visualization to help manage the project schedules. It will aid in determining the project duration and support the project team to allocate resources appropriately. Also, the group will appreciate the relationships between the project activities and assign buffers where necessary.

Responsibility Assignment Matrix

It describes the participation of various teams of the project in the completion of the tasks of the project. The program manager will use it to specify the roles and responsibilities of each group. To develop an effective assignment matrix for this project, some of the essential factors that should be considered are the project activities and deliverables, identification of the project stakeholders, determining the role of each team member and the level of accountability for each activity, assigning the stakeholders tasks and ensure that each stakeholder knows and understands their role in the study given. The below is a responsible, accountable, consulted and informed (RACI) matrix that breaks down the large project tasks.

P=Primary Responsibility

S=Secondary Responsibility

AP= Approval