MITS5002 Presentation: Waterfall to Agile Transition Analysis

This presentation focuses on the complexities of transitioning from a Waterfall software development approach to Agile methodologies. It analyzes a selected academic paper that explores the role of stakeholders and the implementation of Agile principles. The presentation discusses the research methodology, which includes positivism, an exploratory design, secondary data collection, and a non-probabilistic sampling method. It highlights the importance of considering team needs and the crucial roles of Agile managers and Scrum masters in mitigating implementation challenges. The presentation emphasizes flexibility and provides insights for students on how to approach the transition from Waterfall to Agile. The presentation is a part of the MITS5002 course requirements.

Presentation on
Moving from Waterfall
to Agile

INTRODUCTION
The foremost
determination of this
presentation is to focus
on the complexities
faced by a software
development
organization when they
tries to change their
software development
approach from Waterfall
model to the Agile
Model [1].
This selected article is
directly related with the
risk analysis in software
engineering.

Selected
Article
The role of each of the stakeholders during this
organization change have been presented in the
paper [2]. Transformation from Waterfall to Agile
has been discussed week wise in the selected
article. The article highlighted the complexities
while transforming from one software development
approach to another.

Research Methodology of
the selected article
•Research Philosophy: Positivism
•Research design: Exploratory
•Data collection procedure:
Secondary
•Sampling method: Non-probabilistic
sampling method
•Data Analysis: Qualitative

Results and conclusion for the
Selected Article
The changing needs of the team should be given
priority considering the implementation plan. The
role of the Agile managers as well as the scrum
masters are very much important to mitigate the
complexities in the implementation procedure of
any software development approach. Flexibility

REFERENCE
[1] S. Komai, H. Nakanishi, and H. Saidi, H.Guidelines for
selecting agile development method in system
requirements definition. In 2017 7th IEEE International
Conference on Control System, Computing and
Engineering (ICCSCE) (pp. 49-53). IEEE, 2017
[2] W. Alsaqaf, M. Daneva and R. Wieringa.
Understanding challenging situations in agile quality
requirements engineering and their solution strategies:
insights from a case study. In 2018 IEEE 26th
International Requirements Engineering Conference (RE)
(pp. 274-285). IEEE, 2018