Scrum Methodology 
                     
Scrum is an incremental, iterative, and one of the widely 
used agile frameworks which emphasize a cross-functional 
team frequently delivering a meaningful shippable product 
in a short duration of time. Scrum Methodology works by 
breaking a large product/project into smaller deliveries. By 
doing this scrum promotes faster feedback, incremental 
product delivery, faster time to market, and better visibility 
of the product.
Scrum teams plan a delivery based on business priorities 
and needs, develop them over a fixed timeframe and deliver 
it. And this continues till the entire backlog is delivered.
Benefits of Scrum Methodology: With frequent 
delivery based on priority and feedback, Scrum 
methodology achieved high alignment of business with 
IT, adapting to business changes, early risk 
identification, and reduction of waste. Scrum makes 
businesses innovate faster, convert ideas to deliver 
quickly, and drive higher customer satisfaction. Scrum 
also promotes key business driving factors like 
Predictability, Transparency, Visibility, and Quality.
Sprint and Duration: A key decision to take when 
Scrum methodology is adopted, is to identify and fix 
the duration of an iteration. An iteration is called 
SPRINT. Sprint duration is decided based on :
1. Number of feedback needed — Shorter the 
duration of the sprint, more is the number of 
feedback the team can get
2. Requirement Certainty — If the requirements are 
uncertain, shorter sprints help in less wastage of work
3. Team’s confidence in delivering a meaningful 
outcome — If the team is confident in delivering a 
meaningful outcome ( Shippable product ) in two 
weeks, the sprint duration should be two weeks
Roles Of Scrum: An ideal Scrum team consists of 3 
roles, “Product Owner” — who is the visionary of the 
product, sets priorities, owns the backlog, “Scrum 
Master” — who maintains agile mindset within the 
team, facilitated the ceremonies and helps team 
resolve impediments, “Development Team’’ — which 
is cross-functional and are the actual 
doers/developers.
Scrum Ceremonies: As per the Scrum guide, there are three 
ceremonies any scrum team should follow and one optional 
ceremony.
● Sprint Planning — Happens on Day one of the sprintss 
with the intention to plan the iteration deliverables. PO sets 
the priorities and goals based on the business needs, the 
development team estimates the work items and discusses the 
work items in detail. At the end of the ceremony, a sprint 
backlog is created and agreed upon
● Daily Scrum Meeting: Happens every day at the same 
time in the same place for not more than 15 minutes. The 
intention is to check the sprint progress and the team’s 
confidence in achieving the sprint goal.
● Sprint Grooming / Backlog Grooming: An optional 
ceremony that is done in the middle of every sprint. The 
intention is to understand what is coming up in the next sprint 
at a high level and to highlight dependencies/blockers to be 
resolved before starting the next sprint.
● Sprint Review / Demo: Happens on the last day of the 
sprint. The intention is for the development team to demo 
the work items planned or showcase a working software 
and to collect feedback on the work completed
● Sprint Retrospection: This happens after the Sprint 
Review on the last day. The purpose is for the team to 
identify ways to improve themselves, process and 
tools/artefacts
Scrum Artifacts and Reports: Some of the commonly used 
reports and artefacts in Scrum methodology are,
● Product Backlog — A unidirectional list of prioritised work to be 
done by the development team.
● Sprint Backlog — A part of the product backlog planned by the 
development team in an iteration to achieve a goal.
● Burndown Chart — A report that helps the team to visualise their 
progress during the sprint. Also helps in predicting sprint level 
failures
● Velocity Chart — A report which helps in understanding the 
team’s average capacity of doneness of work. Helps in predicting 
the team’s ability to complete the backlog
● Cumulative Flow Diagram — A report to visualise the workflow 
across the project/sprint.
● Control Chart — A report to understand the team’s average cycle 
time and its trend
● Release burndown chart — A report to visualise the work done in 
a particular release. Also helps predict the milestone completion 
based on the team’s current capacity.
For more insights on 
Scrum and Agile, check 
our website 
www.benzne.com