Software Management Risks: Project Management and Open Source Software

This assignment delves into the critical aspects of software management risks, addressing potential issues in project development and the utilization of open-source software. The first part of the assignment analyzes common risks within project lifecycles, such as project flaws, requirement inflation, and long deadlines, providing illustrative examples of their adverse impacts, including reputational damage, project halts, and reduced productivity. The second part focuses on the dependency issues associated with open-source software, highlighting the need for thorough research on privacy implications and security checks. It emphasizes the vulnerabilities that can arise from open access to source code, leading to potential malware and security breaches, while also acknowledging the cost-saving benefits of open-source applications.

Running head: SOFTWARE MANAGEMENT RISKS
Software management risks
Name of the student
Name of the University
Author Note

1SOFTWARE MANAGEMENT RISKS
Answer to question 1:
For the development of a project, management is always considered for considering the
budget and analytical information regarding the process. The manager of the project is supposed
to carry out all the steps required for a successful project completion. However, the process of
analytical information gathering is not simple and risks or threats are evident in the entire project
life cycle. Even under very controlled conditions, risks can arise in the of a project life cycle.
Many of these risks may arise due to mismanagement or negligence in considerations.
The existence of flaws is a very common incident in a project. However, the level of the
flaw occurred will determine the problem. This is the first risk that may be present in a project
life cycle. As a project life cycle involves various steps that are to be followed before
commencing with the project, the complex analytical considerations cannot be simply considered
(Fleming and Koppelman 2016). This result in flaws which are later reflected in the project
development stages.
The next risk is the inflation in the considered requirement for the project. Requirements
are a major aspect that is always considered in the planning phase of a project (Schwalbe 2015).
However, as the requirements of the stakeholders may change or some requirements may get
missed out due to the increase in complexity of the project, inflation occurs due to this.
Lastly, long deadline is another risk to the success of the project as the members
responsible for the project does not finish their requirements (Kerzner 2013). This removes the
need for urgency and after reaching close to the deadline, the members complete it however
possible.

2SOFTWARE MANAGEMENT RISKS
Example 1:
The first cause of problem occurrence due to the presence of flaws will be responsible for
the project not meeting the set deadline. As a result, the company responsible for the
construction of the project will lose their reputations in the market which will eventually lead to
less business acquisition.
Example 2:
The problem due to the inflation in the project requirements can lead to a halt if the
requirement is proportionately very large in comparison to the considered amount in the planning
phase. In case such conditions occur, the period of halt would be very long where resuming the
work may take a large amount of time.
Example 3:
Another scenario which depicts the impacts due to risks in project management is the one where
long deadline frequently occurs. The project members lose their need for urgency and undertake
their task in a very slow manner. However, in case the assigned deadline comes close, the
members then complete their remaining task by undertaking several methods possible. This
reduces the effectiveness of the project ultimately leading to a reduced productivity.
References:
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management.
Project Management Institute.

3SOFTWARE MANAGEMENT RISKS
Kerzner, H., 2013. Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Answer to question 2:
Open source software is considered as those applications whose source code and the
application itself are available to anyone. In cases like this, the open source software consists of
different characteristics that are considered superior in comparison to the customized
applications (McLean 2015). Some examples considered as open source software are the
operating system. However, there are many dependability issues which exist due to these open
source software applications.
The first issue surrounding the open source applications is the need for research. The
research helps in analyzing the prospect of considering the privacy requirements for the open
source products. As they are open sourced, the privacy and security are also very low. As a
result, giving access and permissions to it requires full research of the effects it may have. As
there is a major list of open source applications, it becomes difficult to research and analyze the
privacy issues of each request (Martínez-Torres and Diaz-Fernandez 2014). As many open
source software products are used for the development of new software specifications, it makes it
a pre-requisite for analyzing the security and privacy implications of them.
Another issue considered in the dependency section of an open source application is the
need for security checks. As open sourced applications have their source codes open, it can be
accessed by anyone. Advanced hackers can modify the source code available and make a
malware out of it. This bug application will then be released in the internet and people with less

4SOFTWARE MANAGEMENT RISKS
knowledge of security implications will be affected. As a result, the software will lead to major
breaches and hacks in a system. This will also lead to information breaches which are the sole
outcome of unethical hacking (Colombo, Piva and Rossi-Lamastra 2014). On the same time, the
vulnerabilities on a source code can be found by a hacker and can be used for breaches. For
example, the biggest ransomware attack that affected the whole world was the main cause of
such issues. The cause for the attack was the presence of vulnerabilities in the operating system
of Microsoft which was discovered by the attackers. This was considered as a major problem
which affected millions of people worldwide.
Although there are many reasons where open sourced software applications are not
considered to be applicable, it can however be useful in many cases. As the cost of the software
is free, it reduces the overhead charge needed for a company for applying in their process. This
also reduces the need for a company to consider making an application an application and then
doing business. In cases like this, open sourced applications are termed appropriate.
References:
Colombo, M.G., Piva, E. and Rossi-Lamastra, C., 2014. Open innovation and within-industry
diversification in small and medium enterprises: The case of open source software
firms. Research Policy, 43(5), pp.891-902.
Martínez-Torres, M.R. and Diaz-Fernandez, M.D.C., 2014. Current issues and research trends on
open-source software communities. Technology Analysis & Strategic Management, 26(1), pp.55-
68.
McLean, A., 2015. Open-Source Software. Canadian Journal of Nursing Informatics, 10(3).