Scrum Methodology

What is Scrum?

• Scrum is framework derived from agile

• Scrum encourage team to learn through experience ,self-
organized while working on a problem
• Its principle and lesson can be applied to all kinds of team
work and reflects on their wins and losses to continuously
improve
• This is the reason scrum is so popular.
Scrum

provides generic Scrum is a software

things for framework that development under Scrum is a framework
development helps teams work which requirements for getting work done,
together. and solutions evolve where agile is a mindset.
through the
collaborative effort
of self-organizing

Framework Scrum Agile Scrum VS Agile

Scrum Artifacts

• Product backlog
• Lists all the work on a project
• Sprint Backlog
• work to be completed
In the sprint 01

• Increment
• Shippable piece of
product 03
02
Stories Not Started In Progress Done

Story #1 Task C Task F

__________
__________
_ Task G

Story #2
__________
Task A Task B Task H
__________
_

Task I Task J
Story #3
__________ Task D Task E
__________
_
Roles For Scrum

1. Product owner

2. Scrum master

3. Scrum development team

 Product Owner

Although he will
be the
responsible to Product owner
answer question will be single
to his person he can
have a team

This role have a

vision of what they
want to build.
Product owner can
Prioritizes the person who
all work for have strong
the product knowledge of system
user
Scrum Master
Removing
blockers to Enables
development agreement
team progress building within
the Team

Acts as a
process
coach
Manage process
Protects the authority, finding
Team from new techniques
organizational
distractions
 Scrum Development Team

Cross-functional not Directly answerable

single skillset. 1. 4.

Self-organizing and
self-managing. dedicated to one
2. 5. project

Team focuses
how work gets 3. 6. Appropriate Skills members
accomplished.
 Scrum Events

1. Organize the backlog

2. Sprint planning
3. Sprint
4. Daily scrum stand up Sprint Review
5. Sprint review
6. Sprint retrospective

Sprint
The Sprint
Retrospective

Sprint Planning

Daily Scrum
1-Organizing the Backlog

• According to the prioritize features the product is organized.

• Sometimes known as backlog grooming, this event is the
responsibility of the product owner. The product owner’s main
jobs are to drive the product towards its product vision Therefore,
he/she maintains this list using feedback from users and the
development team to help prioritize and keep the list clean and
ready to be worked on at any given time
2-Sprint Planning

• According to the prioritize features the product is organized.

• The work to be performed (scope) during the current sprints
planned during this meeting by the entire development team.
Specific use stories are then added to the sprint from the product
backlog. These stories always align with the goal and are also
agreed upon by the scrum team to be feasible to implement
during the sprint. At the end of the planning meeting, every scrum
member needs to be clear on what can be delivered in the sprint
and how the increment can be delivered.
3-Sprint

• A Sprint is a time-box of one month or less. A new Sprint starts

immediately after the completion of the previous Sprint
• A sprint is the actual time period when the scrum team works
together to finish an increment. Two weeks is a pretty typical
length for a sprintBut it’s really up to your team, and you
shouldn’t be afraid to change it if it’s not working!
4-Daily Scrum

• This is a daily super-short meeting that happens at the same

time (usually mornings) and place to keep it simple. Many teams
try to complete the meeting in 15 minutes, but that’sjust a
guideline. This meeting is also called a ‘daily stand-up’
emphasizing that it needs to be a quick one.
• What did I do yesterday?
•What do I plan to do today?
•Are there any obstacles?
5-Sprint Review

• If the product still have some non-achievable features then it will

be checked in this stage and then the product is passed to the
Sprint Retrospective stage.
• At the end of the sprint, the team gets together for an informal
session to view a demo of, or inspect, the increment. The
development team showcases the backlog items that are now
‘Done’ to stakeholders and teammates for feedback. The product
owner can decide whether or not to release the increment,
although in most cases the increment is released.
6-Sprint Retrospective

• In this stage quality or status of the product is checked.

• The retrospective is where the team comes together to document
and discuss what worked and what didn’t work in a sprint
Input from end-
users,
customers ,
teams , and Scrum Meeting
other Scrum
stakeholders
Master
Every
24
Product Hours
backlog
refinement
Product Owner
Features Team
1. tasks
Sprint Review
2.
Plan how much
work to commit for
1. 2-4 Potentially
3. 2. shippable product
4.
sprint
3.
weeks increment
5. 4.
Sprint Planning Meeting No changes in duration
6. 5. or scope during the
7. sprint cycle
Sprint Backlog Retrospective
Product backlog
 Comparative Analysis

Parameter Scrum Adaptive

Development Approach Iterative approach Iterative approach

Iteration time period 2-4 weeks 4-8 week

Project team All sizes usually 10-15 Smaller 5-9 members

Team communication Informal daily stand up meeting Informal face-to-face

Comparative Analysis of
Adaptive and Scrum
 Comparative Analysis

Parameter Scrum Adaptive

Project Size All sizes of project Smaller projects

Process type Several releases Incremental

Focus Self organization of team Add issues such as social, cultural team
skills

Additional features • Adaptive • Rapid

• Experimental • iterative
• Flexible
Advantages

• Scrum framework is fast moving and money efficient.

• Scrum framework works by dividing the large product into small sub-products. It’s like a divide and
conquer strategy
• In Scrum customer satisfaction is very important.
• Scrum is adaptive in nature because it have short sprint.
• As Scrum framework rely on constant feedback therefore the quality of product increases in less
amount of time
Disadvantages

• Scrum framework do not allow changes into their sprint.

• It can be difficult for the Scrum to plan, structure and organize a project that lacks a clear definition.
• The daily Scrum meetings and everyday reviews require large resources
Conclusions

• Agile methodology is a practice that helps continuous iteration of the development process.
• In the Agile method, the priority is always to satisfy the customer by providing continuous delivery of
valuable software.
• The main benefit of Scrum is its flexibility as it quickly reacts to changes.
• In the Agile process, the leadership plays a energetic role.
• In Scrum, daily sprint meeting is conducted to review and feedback to decide future progress of the
project.
• In Scrum, when the team is done with the current sprint activity, the next sprint can be planned.
Sources

https://www.geeksforgeeks.org/scrum-software-development/
https://www.atlassian.com/agile/scrum
https://www.mountaingoatsoftware.com/agile/scrum
https://www.guru99.com/agile-vs-scrum.html