University Report: Agile Method Adoption - ENSE880 Analysis

This report investigates the adoption of Agile methodologies, analyzing the complexities encountered in IT projects across different decades. It begins by reviewing five key pieces of literature on Agile adoption, identifying complexities related to traditional methodologies, digital platform dependencies, employee job satisfaction, budgeting and timelines, and project dynamicity. The report then provides a thematic analysis of these complexities, highlighting issues such as the need for business case introductions, organizational transformations, the importance of quality, and the rigidity of traditional functioning. Furthermore, the report examines IT projects from the 1980s to the 2010s, discussing their critical issues, risks, and challenges, including scope, schedule, cost, quality, and the expertise of project managers and teams. The report references various projects such as Pac-Man, Adobe Photoshop, and Facebook, to illustrate how Agile methodologies address these complexities, offering a comprehensive view of Agile adoption in the IT landscape.

Running head: AGILE METHOD ADOPTION
AGILE METHOD ADOPTION
Name of the Student:
Name of the University:
Author Note:

1
AGILE METHOD ADOPTION
1 a.
Literature 1
Gandomani, T. J., & Nafchi, M. Z. (2016). The essential prerequisites of Agile transition and
adoption: A grounded theory approach. Journal of Internet Computing and Services (JICS), 5,
173-183.
In this paper the major complexity that is present includes issues related to issues related
to traditional methodology. There has been an increase in challenges in ATP due to the presence
of the traditional methodology. Inefficient human interaction in the processing of the software
development has been acting as the complexity, leading to implementation of Agile
methodology.
Literature 2
Rigby, D. K., Sutherland, J., & Takeuchi, H. (2016). Embracing agile. Harvard Business
Review, 94(5), 40-50.
In today’s society, increase in dependence of digital platform. This ensures the fact that
software development has been the major concern. This requires constant updating of the file.
Hence wise the other PMMs will not be capable enough to perform the updates other than Agile
methodology. Hence requirement in adoption of Agile PMM will be beneficial.
Literature 3
Vacari, I., & Prikladnicki, R. (2015). Adopting agile methods in the public sector: a systematic
literature review. In Embrapa Informática Agropecuária-Artigo em anais de congresso (ALICE).

2
AGILE METHOD ADOPTION
In: INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING AND
KNOWLEDGE ENGINEERING, 27., 2015, Pittsburgh. Proceedings... Pittsburgh: Pittsburgh
University, 2015..
In this paper the major complexity is considered includes the fact that there has been an
issue related to job satisfaction of the employees in the software development industry. This is
the main reason that efficiency of the functional process might be getting affected in a negative
manner. This is the major reason of Agile methodology implementation.
Literature 4
Ahimbisibwe, A., Daellenbach, U., & Cavana, R. Y. (2017). Empirical comparison of traditional
plan-based and agile methodologies: Critical success factors for outsourced software
development projects from vendors’ perspective. Journal of Enterprise Information
Management, 30(3), 400-453.
As per this literature the major complexity in the functional process of software related
projects. The main aspect that is considered in this case is that it is seen that issues related to
budgeting and timeline of the project execution. It is seen that in case of using the traditional
PMM, there is a rigidity in the processing and hence wise an increase in complexity. With Agile
PMM adoption this issue can be mitigated.
Literature 5
Papadopoulos, G. (2015). Moving from traditional to agile software development methodologies
also on large, distributed projects. Procedia-Social and Behavioral Sciences, 175, 455-463.

3
AGILE METHOD ADOPTION
Initially in the business organization, traditional PMM were used. Due to the usage of the
traditional PMM usage, the main aspect that is used includes the fact that dynamicity of
functional process is hampered. Issue regarding customer requests are also not met in a dynamic
manner as rigidity of the entire system is very high. Changes that are to be brought in are not
well introduced due to this PMM. With the help of Agile PMM, these issues can be mitigated.
b.
Themes Issue 1 Issue 2 Issue 3
Business Case ATP introduction
Organization Transforming to
digital platform
Quality Requires Iteration High rigidity in
functionig
2 a.
1980
Pac-Man
In the year 1980, projects regarding game development was performed. Arcade game Pac-Man
was released.
Critical Risk
 Failure in budget planning

4
AGILE METHOD ADOPTION
 Failure in Resource Allocation
Issue
 The programmers were inexperience
 Resource strength was low
Challenge
 It was the very first game being developed
 Licensing issues
Schedule planned was highly professional and the budget it had was very limited. Cost Quality
was very high and the skills were very high as well but the experience was a concern.
Space Invaders
Critical Risk
 The budget that was initially set was very low
 The game that was being designed was highly indifferent
Issue
 Improper gameplay
 Inefficient microcomputers in Japan to play the game
Challenge
 Make it compatible to the Japanese microcomputers
 Reduce complexity in the game

5
AGILE METHOD ADOPTION
Scope of the project is to provide proper entertainment to the clients. Schedule, cost, quality of
the products have been very high. The skill set was very high and the roles are diversified.
Unix to Unix copy
Critical Risk
 Error in copied data will be resulting in improper result
 Improper alignment from peer to peer networks
Issue
 Presence of minority of newsgroup
 Lot of information is required in RFD.
Challenge
 RFC 850 was the first formal specification and hence specification setting was a problem Budgeting is also an issue.
1990
Adobe Photoshop
Critical Risk
 It is the very first version and hence risks were unpredictable
 X86-64 implementation
Issue
 Gaining license

6
AGILE METHOD ADOPTION
 Performing photo shop mix.
Challenge
 Schedule was tight
 Implementation of android handset
The scope of the projects is to provide better assessment in editing purpose and the budget as
well as the scope was met. The employees were highly skilled.
Windows 3.0
Critical Risk
 Revamped User Interface
 Usage of list based file manager
Issue
 High system requirement
 Requirement of MS DOS version higher than 3.1
Challenge
 Installation of VGA drivers
 Alignment of memory modes
The budget that is stated was robust and the process was completed in the meantime.
World Wide Web
Critical Risk

7
AGILE METHOD ADOPTION
 Improper functioning of HTML
 Performing Linking
Issue
 Improper scheme specifiers
 Improper web server linking
Challenge
 Modelling SGML
 Signing off of SGML ISO
Budget was well maintained and the schedule was well maintained.
2000
PlayStation
Critical Risk
 Return of investment
 Acceptance of the product
Issue
 Cost of the product manufacturing was high
 Usage of Emotion engine for the first time
Challenge
 Providing dual shock handling

8
AGILE METHOD ADOPTION
 Creating lighter versions of the gaming console
There was an issue regarding the scheduling process and hence wise budgeting issue was also
present.
E-book
Critical Risk
 Acceptance of the book
 Excess dependency on internet
Issue
 Accessibility issue
 Direct competition with traditional books
Challenge
 Staying in the budget
 Increasing accessibility
Schedule and budget was well maintained. Employees were well trained as per the job roles.
Facebook launch
Critical Risk
 Data privacy risk
 Data base management system risk
Issue

9
AGILE METHOD ADOPTION
 Low resources
 Lack of personal privacy
Challenge
 Dependent on Internet
 Lack of accessibility
There was no schedule or budget present in case of Facebook development. Roles were not
properly aligned as well.
2010
Automated cars
Critical Risk
 Sensor functioning
 Decision making
Issue
 Excess cost incurred in manufacturing
 Requires proper scheduling and planning
Challenge
 Marketing of the product
 Acceptance of the product
Scheduling is performed in a proper manner and so is the budget.

10
AGILE METHOD ADOPTION
AI
Critical Risk
 Following the schedule
 Providing required data
Issue
 Lack of control in decision making
 Poor performance in decision making
Challenge
 Reliability on the technology
 Managing the resources
The budgeting and scheduling section is performed in a proper manner. Resources are highly
viable.
Machine learning
Critical Risk
 Excess data reception
 Improper data analysis
Issue
 Programmers have no control
 Resources need to be highly skilful

11
AGILE METHOD ADOPTION
Challenge
 Requires complex framework for implementation of machine learning In case of inaccurate data provisioning decision making gets affected
Scheduling of the project is highly affected. Programmers were highly efficient.

12
AGILE METHOD ADOPTION
References
Ahimbisibwe, A., Daellenbach, U., & Cavana, R. Y. (2017). Empirical comparison of traditional
plan-based and agile methodologies: Critical success factors for outsourced software
development projects from vendors’ perspective. Journal of Enterprise Information
Management, 30(3), 400-453.
Gandomani, T. J., & Nafchi, M. Z. (2016). The essential prerequisites of Agile transition and
adoption: A grounded theory approach. Journal of Internet Computing and Services
(JICS), 5, 173-183.
Papadopoulos, G. (2015). Moving from traditional to agile software development methodologies
also on large, distributed projects. Procedia-Social and Behavioral Sciences, 175, 455-
463.
Rigby, D. K., Sutherland, J., & Takeuchi, H. (2016). Embracing agile. Harvard Business
Review, 94(5), 40-50.
Vacari, I., & Prikladnicki, R. (2015). Adopting agile methods in the public sector: a systematic
literature review. In Embrapa Informática Agropecuária-Artigo em anais de congresso
(ALICE). In: INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING
AND KNOWLEDGE ENGINEERING, 27., 2015, Pittsburgh. Proceedings... Pittsburgh:
Pittsburgh University, 2015..