Information System Design: Agile SDLC Model and Iterative Process

This journal assignment reflects on the implementation of the Agile Software Development Life Cycle (SDLC) model within a fictitious organization, emphasizing the iterative and incremental nature of the methodology. The author agrees with the feedback received, highlighting Agile's adaptive approach and its focus on incorporating stakeholder feedback at each iteration. Key aspects discussed include the creation of a product backlog to manage evolving requirements, the development of sprint backlogs for task management within Scrum sprints, and the importance of sprint planning for effective execution. The ultimate goal is to demonstrate a high-quality product that aligns with stakeholder needs through iterative development and continuous feedback integration. The document concludes by emphasizing product demonstration and planning for subsequent iterative phases to ensure an effective SDLC.

Running head: INFORMATION SYSTEM DESIGN
Information System Design
Name of the Student:
Name of the University:
Author note

1INFORMATION SYSTEM DESIGN
The feedback received for the Software Life Cycle Model (SDLC) to be used was the
Agile Model. I agree with the above feedback as it is a better methodology. It is a
combination of two processes namely the iterative model and the incremental model (Rani,
2017). The model is broken down into small incremental parts and iteratively built. In the
Agile model the entire task is divided into small time frames and at the completion of each
iteration the product developed is presented to the stakeholders for their respective feedback.
I will be implementing this methodology in consultation with a fictitious organization such
that the requirement of the stakeholders will be more understandable to me. The feedbacks of
the stakeholders will also be implemented by me.
The Agile methodology is an adaptive approach incorporating no detailed planning
and the requirement becomes more vivid in consideration to what features more are required
by the stakeholders after the first and second week of the development of the product. I will
try to implement the Agile SDLC model as it provides high quality products as it is a realistic
approach to the software development. I will also try to implement all the aspects of the life
cycle methodology. The stages of life cycle planning include selection of the project initially
then the development phase starts which is done in various iterations. Then the various stages
for each iteration begins which includes planning of the work to be done in each step, then
the requirement analysis is done, the third step includes the designing of the product. After
the designing phase the building phase process starts in which the designed product is built
and then the testing of the product is done (Kazim, 2017). After the completion of the
iteration the product developed will be shown to the stakeholders such that any requirement
of the stakeholders that was not implemented earlier would be represented.
Then after, the process for the next iteration is repeated and this continues till the
entire product is developed. However, for the proper development of the product as per the
feedbacks, my prime objective is to create a product backlog. The product backlog contains

2INFORMATION SYSTEM DESIGN
the entire information that would be required in the product (Alsalemi & Yeoh, 2015). It is an
ordered list and acts as a single source of information of any alterations in the product as the
requirement constantly keeps on changing. Then I will create a sprint backlog in which a
catalogue of errands should be accomplished within the Scrum sprint as stated down by the
Scrum team (Lei et al., 2017). Then after, a sprint planning will be done. Thus, after the
completion of the objectives I will execute the work in the manner as decided in the sprint
meeting so as to gain positive response in my work. Finally, I will be giving the product
demonstration and plan for the next iterative phase in a procedure to execute an effective
SDLC.

3INFORMATION SYSTEM DESIGN
References:
Alsalemi, A. M., & Yeoh, E. T. (2015, December). A survey on product backlog change
management and requirement traceability in agile (Scrum). In Software Engineering
Conference (MySEC), 2015 9th Malaysian (pp. 189-194). IEEE.
Kazim, A. (2017). A Study of Software Development Life Cycle Process
Models. International Journal of Advanced Research in Computer Science, 8(1).
Lei, H., Ganjeizadeh, F., Jayachandran, P. K., & Ozcan, P. (2017). A statistical analysis of
the effects of Scrum and Kanban on software development projects. Robotics and
Computer-Integrated Manufacturing, 43, 59-67.
Rani, S. B. A. S. U. (2017). A detailed study of Software Development Life Cycle (SDLC)
Models. International Journal Of Engineering And Computer Science, 6(7).