Stakeholder Analysis, Risk Management for Accounting Software Project

This report examines the implementation of new accounting software within an organization, focusing on stakeholder analysis, risk management, and team roles. It begins by exploring how different organizational structures, such as projectized structures, impact team efforts and roles, referencing Belbin's team role theory. The analysis then identifies primary and secondary stakeholders, including internal employees, project managers, and end-users, emphasizing the importance of communication and managing stakeholder relationships. The report also details various project risks, such as delays, improper training, and financial risks, and outlines a risk mitigation process involving identification, analysis, planning, and monitoring. The report references key project management literature, emphasizing the importance of understanding stakeholder influence and managing project risks effectively to ensure successful software implementation.

Organization’s Management, Stakeholders analysis and, RISKS analysis
0

Table of Contents
Table of Contents.............................................................................................................................1
Determine as to whether different structures, projects, and context of the enterprise or
organization’s need different team efforts or roles?........................................................................2
STAKEHOLDERS ANALYSIS.....................................................................................................2
RISKS ANALYSIS.........................................................................................................................3
References........................................................................................................................................4
1

Determine as to whether different structures, projects, and context of
the enterprise or organization’s need different team efforts or roles?
An organization is defined as a group of persons or employees who work to achieve the
organization’s goals or objectives. According to Belbin team role theory, the behavior of every
individual should be measured when they are working as a team. The organizations should not
measure personality of the employee or individuals, they should measure individual behavior.
According to Skytova (2018 p.625), management of the projects can be impacted by
organization structures. In the given scenario, the firm or company is going to implement new
accounting software, so that they can automate their accounting operation. The management
should analyze nature of organizational structure that is whether it is matrix or, functional or
projectized. As all individual or employees of enterprise or firms are assigned as a team to
implement accounting software, structure is projectized structure. According to the theory, team
role means a tendency as to how to behave if they are given a project to complete. A team role is
an interrelation and contribution with other individuals in different ways. As per Belbin theory,
an individual in a team need not be equally educated to complete a project. In this scenario,
internal members such as employees as a team have been assigned for the installation of the
accounting software. If the roles assigned to the team are equally balanced, then a team even
with a little knowledge of the project will succeed in their project. In this case, as every
individual of the team is responsible for installation of software, the project will surely succeed.
If the roles of the team are different then there the probabilities of success is high but the goals
should be common and they should be motivated to achieve it. There should be clarity while
assigning team roles.
STAKEHOLDERS ANALYSIS
In the given scenario stakeholders who belong to primary category who are negatively or
positively impacted are the individuals who help in recoding the data, gathering data and also
helps in the distributing information in previous system used by enterprise, for example staff,
internal employees. According to Ahlan et al. (2015 p.271), the management of the project
should first identify the relationship between the team and the individuals and then engage them
to complete the project. The persons who have finite influence on the project such as the
manager of the project are primary stakeholder. Key persons of the project are sponsor of
project, community, client of organizations, research, and analyst group and end users. Software
2

engineers, project personnel, team members, leaders of project, team leaders of project are
secondary stakeholders of project. If the manager of the project is not taking advice of the
stakeholders while taking important decision then there can be dispute between the stakeholders
and project manager. If project manager hides all errors which have come across while
completing the project, there can be disputes between the project manager and stakeholders.
Project manager should make plans, reports, forecasts, and lessons which can work as a
communication tool to improve relationship between them.
RISKS ANALYSIS
The risks in the given scenario should be first identified and then it should be analyzed and then
it should be properly planned and last one is monitoring of risk. Risk drivers in the given
scenario are chains in the events, diagrams in the chains, the allocation of task relating to
implementation and installation of software. Risks which are associated with the given scenario
are delay in installation, improper training of software, safety risk, improper technical support,
cost of project, contractual risk, financial risk, environmental risk, risk related to client. Another
risk which is related with stakeholders is that if the software does not meet the stakeholder’s
needs, stakeholders will leave the project. According to Van et al. (2015 p.877), to eliminate the
risks which are related with project the project manager should identify main cause of risk and
then evaluate it. Risk mitigation process involves designing proper plan to mitigate the risk,
preparing a checklist and then according to checklist designing a proper well-structured plan to
mitigate risk.
3

References
Ahlan, A.R., Kartiwi, M. and Sukmana, H.T., (2015). Measurement of information system
project success based on perceptions of the internal stakeholders. International Journal of
Electrical and Computer Engineering (IJECE), 5(2), pp.271-279.
Skytova, G., (2015). Revealing Managerial Competences of MBA Students Using Belbin Role
Profile 6(1), pp.625-691.
Van Os, A., Van Berkel, F., De Gilder, D., Van Dyck, C. and Groenewegen, P., (2015). Project
risk as identity threat: explaining the development and consequences of risk discourse in an
infrastructure project. International journal of project management, 33(4), pp.877-888.
4