Introduction to Scrum
Scrum is the most widely used Agile methodology around the world. Scrum focuses more on project management level for prioritization of work and getting feedback. Scrum is based on three pillars; visibility, inspection and adaptation. The Scrum methodology mainly consists of sprints which range from 1 to 4 weeks each and consists of product backlog which lists down all the customer requirements in the form of user stories.
Scrum methodology has 3 main roles; Product owner (the one who owns the backlog), The Team (which will be working on the development of the product) and the Scrum Master (who can be termed as a project manager).
Scrum consists of some of the important components which encapsulate the Scrum methodology:
Sprint Planning Meeting
Sprint planning meeting is conducted on the very first day of the sprint and consists of two halves of 4 hour each. First half is conducted by Product Owner in the presence of the team. The Product Owner, who has already arranged the backlog according to priority, describes User Stories from the top of the list, and the team after discussing selects the User Stories for the sprint.
Second half of the meeting is conducted by Scrum Master. All the selected User stories comprise of the Sprint Backlog and the team creates tasks for each of these.
The daily scrum is a 15 minute stand-up meeting of the team members conducted by Scrum Master. Each member of the team turn-by-turn answers 3 questions:
- What did you do since the last meeting?
- What are you planning to do?
- What issues are you facing?
The daily scrum helps the team to be on the same page and helps the team deal with any issues they may be facing.
The Sprint Review is a 4 hour meeting conducted at the end of the Sprint with the team and the Product owner. The main aim of this meeting is to share and show the Product Owner new functionalities developed and discuss potential new features for next sprint.
It is a meeting conducted by the Scrum Master with the team at the end of the Sprint and start of new Sprint. The Product Owner does not participate in this exercise. It is a meeting where the team analyzes 3 aspects for current and next Sprints:
- What went right? (Continue)
- What went wrong? (Change or Stop)
- What can be done new? (Experiments and Additions)
Disclaimer: The views expressed here are solely those of the author in his private capacity and do not in any way represent the views of Systems Limited, or any other entity related to Systems Limited.