Documente Academic
Documente Profesional
Documente Cultură
Stakeholders are “individuals and organizations who are actively involved in the project, or
whose interests may be positively or negatively affected as a result of project execution or
successful project completion” (Project Management Institute (PMI®), 1996).
Every project has its own unique stakeholder that might not be very evident and these
stakeholders might have different disagreeing expectations and wants from the project. Hence,
stakeholder analysis is a crucial practice for any projects to be successful. ( Mulcahy 2013)
Data gathering techniques such as interviewing and/or brain storming can help you identify and
analyze stakeholders ( Mulcahy 2013). The identification focuses on both internal and external
stakeholders (users, developers, decision makers etc.) throughout the project predicted lifecycle.
(Mibei, 2018)
In addition to analyzing stakeholders and their potential impact, you need to identify ways to
manage those impacts successfully. Design negotiations and interventions, forecast risks and
thresholds, and predict sources of conflict and cooperation.
The next phase after gathering of data is an analysis of the data. Analyzing the result of the
benchmark will put the app into viewpoint for each area (performance, ease of use, design,
creativity, price, UI etc.) that was studied. This will enable you make out the gaps in your app’s
working ability and incorporate the new improvements in your app.
System environment analysis is the hub for the structural requirement; it is an important
requirement in the elicitation process since the mobile application is going to be fixed in the
client’s already existing system environment. The system environment analysis will examine
how the functions in the IT system environment will be programmed and implemented.
The analysis has to identify the interface, modules, services, security and support system of the
existing system and the system needed for the mobile application (Liu et al., 2016). The first
phase of the system analysis is to get an understanding of the related existing systems and this
can be achieved in an interview process with the person or persons responsible for the client’s IT
process. This will help reveal what existing module could be adopted into the new system and
also understand which existing module and interface is impacted by the new application and
what tools are needed to enable proper usage of the application (Pries and Quigley, 2008).
2.2 Personnel Analysis
Generally a mobile app project will involve significant contributors who play significant role in
the development and execution of the project. These are individuals who contribute to the
execution or the scientific development of the mobile app. Their contribution should be
measurable in a substantive way. It goes to say that no project can survive without key personnel.
One question should be asked; does the client have the necessary personnel with relevant skill set
to run the functions? Because, only with the appropriate personnel can a mobile app project be
fully developed and implemented.
Personnel analysis shows what is available and what will be needed to actualize the project
goals. It compares the project requirements and tasks with the current personnel strength of the
client.
The first step in this analysis is defining, planning and assigning project roles based on the
functional requirement and results from the application benchmarking. This project role has to be
rooted within the client’s organizational structure (Mibei 2018).
The second phase in the analysis is working with the HR or top management to get pessonel job
description and taking the information gathered in the project role planning and matching it to
the client organizational talents.
Risk identification can be done using some tools and techniques like documentation reviews
containing experiences from previous client projects. Identification can also be done by using
information gathering technique like brainstorming where one idea helps to spawn another.
Once risk identification has been done, what should be done to all the risks identified has to be
determined. An analysis of the risks and its potential impact on the project to determine which
risk or risks needs a response is carried out using a probability and impact matrix (likelihood and
risk impact). This is because not all risk can be dealt with as it will have an effect on project
resource (time, cost, personnel etc.).
Just like each project, the client’s mobile application project consists of individual steps which
have to be undertaken. In order to get an overview of the time the company has to spend for the
project, project time planning is an important step to reveal temporal requirements. Especially
for software engineering projects, time estimates depict a special challenge due to the high
complexity and dependency on uncertain proceedings (Lock, 2013). A breakdown of the
network-based task is the first step in IT time planning. Once this is done, the next step is to
organize them in accordance to their logical sequences and dependencies that estimates each
activity and the total time needed.
Liu B. et al. (2016).Structural Analysis of User Choices for Mobile App Recommendation.
[Online]. Available from: https://arxiv.org/abs/1605.07980 [Accessed 29 October 2019]
Mulcahy. R (2013). Project management professional Exam prep, 8th edition pp395-435
Mibei. H (2018). Requirements elicitation for mobile B2B application for company X, a project-
based consulting approach. Available at: www. Academia.edu [Accessed 27 October 2019]
Pries, K.M. and Quigley, J.M. (2008), Project Management of Complex and Embedded Systems
Ensuring Product Integrity and Program Quality. Hoboken: Taylor and Francis.
Project Management Institute (2013), “A Guide to the Project Management Body of Knowledge
(PMBOK Guide)”, Newtown Square, Pa.: Project Management Institute.
Vlachý, J. (2014), “Using Life Cycle Costing for Product Management”, Management,
Vol.19(2), pp. 205-218.