0% found this document useful (0 votes)
160 views27 pages

Muhammad Azani Hasibuan

SCRUM is an agile framework for managing complex projects. It consists of roles, artifacts, and events. The roles are Product Owner, Scrum Master, and Development Team. The artifacts are Product Backlog, Sprint Backlog, and Increment. The events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The framework uses an iterative approach with sprints to incrementally deliver working software.

Uploaded by

Arif Raihan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
160 views27 pages

Muhammad Azani Hasibuan

SCRUM is an agile framework for managing complex projects. It consists of roles, artifacts, and events. The roles are Product Owner, Scrum Master, and Development Team. The artifacts are Product Backlog, Sprint Backlog, and Increment. The events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The framework uses an iterative approach with sprints to incrementally deliver working software.

Uploaded by

Arif Raihan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 27

Muhammad Azani Hasibuan

[email protected] 1
Definition of SCRUM

SCRUM Components

SCRUM Process
Definition of SCRUM

SCRUM Components

SCRUM Process
uncertainty

CHAOS

COMPLEX
COMPLICATED

PREDICTABLE

known
simple complex
uncertainty

CHAOS

COMPLEX
COMPLICATED Agile
Project
Structured
Project PREDICTABLE

known
simple complex
The best way to optimize the predictability
and control the risk is by employs an
iterative and incremental approach.
--SCRUM Guide
A framework within which people can address
complex adaptive problems, while productively
and creatively delivering products of the highest
possible value.
SCRUM GUIDE

Source: Ken Schwaber, SCRUM Guide


Jan Feb Mar Apr Mei Jun Jul Aug Oct Nov

Planning

Design

Coding

Testing

Release

Review
Jan Feb Mar Apr Mei Jun Jul Aug Oct Nov

ITERATION #1 ITERATION #2 ITERATION #3 ITERATION #4


Design Design Design Design
Planning

Planning

Planning
Planning
Review

Review

Review

Review
Coding Coding Coding Coding

Testing Testing Testing Testing

Release Release Release Release


Definition of SCRUM

SCRUM Components

SCRUM Process
ROLE ARTIFACTS EVENTS
Product Owner Product Backlog Sprint Planning

Scrum Master Sprint Backlog Daily SCRUM

Development Team Increment Sprint Execution

Sprint Review

Sprint Retrospective
Product Owner SCRUM Master Development Team
Define features/Product Backlog
Prioritize features/ Product Backlog
Pick release dates
Give feedback
Manage stakeholders
Accept or reject results Product Owner
Define tasks
Ensure quality
Estimate effort
Evolve processes
Development Team Develop product Collaboratively
Keep the team fully productive
Ensuring SCRUM is undestood and enacted
Facilitate the team
Remove impediments
Prevent interruptions
Support the process SCRUM Master
Definition of SCRUM

SCRUM Components

SCRUM Process
DAILY
SCRUM

SPRINT SPRINT SPRINT SPRINT


PLANNING EXECUTION REVIEW RETROSPECTIVE

SPRINT/ ITERATION
Product Owner

• An ordered list of requirement


• Potential features of the product
• The single source of truth for what is planned in
SPRINT DAILY SPRINT SPRINT
thePLANNING
product SCRUM REVIEW RETROSPECTIVE
• Public and available

SPRINT/ ITERATION
Subset of product backlog

Subset of 4 hours for 2 weeks sprint /


Product Backlog 8 hours for 4 weeks sprint

Product Owner, SCRUM Master, and Dev. Team

SPRINT •Estimate the complexity


DAILY of each product
SPRINT SPRINT
backlog item (PBI)
PLANNING SCRUM REVIEW RETROSPECTIVE
•Negotiate the scope of PBI to PO
•Decompose each product backlog items into
tasks (called sprint backlog)

Sprint backlog, Sprint Goal

SPRINT/ ITERATION
Progress in previous day

15 minute ( in the early day)


Sprint Backlog

DAILY SCRUM Master, and Dev. Team


SCRUM
• Create a plan for the next 24 hours
• Assess progress toward the Sprint
SPRINT SPRINT SPRINT
Goal SPRINT
PLANNING EXECUTION REVIEW
• By the Development RETROSPECTIVE
Team, for the
Development Team)

SPRINT/ ITERATION
Sprint Backlog
Sprint Backlog

2-4 weeks
DAILY
SCRUM SCRUM Master, and Dev. Team

SPRINT SPRINT SPRINT SPRINT


Implement the sprint backlog
PLANNING EXECUTION REVIEW RETROSPECTIVE
Increment

SPRINT/ ITERATION
Sprint Backlog Increment
Increment Of Software
DAILY
2 hours for 2 weeks sprint/ SCRUM
4 hours for 4 weeks sprint
SPRINT SPRINT SPRINT SPRINT
PLANNING
PO, SCRUM Master, and Dev.EXECUTION
Team REVIEW RETROSPECTIVE
• No Slides
• Show the increment
• Get Feedback form Product Owner

Feedback from Product Owner

SPRINT/ ITERATION
Sprint Backlog Increment
Feedback from PO & Experiences
DAILY
2 hours SCRUM
for 2 weeks sprint/
4 hours for 4 weeks sprint
SPRINT SPRINT SPRINT SPRINT
PLANNING EXECUTION
SCRUM Master, and Dev. TeamREVIEW RETROSPECTIVE
• Identify what worked well
• Identify what could be improved
• Find the actionable improvements

Future Improvements

SPRINT/ ITERATION
Increment

DAILY
SCRUM

SPRINT SPRINT SPRINT SPRINT


PLANNING EXECUTION REVIEW RETROSPECTIVE

SPRINT/ ITERATION
ROLE ARTIFACTS EVENTS
Product Owner Product Backlog Sprint Planning

Scrum Master Sprint Backlog Daily SCRUM

Development Team Increment Sprint Execution

Sprint Review

Sprint Retrospective
• Schwaber, Ken & Jeff Sutherland (2011), The Scrum Guide, scrum.org

•Joshua Partogi (2012), The Scrum Fundamental Course, scrumway.co

You might also like