SCRUM Methodology

Scrum methodology is mainly used in project management and in agile software development. Scrum methodology is iterative; the software product is developed in small iterations called sprints. Also, scrum is incremental; the functionality of the product increases during each iteration by adding new properties. We can identify scrum as a framework than considering it as a methodology because in the scrum it doesn’t tell us what to do. Instead, it exposes the weaknesses and failures in how we’re doing it.

Image from https://www.apeironsoftware.com/scrum-roles-artifacts-and-ceremonies/ 

 

Little History on Scrum

Scrum is a methodology which was gradually evolved. It was inspired by two people called Hirotaka Takeuchi and IKujiro Nonaka. In 1991 a person called DeGrace referred to this approach as Scrum in “Wicked Problems, Righteous Solutions”. In 1995 Jeff Sutherland and Ken Schwaber analyzed common software development processes and as a result, they proposed Scrum. Introduction to Scrum in OOPSLA happened in 1995. Finally, Scrum publicly appeared in 2001. Two people called Ken Schawaber and Mike Beedle Jointly presented a paper about Scrum namely “Agile Software Development with Scrum”

Scrum is basically based on something called sprint which is a 30 day period of time towards a particular goal. 

Main Roles of SCRUM

There are three main roles in SCRUM

• ScrumMaster
• Product Owner
• Team

ScrumMaster: The ScrumMaster acts as a coach or a great keeper of the team. He or she works to remove any impediments that are obstructing the team from achieving its sprint goals. The ScrumMaster is the one who maintains rules inside the team. His main responsibility is to make team members focus on the work that they are doing.

Product Owner: He is the person who specifies requirements for a given project. Monitor the Scrum team whether the team achieves the goal or not.

Scrum Team: A team can have 5 to 9 members. All the team members should have experience in almost all areas in the software development Life Cycle. All of them have a joint responsibility to deliver the product on time. Each member is not given a specific task. Instead, they can swap tasks among them as they wish.

Stakeholders: Represents the customers and vendors. They are the people who initiate project, monitor it and justify the outcome whether they are correct or wrong.

Managers: Set up the environment for product development organizations.