MITS5002: Moving from Waterfall to Agile Software Development

This report provides a critical analysis of a peer-reviewed journal article focusing on the transition from the Waterfall to Agile software development methodology, using a case study of Wipro Technologies. The paper examines the issues faced by the organization during the transformation, including delays, overworking, and the need for test-driven development. The report details the research methodology, including positivism and exploratory research design, and the use of secondary and qualitative data analysis. It highlights the findings, such as the importance of Agile coaches and the need to measure software development procedures. Key issues highlighted are late integration, insufficient analysis, and omissions in the project. The report concludes by emphasizing the importance of tracking the changing needs of the team, the role of Agile coaches, and the relevance of the article to risk analysis in software engineering, making it a valuable resource for students on Desklib.

Running head: MOVING FROM WATERFALL TO AGILE
Moving from Waterfall to Agile
Name of the Student
Name of the University
Author Note

MOVING FROM WATERFALL TO AGILE
Table of Contents
Introduction................................................................................................................................3
Statement of purpose..............................................................................................................3
Structure of the paper.............................................................................................................3
Intention and content of the article.............................................................................................4
Research method of the article...................................................................................................4
Research Philosophy..............................................................................................................4
Research design......................................................................................................................4
Data Collection.......................................................................................................................5
Sampling method...................................................................................................................5
Data Analysis.........................................................................................................................5
Findings of the article.................................................................................................................5
Issues highlighted in the article..................................................................................................6
Conclusion..................................................................................................................................6
LAPTOP_MP0240 1
Name of the student:
Student ID:

MOVING FROM WATERFALL TO AGILE
Introduction
The principal purpose of this document is to focus on the critical analysis of a peer-
reviewed journal related to software engineering. The selected paper helps in identifying the
issues in a crisis ridden business environment which has resulted in the transformation in
their working procedures [3]. The paper explains the transformation from waterfall to agile in
an organized manner. The needs and requirements of the consumers of software development
organization keep on changing every moment, in a specific project in Wipro technologies
where an existing system was supposed to be enhanced using C and C++ there were several
issues such as delay, overworking for the employee to meet the deadlines, delay in testing as
well as in development [4]. This software development organization was not wanting to adopt
the test driven documentation to resolve these issues. Thus, the organization wanted to switch
from waterfall software development methodology to Agile software development
methodology [8]. The deliverables of each of the transformational week has been presented in
the paper in chronological order. The following unit of the paper will be discussing the
statement of purpose off the report.
Statement of purpose
The foremost determination of this paper is to evaluate and analysis the paper which
is selected for this assignment. The structure of the report will be discussed in brief in the
subsequent unit of the report. The subsequent unit of the report will be the structure of the
paper.
Structure of the paper
The importance of the content and the intention of the selected article will be
presented in the paper along with the research methodology. The issues highlighted by the
researchers of the paper will also be discussed in this paper [5]. The paper will also evaluated
the conclusions or the findings of the selected article and will be justifying how the selected
article is relevant to project management methodologies of software engineering. The content
and the intent of the article will be selected in the next chapter of this report. The resulting
division of the paper will be conferring the intention and the content of the selected article.
LAPTOP_MP0240 2
Name of the student:
Student ID:

MOVING FROM WATERFALL TO AGILE
Intention and content of the article
The most striking specification of the selected article is to present the transformation
from Waterfall to Agile software development methodology [9]. Complexities and the role of
each of the stakeholders associated with the project has been identified in the article week
wise. The subsequent component of the report will be discoursing the research methodology
of the selected paper.
Research method of the article
Research Philosophy
The research philosophy which was selected in this article was positivism. The
positivism research philosophy will be very much important to investigate the topic in a
logical manner. The in-depth analysis of the topic is possible with the help of this research
philosophy. Existing project management theories have been successfully incorporated into
this research philosophy. Properties and relations of each of the subject have been presented
in the article in an organised manner.
Research design
The research design which was followed in this article is the exploratory research
design as it explores the possible of making significant progress if the software development
methodology is changed from Waterfall model to the Agile model. Detailed idea about Agile
software development approach was obtained from the paper as the result of this research
design.
Data Collection
The data collection method which was chosen in the selected article is secondary data
collection. Data has been collected from reliable and peer-reviewed sources which helps in
maintaining the efficiency of the paper. Data was collected from online platforms and other
printed documents.
Sampling method
The sampling method which was selected in the article is non-probabilistic sampling
method as there are no numerical values and calculations associated with the secondary data
collection procedure.
LAPTOP_MP0240 3
Name of the student:
Student ID:

MOVING FROM WATERFALL TO AGILE
Data Analysis
The secondary data which was considered in the paper was analysed with the
help of the qualitative data analysis. Thematic approach was undertaken during the data
analysis of this paper. At the same time, it can also be said that the data analysis of the paper
has been done in a professional manner which is very much important for the readers as it
improves the transparency of the findings of the paper. The next entity of the report will be
deliberating the findings of the selected article.
Findings of the article
The article is very much important to understand the complexities faced by a
software development organization such as Wipro Technologies as they wanted to modify
their software development approach from Waterfall to Agile. The importance of an Agile
coach was found from the paper, at the same time it can also be said that the paper was very
much helpful to understand the complex implementation procedure of a continuous change
[7]. Business situations are needed to be handed in a diplomatic manner as well. The data
required in the iteration process has to be calculated in the first place in order to resolve the
issue of project scheduling. Changing the mind-set of the project manager are essential for
any kinds of transformation as mentioned by the researcher [10]. The measurements of the
software development procedures have to be measured carefully in order to manage the
complexities in the software development as well as software testing phase. Practical
demonstration of the problems by the project manages could have eased the situation where
there is an argument between the developers and the project managers. The researcher of the
paper successfully mentioned about the role of the scrum masters in this particular scenario
when an organization is switching from Waterfall to Agile. Along with that it can also be said
that the agile managers can have huge role to deal with the complexities of the traditional
software development approaches [2]. Thus, the article is very much beneficial for the
readers of this document to understand the importance which is needed to be given to the
changing needs of the software development team, rather than have a preconceived plan
which is usually selected in the agile projects.
Issues highlighted in the article
The prime issue which were highlighted in the selected article is late integration for
the team members of the project. The researchers of the paper stated that the complexities in
LAPTOP_MP0240 4
Name of the student:
Student ID:

MOVING FROM WATERFALL TO AGILE
development and designing could have been easily resolved with the help of the Test Driven
Approaches [11]. Insufficient analyses in each week have opted the programmers to follow
partial par programming which is a significant concern which was highlighted in the article.
The identification of the dependencies in the early stages could have been much easier to deal
with the complexities of this transformation as stated by the researcher [6]. The other issues
which were highlighted in this article is the identification of the omissions of the project. The
next chapter of the paper will be reflecting the results of the selected article.
Discussion of the results
The paper discusses the importance of choosing the measurements required to change
software development methodology. The role of the Agile coaches can be determined from
the paper as well [1]. The role of the experienced project managers can be understood from
the paper as well as they are very much capable of dealing with the complexities of the Agile
approach.
Conclusion of the article
The selected article concludes that the changing needs of the tram should be tracked in the
first place so that Agile can be successfully implemented in software development
organization such as Wipro Technologies. The paper also identifies that the transformation
must be done in a professional manner keeping in mind with the conventional software
development practices. The paper also accepts the need of having employees with a flexible
approach so that they can yield better products for the consumers of the organization.
Relevance of the article
The selected article is very much important to understand the different procedure to
analysis the risk of transformation from one software management approach to another [12].
The paper was also very much important to understand the challenges of an organizational
change. Thus, the paper is very much important to understand software engineering
methodologies in a professional manner.
Conclusion
The paper is very much important to understand the concept of risk analysis in
software engineering with the help of an article. The selected papers help in identifying the
challenges faced when software development organizations such as Wipro technologies
LAPTOP_MP0240 5
Name of the student:
Student ID:

MOVING FROM WATERFALL TO AGILE
changes or updates their existing software development approach from Waterfall to Agile.
The paper determines that the role of the Agile coaches and the scrum master are very much
important regarding the implementation as well as the functionality of the Agile project
management methodology.
The research methodology of the paper helps in understanding that the article is very
much reliable in nature and can contribute hugely in future projects as well. The issues of the
article, discussions of the result and justification behind selected the article can also be
understood from this paper. Thus, this paper can be very much beneficial for readers to
understand the risk analysis in software engineering.
LAPTOP_MP0240 6
Name of the student:
Student ID:

MOVING FROM WATERFALL TO AGILE
Reference
[1] A.M. Dima, and M.A. Maassen, M.A.From Waterfall to Agile software: Development
models in the IT sector, 2006 to 2018. Impacts on company management. Journal of
International Studies, 11(2), pp.315-326, 2018
[2] A.P Veiga. Project Success in Agile Development Projects. arXiv preprint
arXiv:1711.06851, 2017
[3] B. Rajput. Software Quality Assurance Using Agile Software Methodology in Education
Assessment Industry, 2016
[4] E.T Pool, K. Poole, D.P Upjohn, and J.S. Hernandez. ‘AGILE’HELPING MAYO
IMPROVE ITS PROJECTS. Physician Leadership Journal, 6(2), 2019
[5] F. Almeida, and J. Simões. Moving from Waterfall to Agile: Perspectives from IT
Portuguese Companies. International Journal of Service Science, Management, Engineering,
and Technology (IJSSMET), 10(1), pp.30-43., 2019
[6] G.L. Johnson. The Causal Effects of Cost, Schedule, and Quality on the Development of
Geospatial Technology Using Waterfall and Agile Scrum Software Development Methods
(Doctoral dissertation, The George Washington University), 2018.
[7] K. Dikert, M. Paasivaara, and C. Lassenius. Challenges and success factors for large-
scale agile transformations: A systematic literature review. Journal of Systems and Software,
119, pp.87-108, 2016
[8] K. Sureshchandra, and J. Shrinivasavadhani. Moving from waterfall to agile. In Agile
2008 conference (pp. 97-101). IEEE, 2008
[9] L. Mahadevan, W.J. Kettinger, and T.O. Meservy. Running on Hybrid: Control Changes
when Introducing an Agile Methodology in a Traditional" Waterfall" System Development
Environment. CAIS, 36, p.5, 215
[10] M. Ajam. Project Management Beyond Waterfall and Agile. Auerbach Publications,
2018
M. Säisä, K. Tiura, and J. Roslöf. Waterfall vs. agile project management methods in
university-industry collaboration projects, 2018
LAPTOP_MP0240 7
Name of the student:
Student ID:

MOVING FROM WATERFALL TO AGILE
[11] M.K Lal, M.K. Knowledge Driven Development: Bridging Waterfall and Agile
Methodologies. Cambridge University Press, 2018
[12] R. Elghondakly, S. Moussa, and N. Badr. Waterfall and agile requirements-based model
for automated test cases generation. In 2015 IEEE Seventh International Conference on
Intelligent Computing and Information Systems (ICICIS) (pp. 607-612). IEEE, 2015
LAPTOP_MP0240 8
Name of the student:
Student ID: