STAKEHOLDER REGISTER Shareholder Register KEY TEAM MEMBERS ID Shareholder’s Name Shareholder’s Title

STAKEHOLDER REGISTER

Shareholder Register

KEY TEAM MEMBERS

ID

Shareholder’s Name

Shareholder’s Title

Mobile Number

Email Address

Project Role

Influence

H / M / L

Outcomes

1

Student’s Name

Rawaz Ramadan

(573)697-4987

Rawaz.ramadan@snhu.edu

Develop detailed project plans, ensure resource availability and on-time delivery of deliverables.

H

Deliver the Project Sponsor’s expectation.

2

Michael Lee

Software Architect

(306)249-3692

leemichael@ABCSolutions.com

Collaborate with the Project Manager and Project Sponsor in building the architectural models.

H

Provide the architectural blueprints to follow.

3

Simon Bloom

Software Developer

(772)907-4168

bloom_simon@ABCSolutions.com

Involved in every software development life cycle.

H

Improve the software from time to time.

4

Warren Olson

Software Tester

(724)284-4233

warren_olson@ABCSolutions.com

Performs manual testing to the software applications. Usually responsible to oversee any errors.

H – M

Avoid any system or software error by consistently checking the database.

5

Patryk Jordan

User Interface Designer

(248)926-8256

jordan_cole@ABCSolutions.com

Resolves any usability problem by creating a conducive user system.

H

Make UI design more user-friendly.

6

Cole Riddle

UI Developer

(336)418-3146

cole-riddle@ABCSolutions.com

Create a functional and visually appealing software.

H

Produce a practical and useful software.

7

Braden Bell

Technical Team Leads

(567)319-8534

bell_braden@ABCSolutions.com

Develop, Install and Troubleshoot technical problems to successfully execute the project

H – M

Monitor the progress in the project and mitigate any risks as soon as possible.

DEVELOPMENT – CONSULTANT TEAM

ID

Shareholder’s Name

Shareholder’s Title

Mobile Number

Email Address

Project Role

Influence

Outcomes

1

Julia Smith

Product Manager

(252)658-2180

smithjulia@ABCSolutions.com

A customer advocate who is assigned to articulate the customer requirements.

M – L

Be in communication with the client and the end-user.

2

Ryan Hernandez

Team Lead

(435)665-2992

hernandezryan@ABCSolutions.com

Training employees, sets strategies, and monitors performance.

M – L

Make sure that any changes do not affect the uptime of the system.

**H: High ** M: Medium **L: Low

Table 1. Stakeholder Register

Human Resource is the most important part of running a project. A project is an agreement between the provider (firm) and the client (another company). It can only be accomplished through specific guidelines. These guidelines are the duties that a stakeholder need to fulfill.

The table above shows who are the key persons and their department assignment. They are Project manager, Software architect, User Interface (UI) Designer, UI Developer, Technical Team Leads, Software Developers and Software Testers. On one hand, the Product Manager and Team Lead is only a limited resources. The above-mentioned personnel are expected to undertake their role within their level of influence in the project (Roseke, 2019). As the name suggests, high depicts influential and low shows less authority in the project.

RISK REGISTER

Project Name

XYZ Business Workflow

Date

03/01/2021

Project Manager

Rawaz Ramadan

Project Owner/Client

XYZ Financial Services

Document Number

QSO 340

 

 

Risk Description

Probability

Impact

Response Plan

Person Responsible for the Risk

Status

(1-5)

(1-5)

End user engagement is low because users are change resistant.

3

5

The design team should enact beta testing and user testing or surveys.

Patryk Jordan and Cole Riddle

C

Software compatibility (Software systems could not work simultaneously).

4

5

Review the software architecture and identify the potential causes of software incompatibility.

Warren Olson and Braden Bell

C

Resource availability (Lack in right financing, time management, and skilled workers).

2

5

Track the resource availability from time to time through the project dashboard.

Project Manager and Ryan Hernandez

C

Inevitable changes in the environment (COVID 19 risks).

4

5

Follow the skeletal workforce system that has been implemented last year. Any changes in legal policies should be implemented.

Project Manager

C

Table 2. Probable Risk That The Project May Encounter

The table below elucidates the possible risks that may happen in different aspects of the team. The main problem that can be cited may happen concerns the end-user. Since the client wil rework its business to streamline efficient ways for its processes, its employees may or may not receive the project well. Another probable risk that may happen targets the software compatibility. Given that the technology is changing rapidly, the software development personnels may experience difficulties in aligning the software to the client’s expectation. Such is also connected to the next risk which is resource availaibility. If some tasks are not foreseen to happen, the team may not be able to cope really well. However, the response plan can save the project and the team members. If the Project Manager, Product Manager, and Team Lead will collaborate together, any defficiencies can be overcomed. Lastly, the inevitable changes in the environment is also acknowledged as a risk. This one is beyond anyone’s control but if the team were able to deploy strong skeletal workforce prior to the commencement of the project, then it will be easier to cope from any disruptions.

WBS

WBS

TASK NAME

START DATE

DUE DATE

DEPENDENCIES

1

Project Management

March 1, 2021, to March 03, 2021

Start to Start

1.1

Requirement Analysis

1.1.2

Deliverable: Finalized Project Charter

Start to Finish

1.2

UI Design FGD and Planning

March 04, 2021

March 18, 2021

Finish to Start

1.2.1

Feature 1

March 12, 2021

April 16, 2021

Finish to Start

1.2.2

Feature 2

April 23, 2021

May 07, 2021

Finish to Start

1.2.3

Feature 3

May 10, 2021

May 19, 2021

Finish to Start

1.2.4

Deliverable: Finalized 3 Features

May 20, 2021

May 21, 2021

Finish to Start

1.3

Software Design FGD and Planning

May 24, 2021

May 28, 2021

Finish to Start

1.3.1

Feature Customization 1

May 28, 2021

June 25, 2021

Finish to Start

1.3.2

Feature Customization 2

June 25, 2021

July 16, 2021

Finish to Start

1.3.3

Feature Customization 3

July 19, 2021

August 06, 2021

Finish to Start

1.3.4

Feature Customization 4

August 09, 2021

August 20, 2021

Finish to Start

1.3.5

Feature Customization 5

August 23, 2021

September 1, 2021

Finish to Start

1.3.6

Deliverable: Finalized 5 Feature Customization

September 2, 2021

September 3, 2021

Finish to Start

1.4

Support

September 5, 2021

September 14, 2021

Finish to Start

1.4.1

Quality Assurance

September 6, 2021

September 9, 2021

Start to Start

1.4.2

Software Beta Testing

September 14, 2021

Start to Start

1.5

First Rollout

September 15, 2021

Finish to Finish

1.5.1

Milestone: Release XYZ Business Workflow 1.0

1.6

Software Maintenance

September 16, 2021, to December 14, 2021

Start to Finish

1.6.1

Communicate with the user

Start to Finish

1.6.2

Collaborate with the project sponsor for any room of improvements

Start to Finish

1.6.3

QA Documentation

Start to Finish

1.7

Final Rollout

December 15, 2021

Finish to Finish

1.7.1

Milestone: Release XYZ Business Workflow 1.1

Table 3. Work Breakdown Structure

The table above states the series of activities that needed to be accomplished to achieve the first and second software rollout for XYZ Business. The table adapts the four types of dependency relationship (Spacey, 2015). The type of dependencies is finished to start, start to start, finish to finish, and start to finish. The project will run from March 1, 2021, to December 15, 2021.

NETWORK DIAGRAM

END PRODUCT

END PRODUCT

PROJ. ROLLOUT

PROJ. ROLLOUT

SOFTWARE MAINTENANCE

SOFTWARE MAINTENANCE

SUPPORT

SUPPORT

UI DESIGN

UI DESIGN

SOFTWARE DESIGN

SOFTWARE DESIGN

SOFTWARE DEV

SOFTWARE DEV

REQ ANALYSIS

REQ ANALYSIS

START

START

RESPONSIBILITY ASSIGNMENT MATRIX

LEGENDS:

RESPONSIBLE

ACCOUNTABLE

CONSULTED

INFORMED

TASK NAME

Project Manager

Software Architect

Software Developer

Software Tester

User Interface Designer

UI Developer

Technical Team Leads

Product Manager

Team Lead

Project Management

R

Requirement Analysis

R

Deliverable: Finalized Project Charter

A

UI Design FGD and Planning

C

R

R

A

A

Feature 1

I

C

R

R

Feature 2

I

C

R

R

Feature 3

I

C

R

R

Deliverable: Finalized 3 Features

I

C

R

R

C

Software Design FGD and Planning

R

R

C

A

A

Feature Customization 1

I

R

R

C

Feature Customization 2

I

R

R

C

Feature Customization 3

I

R

R

C

Feature Customization 4

I

R

R

C

Feature Customization 5

I

R

R

C

Deliverable: Finalized 5 Feature Customization

I

R

R

C

C

Support

R

R

Quality Assurance

R

R

Software Beta Testing

R

R

R

First Rollout

I

Milestone: Release XYZ Business Workflow 1.0

I

C

R

R

Software Maintenance

Communicate with the user

R

Collaborate with the project sponsor for any room of improvements

R

R

QA Documentation

R

C

Final Rollout

R

R

Milestone: Release XYZ Business Workflow 1.1

R

R

Reference:

Roseke, B. P. (2019, March 13). The Parts of a Stakeholder Register. Retrieved July 18, 2021, from https://www.projectengineer.net/the-parts-of-a-stakeholder-register/

Spacey, J. (2015). 4 Types of Project Dependency. Retrieved July 18, 2021, from https://simplicable.com/new/project-dependencies

ABC SOLUTIONS PROJECT PLAN