IS Methodologies

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

IS methodologies

1.1.1. SCRUM Methodology


Scrum is one of the methodologies of IS development which is an iterative and
incremental-based process. This agile framework is flexible, adaptive and is designed
to come out with a user’s-based system. This methodology enables customers and
stakeholders to come up with their requirements for a business system and prepare a
system requirement document as their preferred requirement. This methodology
begins with collecting business requirements of the system from users and
stakeholders and then prioritizing the fundamental requirement as the product owner
wants to acquire (Rubin, 2012).
Key concepts of Scrum Methodology:
(i) User Stories

At the first step, the system users, developer, stakeholder, and company executive
come up with general ideas of system requirements. They set their requirement as
their needs and understanding. This is an important stage since the product owner can
get the perspective of the customer and what would they like to prefer in the system or
business process.
(ii) Product Owner

Once the requirement from all the users, developers, and stakeholders are analyzed,
the product owner verifies, whether all the system requirements are mentioned or not,
whether there are some missing or unwanted requirements. Therefore, reviewing the
requirement the product owner comes up with the final requirement for the system,
preferring the customers, developer’s requirement, and some additional requirements
(if needed) as well.
(iii) Development Teams

After finalizing the requirements, the product owner assigns a system development
team to turn these system requirements into their system or business process. A
development team that contains individuals of different skills like programming,
database management, User interface, research analyst, and leadership come up
together to make a well-functioning term which can work together, implementing
their respective skills to make a functional system as of the product owner’s
requirement.

(iv) Scrum Master

The scrum master is one, who is the leader of the system development group and
takes the responsibility to handle overall problems and gaps that occurred during the
developmental process using agile methodology. Scrum Master is also responsible for
giving ideas and solving the problem that occurred during the developmental phase
(Watts, 2021).
(v) Sprint

Sprint in scrum is a cycle of tasks, in which the assigned task is to be completed in a


certain time frame. In this process, the whole developmental process is split into
different sub-tasks and the development team takes the challenge to complete these
sub-tasks in a certain period.
(vi) Backlogs

Backlogs in scrum methodology is a list of fundamental requirements or sub-tasks


that need to be completed to complete the system development project, delivering a
functional and business-oriented system.

You might also like