Scrum has been used by many big companies like Microsoft, yahoo, Google, IBM etc. and for various purposes including commercial software, in-house development, contract development and even non-software projects The Scrum methodology involves self-organizing teams, series of typically two-week timespans known as “sprints”. The items to be completed are listed in the “Product Backlog”, compiled from captured.
Implementation of Agile (Scrum) Software Development Methodology
The implementation process of Scrum’s methodology can easily be explained with the help of the Scrum Framework. The framework is divided into three parts i.e. roles, ceremonies, and Artifacts.
Three defined roles are a part of the Scrum methodology. These are:
The features of the product are defined by the product owner. The product owner makes the decisions on scope and schedule, achieving financial goals of the project is the responsibility of the product owner, product backlog is prioritized by the Product Owner, based on need the product owner adjusts features and priority every sprint, and work results are accepted or rejected by him.
The Scrum Master
The Scrum Master the owns the process and can make adjustments to it. He also facilitates ceremonies. This does not make him/her a technical lead or manager. They are also responsible for Scrum values and practices and to help removes impediments, improve team productivity, enables close cooperation across all roles and functions and shields the team from external interference.
The team typically consists of five to nine people. Consisting of programmers, testers, and business analysis (for software projects). The teams are self-organizing and the membership should only change between sprints.
Ceremonies are the processes involved in the implementation of the Agile (Scrum) software development methodology and including the following:
The sprint planning meeting consists of team, the Scrum master, and the product owner. In the meeting, the product backlog items are discussed so that they can be prioritized and then the team selects which ones to do. The sprint planning meeting determines what will be worked on and it also helps to develop a considerable understanding of what needs to do in order carry it out. One notable thing done in sprint planning is that tasks are measured in time (whereas before it was done in story points).
A rule of thumb, a sprint planning takes approximately Number of weeks in sprint * 2 hours (4 hours in our case)
The daily Scrum meeting is held daily for about 15 minutes .This is not a problem-solving meeting. The daily Scrum helps avoid unnecessary meetings. In the daily Scrum everyone answers three questions, the questions are:
- What did you do yesterday?
- What will you do today?
- Is anything in your way?
The Sprint Review
In the Sprint Review (can also be referred to a Review & Demo) the team presents what has been accomplished during the sprint. It is a demonstration of new features or the existing architecture. It is an informal presentation and the entire team participates in it.
It involves looking at what is working and what is not. The time period for the sprint retrospective is around thirty minutes and is done after every sprint. It involves the participation of the product owner, Scrum master, team and even the customers. In the retrospective, the whole team gathers to discuss what they want to start, continue or stop doing.
The artifacts can be called the tools of the Scrum methodology and include the following:
The product backlog captures the requirements listed as items or work on the project. Each item is expressed in a way which provides value to the customer, prioritized by the product owner and reprioritized at the start of each sprint.