SlideShare a Scribd company logo
TALENT UP
PENGENALAN
METODE SCRUM
JDV 19 September 2019
Ibnu Fajar
Yunardi
Build QATROS Now
Product Manager : Binar Academy
2017-August 2019
QA Engineer : GOJEK 2015-2017
Game Tester : Gameloft 2014-2015
3
Source : https://www.seguetech.com/waterfall-vs-agile-methodology/
4
Source : https://blog.ganttpro.com/en/waterfall-vs-agile-with-advantages-and-disadvantages/
5
Source :Image based on Jeff Patton’s work jpattonassociates.com
SCRUM
Scrum is a framework that helps teams work together. Scrum encourages
teams to learn through experiences, self-organize while working on a
problem, and reflect on their wins and losses to continuously improve.
6
Scrum History
1986 1993
Dr. Takeuchi and Dr.
Nonaka introduced
the term “Scrum” in
the article The New
New Product
Development Game
1995 2010-2017
Ken Schwaber and
Jeff Sutherland
formalized the
“Scrum” framework
in the first
published paper on
Scrum at OOPSLA.
Scrum was
introduced by Jeff
Sutherland at Easel
Corporation using
the study by
Takeuchi and
Nonaka
The first Scrum Guide
was published.Its
incremental updates
were made in 2011,
2013, 2016, and 2017.
SCRUM
Scrum and agile are the same thing because Scrum is
centered around continuous improvement, which is a
core principle of agile. However, Scrum is a framework
for getting work done, where agile is a mindset.
1
8
“
The scrum framework is heuristic; it’s based on continuous learning and
adjustment to fluctuating factors. It acknowledges that the team doesn’t know
everything at the start of a project and will evolve through experience. Scrum
is structured to help teams naturally adapt to changing conditions and user
requirements, with re-prioritization built into the process and short release
cycles so your team can constantly learn and improve.
9
1
2
SCRUM
MAIN
THINGS
A scrum team
needs three
specific roles
Artifacts are
something that we
make, like a tool to
solve a problem
Actors/Roles
Artifacts
Scrum Events
Scrum framework are the set of
sequential events, ceremonies or
meetings that scrum teams perform
on a regular basis.
Scrum Master
They coach teams, product owners, and
the business on the scrum process, and
look for ways to fine-tune their practice
of it. As the facilitator-in-chief,
Product Owner
They are focused on understanding
business, customer, and market
requirements, then prioritizing the
work to be done.
Team Member
All members of the team help one
another to ensure a successful sprint
completion.
Actors
User stories are short, simple
descriptions of a feature told
from the perspective of the
person who desires the new
capability, usually a user or
customer of the system. They
typically follow a simple
template:
As a < type of user >, I want <
some goal > so that < some
reason >.
Scrum Artifacts
Product Backlog Sprint Backlog User Stories
Inventory of idea features,
defects, or technical work
that has yet to be worked
on.
Sprint backlog is a list of
tasks identified by team to
be completed during the
Scrum sprint. During the
sprint planning meeting,
the team selects some
number of product backlog
items.
Velocity is a measure of
the amount of work a
Team can tackle during a
single Sprint and is the key
metric in Scrum. Velocity
is calculated at the end of
the Sprint by totaling the
Points for all fully
completed Task.
Scrum Artifacts
Story Points Team Velocity
Story points are a unit of
measure for expressing an
estimate of the overall
effort that will be required
to fully implement a
product backlog item or
any other piece of work.
Burndown Chart
Visual measurement tool that
shows the completed work
per day against the projected
rate of completion for the
current project release. Its
purpose is to enable that the
project is on the track to
deliver the expected solution
within the desired schedule.
CreditsScrum Board
CreditsStory Points
Source : https://www.quickscrum.com/ScrumGuide/175/sg-Estimate-A-Story
CreditsBurndown Chart
Source : https://innolution.com/blog/burn-charts-for-communicating-progress-through-a-scrum-release
CreditsVelocity
Scrum Event
Sprint Planning (Day-1)
Product Owner provides a list of
high priority items on the backlog.
The team chooses the task they
can complete during the sprint
and transfer the tasks from
product backlog to the sprint
backlog.
Sprint
Two weeks is a pretty typical
length for a sprint, though some
teams find a week to be easier to
scope or a month to be easier to
deliver a valuable increment.
Standup Meeting
15 Minutes max meeting and
stand-up, update the progress
with :
• What did I do yesterday?
• What do I plan to do today?
• Are there any obstacles?
Sprint Review (Day 10)
A live demonstration is
given at the end of each
sprint to showcase the work
the team has completed
during the sprint in the sprint
review meeting.
Sprint Retrospective(Day 10)
This meeting is held to reflect on the
success of the Scrum process and is
there any changes required to be made in
the next sprint. The team discusses the
highs and lows of the earlier sprint and all
the improvements for the next sprint.
18
Sprint Planning
Attendees :
● Scrum Master
● Product Owner
● Scrum Team
19
Daily Standup Meeting
Attendees :
● Scrum Master
● Product Owner (Optional)
● Scrum Team
20
Sprint Review
Attendees :
● Scrum Master
● Product Owner
● Scrum Team
● Stakeholder
21
Sprint Retrospective
Attendees :
● Scrum Master
● Product Owner
● Scrum Team
22
PROS AND CONS SCRUM
PROS CONS
● it works best and fasts with small team
members only.
● If any team member leaves in the
middle of a project, it can have a huge
negative impact on the project
● Quality is hard to implement until the
team goes through an aggressive
testing process
● Need High Commitment
● Fail Faster and Early Improvement
● Project deliverables quickly and efficiently
● Effective use of time and money
● Team members have a clearer picture of
their tasks.
● Easy to know how much work and effort
individual team members are contributing
to the project.
ADA YANG MAU NANYA???
Thankyou

More Related Content

PDF
Scrum Guide In One Slide
PPTX
How scrum works
PPTX
Agile methodology
PPTX
SCRUM – Agile Methodology
PDF
Scrum & UX - Barcelona Scrum Meetup
PPTX
Introduction to Scrum
PDF
Scrum: Scrum Guide Summary
PDF
Scrum Guide In One Slide
How scrum works
Agile methodology
SCRUM – Agile Methodology
Scrum & UX - Barcelona Scrum Meetup
Introduction to Scrum
Scrum: Scrum Guide Summary

What's hot (19)

PPTX
Scrum
PPTX
Ba questions v1 agile
ODP
Scrum in 15 Minutes
PPT
Overview of Scrum
PDF
Scrum guide 2020
PPTX
Scrum Introduction
PPTX
Scrum for IT Offshore & IT Outsourcing in Asia
PDF
Masie slides Agile_Scrum
PDF
Introduction To Scrum
ODP
PDF
PDF
The Scrum Roles presented by the Scrumlies 2009
PPTX
Agile Methodologies: Introduction to Scrum .
PPT
Agile In 5 Minutes
PPT
Agile Experience
PPT
Introduction To Scrum
PPT
Introduction To Scrum
PDF
Scrum Out Of The Nutshell
ODP
Agile scrum introduction
Scrum
Ba questions v1 agile
Scrum in 15 Minutes
Overview of Scrum
Scrum guide 2020
Scrum Introduction
Scrum for IT Offshore & IT Outsourcing in Asia
Masie slides Agile_Scrum
Introduction To Scrum
The Scrum Roles presented by the Scrumlies 2009
Agile Methodologies: Introduction to Scrum .
Agile In 5 Minutes
Agile Experience
Introduction To Scrum
Introduction To Scrum
Scrum Out Of The Nutshell
Agile scrum introduction
Ad

Similar to Scrum Introduction (20)

PPT
Scrum Overview
PPTX
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
PPT
Lecture 10 Agile Processes-Scrum In SDLC.ppt
PPTX
Introduction to agile
PPTX
Agile Processes - Scrum
PPT
24 scrum
PPT
PPTX
Mujeebur rahmansaher introduction-to-scrum_v2
PPT
Lecture 12 - Agile Processes-Scrum.pptx.ppt
PPT
Lecture 12 - Agile Processes-Scrum 2024.ppt
PPT
24-scrum.ppt
PPT
Scrum and Agile Software Development
PPT
scrum_practice_management_practice_document.ppt
PPT
Agile by KD
PPT
Agile by KD
PPTX
What is Scrum? SlideShare
PDF
Agile, not just for software
PPTX
Agile and Scrum - GB
PDF
Agile Scrum Quick Reference Card
PPT
Agile Scrum - Overview
Scrum Overview
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
Lecture 10 Agile Processes-Scrum In SDLC.ppt
Introduction to agile
Agile Processes - Scrum
24 scrum
Mujeebur rahmansaher introduction-to-scrum_v2
Lecture 12 - Agile Processes-Scrum.pptx.ppt
Lecture 12 - Agile Processes-Scrum 2024.ppt
24-scrum.ppt
Scrum and Agile Software Development
scrum_practice_management_practice_document.ppt
Agile by KD
Agile by KD
What is Scrum? SlideShare
Agile, not just for software
Agile and Scrum - GB
Agile Scrum Quick Reference Card
Agile Scrum - Overview
Ad

Recently uploaded (20)

PPTX
Human Resource Management | Introduction,Meaning and Definition
PPTX
INTELLECTUAL PROPERTY LAW IN UGANDA.pptx
PDF
Features of Effective decision making in Management
PDF
The Cyber SwarmShield by Stéphane Nappo
PPTX
Course Overview of the Course Titled.pptx
PPTX
_ISO_Presentation_ISO 9001 and 45001.pptx
PDF
CISSP Domain 5: Identity and Access Management (IAM)
PPTX
TCoE_IT_Concrete industry.why is it required
PDF
CISSP - Domain 7: Security Operations - InfoSec Institute
PDF
Contemporary management and it's content
PDF
CHAPTER 15- Manageement of Nursing Educational Institutions- Staffing and st...
PPTX
Human resources management -job perception concept
PPTX
Leadership for Industry 4.0 And Industry 5.0
PPTX
Chapter One an overview of political economy
PDF
CHAPTER 14 Manageement of Nursing Educational Institutions- planing and orga...
PDF
Equity at the Helm_ Guiding Schools Through Inclusive Leadership by Dr.pdf
PDF
Phillips model training for evaluation pdf
PPTX
Press Release Importance & Structure.pptx
PDF
Leveraging Intangible Assets Through Campus Entrepreneurship and Tech Transfer
PDF
1_Corporate Goverance presentation topic
Human Resource Management | Introduction,Meaning and Definition
INTELLECTUAL PROPERTY LAW IN UGANDA.pptx
Features of Effective decision making in Management
The Cyber SwarmShield by Stéphane Nappo
Course Overview of the Course Titled.pptx
_ISO_Presentation_ISO 9001 and 45001.pptx
CISSP Domain 5: Identity and Access Management (IAM)
TCoE_IT_Concrete industry.why is it required
CISSP - Domain 7: Security Operations - InfoSec Institute
Contemporary management and it's content
CHAPTER 15- Manageement of Nursing Educational Institutions- Staffing and st...
Human resources management -job perception concept
Leadership for Industry 4.0 And Industry 5.0
Chapter One an overview of political economy
CHAPTER 14 Manageement of Nursing Educational Institutions- planing and orga...
Equity at the Helm_ Guiding Schools Through Inclusive Leadership by Dr.pdf
Phillips model training for evaluation pdf
Press Release Importance & Structure.pptx
Leveraging Intangible Assets Through Campus Entrepreneurship and Tech Transfer
1_Corporate Goverance presentation topic

Scrum Introduction

  • 2. Ibnu Fajar Yunardi Build QATROS Now Product Manager : Binar Academy 2017-August 2019 QA Engineer : GOJEK 2015-2017 Game Tester : Gameloft 2014-2015
  • 5. 5 Source :Image based on Jeff Patton’s work jpattonassociates.com
  • 6. SCRUM Scrum is a framework that helps teams work together. Scrum encourages teams to learn through experiences, self-organize while working on a problem, and reflect on their wins and losses to continuously improve. 6
  • 7. Scrum History 1986 1993 Dr. Takeuchi and Dr. Nonaka introduced the term “Scrum” in the article The New New Product Development Game 1995 2010-2017 Ken Schwaber and Jeff Sutherland formalized the “Scrum” framework in the first published paper on Scrum at OOPSLA. Scrum was introduced by Jeff Sutherland at Easel Corporation using the study by Takeuchi and Nonaka The first Scrum Guide was published.Its incremental updates were made in 2011, 2013, 2016, and 2017.
  • 8. SCRUM Scrum and agile are the same thing because Scrum is centered around continuous improvement, which is a core principle of agile. However, Scrum is a framework for getting work done, where agile is a mindset. 1 8
  • 9. “ The scrum framework is heuristic; it’s based on continuous learning and adjustment to fluctuating factors. It acknowledges that the team doesn’t know everything at the start of a project and will evolve through experience. Scrum is structured to help teams naturally adapt to changing conditions and user requirements, with re-prioritization built into the process and short release cycles so your team can constantly learn and improve. 9
  • 10. 1 2 SCRUM MAIN THINGS A scrum team needs three specific roles Artifacts are something that we make, like a tool to solve a problem Actors/Roles Artifacts Scrum Events Scrum framework are the set of sequential events, ceremonies or meetings that scrum teams perform on a regular basis.
  • 11. Scrum Master They coach teams, product owners, and the business on the scrum process, and look for ways to fine-tune their practice of it. As the facilitator-in-chief, Product Owner They are focused on understanding business, customer, and market requirements, then prioritizing the work to be done. Team Member All members of the team help one another to ensure a successful sprint completion. Actors
  • 12. User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template: As a < type of user >, I want < some goal > so that < some reason >. Scrum Artifacts Product Backlog Sprint Backlog User Stories Inventory of idea features, defects, or technical work that has yet to be worked on. Sprint backlog is a list of tasks identified by team to be completed during the Scrum sprint. During the sprint planning meeting, the team selects some number of product backlog items.
  • 13. Velocity is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. Velocity is calculated at the end of the Sprint by totaling the Points for all fully completed Task. Scrum Artifacts Story Points Team Velocity Story points are a unit of measure for expressing an estimate of the overall effort that will be required to fully implement a product backlog item or any other piece of work. Burndown Chart Visual measurement tool that shows the completed work per day against the projected rate of completion for the current project release. Its purpose is to enable that the project is on the track to deliver the expected solution within the desired schedule.
  • 15. CreditsStory Points Source : https://www.quickscrum.com/ScrumGuide/175/sg-Estimate-A-Story
  • 16. CreditsBurndown Chart Source : https://innolution.com/blog/burn-charts-for-communicating-progress-through-a-scrum-release
  • 18. Scrum Event Sprint Planning (Day-1) Product Owner provides a list of high priority items on the backlog. The team chooses the task they can complete during the sprint and transfer the tasks from product backlog to the sprint backlog. Sprint Two weeks is a pretty typical length for a sprint, though some teams find a week to be easier to scope or a month to be easier to deliver a valuable increment. Standup Meeting 15 Minutes max meeting and stand-up, update the progress with : • What did I do yesterday? • What do I plan to do today? • Are there any obstacles? Sprint Review (Day 10) A live demonstration is given at the end of each sprint to showcase the work the team has completed during the sprint in the sprint review meeting. Sprint Retrospective(Day 10) This meeting is held to reflect on the success of the Scrum process and is there any changes required to be made in the next sprint. The team discusses the highs and lows of the earlier sprint and all the improvements for the next sprint. 18
  • 19. Sprint Planning Attendees : ● Scrum Master ● Product Owner ● Scrum Team 19
  • 20. Daily Standup Meeting Attendees : ● Scrum Master ● Product Owner (Optional) ● Scrum Team 20
  • 21. Sprint Review Attendees : ● Scrum Master ● Product Owner ● Scrum Team ● Stakeholder 21
  • 22. Sprint Retrospective Attendees : ● Scrum Master ● Product Owner ● Scrum Team 22
  • 23. PROS AND CONS SCRUM PROS CONS ● it works best and fasts with small team members only. ● If any team member leaves in the middle of a project, it can have a huge negative impact on the project ● Quality is hard to implement until the team goes through an aggressive testing process ● Need High Commitment ● Fail Faster and Early Improvement ● Project deliverables quickly and efficiently ● Effective use of time and money ● Team members have a clearer picture of their tasks. ● Easy to know how much work and effort individual team members are contributing to the project.
  • 24. ADA YANG MAU NANYA???