What exactly is Scrum ?
Scrum is a framework that will assist you in delivering your product in a creative and productive manner. Scrum is a framework, not a technique or process. Scrum aids in the implementation of Agile methodologies.
Scrum is made up of roles, events, artifacts, and rules, each with its own purpose.
To better understand this blog, please read my prior blog about agile 👇
Sprint
Scrum is built around Sprints. Sprint is a time-boxed event (with a maximum duration specified) that generally lasts two to four weeks. During the Sprint, developers create incremental versions of the products.
Sprint Planning is the first step in the process, during which the team determines what to work on. Every day, there is a Scrum Meeting, a quick 15-minute meeting that helps everyone coordinate activities and prepare for the day. The Sprint Review is completed at the conclusion of the Sprint to inspect the increment that was developed. The Sprint comes to a close with a Sprint Retrospective, in which the team assesses itself and looks for ways to improve. If you don’t comprehend this jargon, don’t worry. They’ll be discussed in more detail in the next section.
Roles
Scrum Master, Scrum Team, and Product Owner are the roles involved in Scrum.
Product Owner is the only person in charge of the Product Backlogs. The product/problem into smaller parts called the Product Backlogs. This is done by the Product Owner, who organizes them by priority and importance. He or she could enlist the help of the Scrum Master or the Scrum team. He also ensures that Product Backlogs are transparent and easy to understand.
Scrum Master is the custodian of Scrum. He ensures that Scrum is properly comprehended and practiced. He’s in charge of the Daily Scrum Meetings. He finds and removes roadblocks in the development process. He aids the team’s ability to self-organize.
Scrum Team is a cross-functional team of developers, testers, designers, analysts. The ideal team size is between 5 and 9 people. The Scrum team is a self-organizing group that provides product gradually and iteratively, allowing for the most amount of input possible.
Events
Scrum is a set of activities that comprise Sprint Planning, Daily Scrum Meetings, Sprint Review, and Sprint Retrospective.
Sprint Planning takes place prior to the start of the Sprint. The Sprint Backlogs are chosen by the team from the Product Backlogs. The Sprint Backlogs are then created from these backlogs. The Sprint Goal is the goal that tells the team why they’re creating increment in the first place.
Daily Scrum Meetings are 15-minute meetings that take place every day. The Scrum Master is generally the one to felicitates it. The team members keep each other up to date, ensuring that everyone is on the same page. They also devise a plan for the day.
Sprint Review is a meeting held at the conclusion of a Sprint. Team reviews the increment they developed in the current Sprint during the Sprint Review. The Scrum Team, as well as the stakeholders, participate in the Sprint Review. The participants’ feedback on the new increment is gathered. Sprint Review offers useful information for the next Sprint Planning.
Sprint Retrospective occurs after Sprint Review and before the following Sprint Planning. The team examines what went well and what didn’t, as well as how certain situations may have been handled more effectively. Sprint Retrospective collects improvements and lessons learned.
Artifacts
Scrum Artifacts are documents that detail the product development process, including the steps done and the activities planned. Product Backlog, Sprint Backlog, Burn-Down Chart, and Increment are all part of this.
Product Backlog is an organized list of features that must be included in the final product. It is the only place where you may get all the requirements. User Stories are the common name for these things. These have description, order, estimate, and value characteristics.
Sprint Backlog are a subset of the Product Backlog that have been chosen for the Sprint, plus Sprint Plan, and Sprint Goal. The Sprint Backlogs outline the additional features that will be added to the increments developed during the Sprint.
Increment is the total of all Product Backlogs completed in prior Sprints. The new increment must be a fully functional product that is superior to the prior one.
Burn-Down Chart displays the amount of work remaining for each Daily Scrum in order to forecast the chances of meeting the Sprint Goal. This is helpful for keeping track of development.
Evaluation
You have a good understanding of Scrum if you can grasp the following memes.
