Scrum Explained
Scrum is an iterative method of managing software development projects It was developed in 1993 by Jeff Sutherland. It has since become one of the leading agile development methodologies and is used worldwide by many Fortune 500 companies. The Scrum process is an incremental series of steps that help ensure projects are completed on time and within budget, without sacrificing product quality.
Other People Are Reading
-
The Roles
-
According to the Scrum Alliance, three roles are pivotal when using the Scrum methodology. First, the product owner must describe the desired product, determine its release date and approve or reject all prototypes created during the projects. The Scrum master oversees the project, hosting daily meetings to ensure that developers remain productive. Finally, the team is responsible for adhering to the product specifications while communicating and maintaining daily goals and providing product demos to the owner.
Sprints
-
Work cycles in the Scrum methodology are referred to as sprints and every sprint consists of several iterations. Sprints can range from two weeks to 30 days, but a finished product is always expected at the end of each sprint. According to Scrum methodology, every sprint begins with a planning meeting and concludes with a review meeting, during which time the product owner determines if all product criteria has been met. If a sprint has produced an acceptable product the same processes can be repeated in the next sprint.
-
Meetings
-
Daily meetings are held during projects that use the Scrum methodology, which emphasizes communication and collaboration. These meetings are helpful in keeping all members of the product development team focused on the most important project goals during the sprint. Meetings also help team members discover and rectify development problems quickly. At the end of the sprint, a retrospective meeting is held to determine what procedures worked best and how productivity might be improved during the next sprint.
Burndown charts
-
Burndown charts are used during a Scrum project to track progress, allowing team members to view daily accomplishments and setbacks. The horizontal axis on a burndown chart represents each sprint and the vertical axis represents the work remaining. The final burndown chart should show a line that has trended downward from left to right during the project. Burndown charts can also be created to show monthly progress. which would include a number of sprints.
Expert Insight
-
Mike Cohn, founder of agile methodology training and project management consulting firm Mountain Goat Software, says a good Scrum master is responsible, humble, collaborative, committed influential and knowledgeable. He likens the role of Scrum master to that of an orchestra conductor, as "both must provide real-time guidance and leadership to a talented collection of individuals who come together to create something that no one of them could create alone."
-
