SCRUM is a framework for managing complex projects that emphasizes iterative development, daily self-organization, and regular inspection of progress and results. Key components of SCRUM include roles like the Product Owner, Scrum Master, and Development Team. Artifacts include the Product Backlog, Sprint Backlog, and Increment. Events in each Sprint include Sprint Planning, Daily Scrums, Sprint Execution, Sprint Review, and Sprint Retrospective. The goal is to optimize predictability, risk control, and value delivery through short cycles of work called Sprints.

1. 1
Muhammad Azani Hasibuan
muhammad.azani@gmail.com

2. Definition of SCRUM
SCRUM Components
SCRUM Process

3. Definition of SCRUM
SCRUM Components
SCRUM Process

4. simple complex
known
uncertainty
PREDICTABLE
COMPLICATED
COMPLEX
CHAOS

5. simple complex
known
uncertainty
PREDICTABLE
COMPLICATED
COMPLEX
CHAOS
Agile
Project
Structured
Project

6. The best way to optimize the predictability
and control the risk is by employs an
iterative and incremental approach.
--SCRUM Guide

7. SCRUM GUIDE
A framework within which people can address
complex adaptive problems, while productively
and creatively delivering products of the highest
possible value.
Source: Ken Schwaber, SCRUM Guide

8. Jan Feb Mar Apr Mei Jun Jul Aug Oct Nov
Planning
Design
Coding
Testing
Release
Review

9. Jan Feb Mar Apr Mei Jun Jul Aug Oct Nov
Planning
Review
Design
Coding
Testing
Release
Planning
Review
Design
Coding
Testing
Release
Planning
Review
Design
Coding
Testing
Release
Planning
Review
Design
Coding
Testing
Release
ITERATION #1 ITERATION #2 ITERATION #3 ITERATION #4

10. Definition of SCRUM
SCRUM Components
SCRUM Process

11. ROLE
Product Owner
Scrum Master
Development Team
ARTIFACTS
Product Backlog
Sprint Backlog
Increment
EVENTS
Sprint Planning
Daily SCRUM
Sprint Execution
Sprint Review
Sprint Retrospective

12. Product Owner SCRUM Master Development Team

13. Define features/Product Backlog
Prioritize features/ Product Backlog
Pick release dates
Give feedback
Manage stakeholders
Accept or reject results Product Owner

14. Define tasks
Estimate effort
Develop product Collaboratively
Ensure quality
Evolve processes
Development Team

15. Remove impediments
Prevent interruptions
Facilitate the team
Support the process
Ensuring SCRUM is undestood and enacted
SCRUM Master
Keep the team fully productive

16. Definition of SCRUM
SCRUM Components
SCRUM Process

17. SPRINT
PLANNING
SPRINT
EXECUTION
SPRINT
REVIEW
SPRINT
RETROSPECTIVE
SPRINT/ ITERATION
DAILY
SCRUM

18. SPRINT
PLANNING
DAILY
SCRUM
SPRINT
REVIEW
SPRINT
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
the product
• Public and available

19. DAILY
SCRUM
SPRINT
REVIEW
SPRINT
RETROSPECTIVE
SPRINT/ ITERATION
Subset of
Product Backlog
SPRINT
PLANNING
4 hours for 2 weeks sprint /
8 hours for 4 weeks sprint
Product Owner, SCRUM Master, and Dev. Team
•Estimate the complexity of each product
backlog item (PBI)
•Negotiate the scope of PBI to PO
•Decompose each product backlog items into
tasks (called sprint backlog)
Subset of product backlog
Sprint backlog, Sprint Goal

20. SPRINT
PLANNING
SPRINT
REVIEW
SPRINT
RETROSPECTIVE
SPRINT/ ITERATION
Sprint Backlog
15 minute ( in the early day)
SCRUM Master, and Dev. Team
• Create a plan for the next 24 hours
• Assess progress toward the Sprint
Goal
• By the Development Team, for the
Development Team)
Progress in previous day
SPRINT
EXECUTION
DAILY
SCRUM

21. SPRINT
PLANNING
SPRINT
REVIEW
SPRINT
RETROSPECTIVE
SPRINT/ ITERATION
Sprint Backlog
2-4 weeks
SCRUM Master, and Dev. Team
Implement the sprint backlog
Sprint Backlog
SPRINT
EXECUTION
DAILY
SCRUM
Increment

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

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

25. SPRINT
PLANNING
SPRINT
REVIEW
Increment
SPRINT/ ITERATION
SPRINT
EXECUTION
DAILY
SCRUM
SPRINT
RETROSPECTIVE

26. ROLE
Product Owner
Scrum Master
Development Team
ARTIFACTS
Product Backlog
Sprint Backlog
Increment
EVENTS
Sprint Planning
Daily SCRUM
Sprint Execution
Sprint Review
Sprint Retrospective

27. • Schwaber, Ken & Jeff Sutherland (2011), The Scrum Guide, scrum.org
•Joshua Partogi (2012), The Scrum Fundamental Course, scrumway.co