"Humans are not ideally set up to understand logic; they are ideally set up to understand stories."
- Roger C. Schank
Scrum is one of the frameworks that disrupted the software development industry. Today, it is the most used Agile framework to manage the development of software products but can be applied to pretty much any project. It became popular because of its simplicity with fast and timeboxed iterations as well as active collaboration between the Teams, the Customers and the Stakeholders.
Scrum is operated based on three roles :
The Product Owner:
The PO is the member who understands the product, the business, and the market requirements. They are responsible for building and maintaining the Product Backlog containing user stories, prioritizing them and make sure the product deliverables match the customer needs. The PO also has to make sure that work items are clear for everyone.
The Scrum Master:
The Scrum Master educates the Team, the PO as well as the Business on Scrum processes. They are responsible for managing the smooth workflow and for scheduling the resources needed for the successful completion of each task.
The Scrum (or Development) Team:
The team usually consist of developers, designers, and testers. The Scrum Team has a common goal and is expected to be collaborative and support each other to be successful. They work towards delivering a working product at the end of each sprint. Teams of 5 to 8 members have proven to be the most efficient.
In Scrum, the features contained in the product backlog are defined as user stories. Basically, it tells what the user needs by telling a story which makes the feature easily understandable by everyone.
Scrum determines fixed length iterations in which new features will be developed. These iterations are called sprints that typically last between 1 and 4 weeks.
Sprint Planning Meeting
Every Sprint begins with a Sprint Planning Meeting in which:
1. Features from the Product Backlog will be selected for this specific sprint.
2. The team will discuss and communicate about the scope, the completion targets and the definition of done.
3. Priorities on the Backlog items (known as user stories) can be attributed and modified.
Daily Scrum Meetings
This framework contains a short 15-minute daily meeting, known as daily scrum or daily stand-up with the attendance of all members of the team to discuss what activities, plan the workday, track progress as well as removing the roadblocks of the project.
The team organizes a Retrospective meeting at the end of every sprint in order to showcase the completed work items but most importantly to discuss and analyze the success points in the sprint as well as the improvements to be made for the next sprint.
Once the sprint is over, the cycle repeats for the remaining user stories in the Product Backlog.