What is SCRUM ?
Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems. This tutorial can help you to understand the SCRUM basics.
Scrum is not a methodology. It implements the scientific method of empiricism. Scrum replaces a programmed algorithmic approach with a heuristic one, with respect for people and self-organization to solve complex problems (especially for IT projects).
Scrum is a project management process that enables a team to communicate and self-organize to make changes quickly, following agile principles. It generally requires 3 elements :
- Roles : Product owner, Scrum master, Developpers
- Events : Sprint planning, Sprints, Daily scrums, Sprint reviews, Sprint retrospectives
- Artefacts : Product backlog, Sprint backlog, Product increment.
Product Owner : is responsible for the project’s outcome (the person requesting the work). The product owner seeks to maximize a product’s value by managing and optimizing the product backlog.
Scrum Master : is a facilitator for an Agile development team. They are responsible for managing the exchange of information between team members.
Development Team : is a group of developers and professionals responsible for creating the project deliverables, together with the rest of the Scrum team
The below graphic represents Scrum in action where the Scrum Master has to foster the environment :
- First of all, the Product Owner orders the work for a complex problem into a Product Backlog.
- The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
- The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
- Repeat
Sprint : in which the product owner and the development team agree upon exactly what work will be accomplished during the sprint. The sprint is generally the time frame in which the work must be completed — often 30 days. During a sprint, work is done to create new features based on the user stories (set of tasks ) and backlog. A new sprint starts immediately after the current sprint ends.
Sprint Planning : is an event that establishes the product development goal and plan for the upcoming sprint, based on the team’s review of its product backlog.
Daily Scrum : is a 15-minute time-boxed event for the developpers to synchronize activities and create a plan for the next 24 hours.
Scrum Review : is one of the most important ceremonies in Scrum where the team gathers to review completed work and determine whether additional changes are needed.
Scrum Retrospective : a timeboxed meeting that takes place after the sprint review and before sprint planning. Its purpose is to: Examine how the just-completed sprint went as far as people, relationships, processes, and tools. Identify and order what went well.
Product Backlog : is an ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.
Sprint Backlog : is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the current sprint.
Product increment : The Product Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be “Done,” which means it must be in useable condition and meet the Scrum Team’s definition of “Done”.
Today’s marketplace offers a multitude of scrum productivity tools. Each is designed to help product development teams follow the scrum/sprint methodology efficiently and accurately.
Popular scrum tools include : Jira, nTask, QuickScrum, ScrumDo, Scrumwise, Vivify Scrum, Ora
It was a step-by-step guide to understand how the scrum process works
Thanks for reading ❤
