Scrum

Indonesia Scrum Master Training

Agile Mindset & Manifesto

Basic Scrum Framework

Scrum Event

Scrum Role

Angga Pratama Scrum Artifact

Senior Agile Coach - Ekipa
 Agile Mindset, Manifesto & Scrum

Scrum Team

Sprint

Product Sprint Incrementally

Scrum Event Working
Backlog Backlog
Software
 Agile Mindset
AGILE IS A DESCRIBED BY DEFINED BY MANIFESTED THROUGH AN
MINDSET 4 VALUES 12 PRINCIPLES UNLIMITED NUMBER OF PRACTICES

Mindset Values Principles Practices

 Agile Values

INDIVIDUAL & INTERACTION over PROCESS AND TOOLS

WORKING SOFTWARE over COMPREHENSIVE DOCUMENTATION

CUSTOMER COLLABORATION over CONTRACT NEGOTIATION

RESPONDING TO CHANGE over FOLLOWING A PLAN

 Agile Principles

#1 #2 #3 #4

Customer Welcome Deliver Working

Satisfaction Change Frequently Together

#5 #6 #7 #8

Motivated Face to Working Constant

Team Face Software Development
Pace

#9 #10 #11 #12

Continues Simplicity Self Reflect &

Attention Organization Adjust
 Agile Practice

SAFe
KANBAN

LeSS

SCRUM
Extreme
Programming
(XP)
….. And many other practices
 Why Scrum

Quicker customer
Complex Project satisfaction and feedback

CERTAINTY UNCERTAINTY
Release small “DONE” Increment
early & often with constant pace.

Examples of UNCERTAINTY Measure & Learn Feedback

● Requirement change
● Validate assumption of the uncertainty
● Market Demand
● Avoid risk for spending time & cost on the
● Stakeholder needs
wrong thing
● Competitor’s Speed
● Ability to adapting the change faster
● New Technology
● Organizational changes Valuable input for Product
● ...etc Grooming & Development
 Scrum Theory

Founded By A framework
within which people can address
complex adaptive problems,
while productively and creatively
knowledge comes from
experience and making
EMPIRICISM
decisions based on

delivering products of the what is known

highest possible value

Jeff Ken
Sutherland Schwaber

The Three Pillars of Empiricism Scrum Values The Building Blocks

● Transparency ● Courage ● Scrum Event
● Inspection ● Focus ● Scrum Role
● Adaptation ● Commitment ● Scrum Artifact
● Respect
● Openness
 Iterative Delivery

Vision Continue
 Scrum Event

Daily Scrum

Sprint
Retrospective

Sprint
Review

Sprint Sprint
Planning
 Sprint Planning

What is Sprint Planning ?

The development team plan and commit to what they can deliver in the next Sprint by
reviewing prioritized backlog item, estimate user stories, planning sprint capacity

When this event held ?

The first day of a new sprint

Who should attend ?

Mandatory : All Scrum Team (Product Owner, Scrum Master, Development Team)
Optional : Stakeholder, Business User, etc.. based on Scrum Team invitation

Event Timebox ?
2-3 hours for 2 week sprint
 Sprint Planning

Input Output

Prioritized Product Backlog

The latest product Increment

Projected capacity of the

Development Team during the Sprint

Past performance of the

Development Team

● Sprint GOAL
● Sprint Backlog picked by
development team
 Sprint

What is Sprint ?
The heart of Scrum which a "Done", useable, and potentially releasable product Increment is
created. Sprints have consistent durations throughout a development effort

When this event held ?

Immediately after Sprint Planning

Who should attend ?

All Scrum Team with Scrum Master as the process owner

Event Timebox ?
1 month or less (usually 2 weeks)
 Sprint

Input Output

Potentially Shippable Increment

Sprint Backlog
 Daily Scrum / Daily Standup

What is Daily Scrum / Daily Standup ?

Progress inspection towards Sprint Goal by conducting 15 minute daily meeting for each of the
Development team members to answer three questions : what did i do yesterday ?, what will i do
today ?, do i have any impediments ?

When this event held ?

Daily, same place & same time, to reduce complexity.

Who should attend ?

Mandatory : Development Team
Optional : Product Owner, Scrum Master

Event Timebox ?
10-15 minutes
 Daily Scrum / Daily Standup

Input Output

Latest development progress

Latest & upcoming impediments

Current condition regarding people,

process & tools

Todays work plan

Replan & Adapting Sprint Backlog

 Sprint Review

What is Sprint Review ?

Inspection of the Sprint Goal (product) by demonstrating the work which meet “definition of
done”, seek feedback from stakeholder or others meeting participant, update product backlog and
accept/reject delivery.

When this event held ?

At the end of sprint

Who should attend ?

Mandatory : Key Stakeholder & All Scrum Team (Product Owner, Scrum Master, Development Team)
Optional : Other Business User by Product Owner invitation

Event Timebox ?
2-3 hours for 2 week sprint
 Sprint Review

Input Output

Latest work that already done

Stakeholder and others feedback

Development team exposure about Replan & Reprioritized

what went well, the impediments Product Backlog
and how they solve.
 Sprint Retrospective

What is Sprint Retrospective ?

Inspection against people and process during previous sprint to encourage continuous
improvement by discussing : what went well ?, what didn’t work well ?, what should be improved
& next action

When this event held ?

At the end of sprint (usually after sprint review)

Who should attend ?

All Scrum Team (Product Owner, Scrum Master, Development Team)

Event Timebox ?
1-2 hours for 2 week sprint
 Sprint Retrospective

Input Output

What went well during previous

sprint

What didn’t go well during

previous sprint

Feedback regarding People and

Process
Scrum Master observation
Action Items for Improvement
 Supporting Event

Product Backlog Grooming

Activities when the product owner and some, or all, of the rest of the team review items on the
product backlog to ensure the backlog contains the appropriate items,
They prioritized the backlog so that the items at the top of the backlog are ready for the upcoming
sprint planning.

Meta Scrum
A regular forum where the entire enterprise can align behind the Product Owners’ backlogs at every
level of Scrum in the organization.
Product Owner’s and high key management person will attend this event.
 Scrum Role

Video

Product Owner Development Team Scrum Master

 ProductOWNER
AS A PRODUCT Owner YOU:
CARE ABOUT THE USER/CUSTOMER NEEDS AND THE BUSINESS GOALS

................................. 1 ARE RESPONSIBLE FOR THE BACKLOG

.............. 2 HAVE A VISION WHERE TO TAKE THE PRODUCT

......... 3 ARE EMPOWERED TO OWN THE PRODUCT ON BEHALF OF

THE COMPANY

......... 4 CARE ABOUT THE USER NEEDS & THE BIZ GOALS

............... 5 ARE A TEAM PLAYER WORKING WITH STAKEHOLDERS AND

THE DEVELOPMENT TEAM

................................. 6 ARE RESPONSIBLE FOR SETTING THE PRIORITIES OF

THE BACKLOG ITEMS
A SCRUM DEVELOPMENT TEAM...
Responsible for delivering a potentially shippable
increment of working software.

Self Organized

Cross Functional

Defines Practice

3 to 9 Persons

Team Player
 AS A SCRUM MASTER YOU

Explain Agile Advise and Facilitate Coach and

coach change Remove impediments

...........

...........
...........

...........
PRODUCT OWNER ORGANISATION

STAKEHOLDERS DEVELOPMENT TEAM

 Supporting Role

Product Owner Team

A team that help Product Owner to maximizing the value of the product. Product Owner Team can
consist of business analyst, UX \ CX designer, growth hacking, etc that appropriate to help the Product
Owner

Stakeholder
A person or group of peoples in organization who frequently interface with the Scrum Team to
provide them with inputs and facilitate creation of the project's products and services, influencing the
project throughout the project's development and valuable feedback

Subject Matter Experts

A person or group of peoples, external to the Team, with special knowledge or skills that the Team
needs in order to do its work.
 Scrum Artifact

Video

Potentially Shippable
Product Backlog Sprint Backlog
Increment
 Product Backlog
What is Product Backlog
The Product Backlog is an ordered list of everything that is known to be needed in the product. It is
the single source of requirements for any changes to be made to the product

Owned by
Product Owner

High

}
Product Backlog
Fine-grained, detailed items ready For
consumption in the next iteration, i.e.,
small user stories

}
Priority

Medium-grained items, i.e.,

larger user stories

}
Coarse-grained
items, i.e., epics

Low
 Sprint Backlog
What is Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for
delivering the product Increment and realizing the Sprint Goal

Owned by
Development Team
 Potentially Shippable Increment
What is Potentially Shippable Increment
The Increment is the sum of all the Product Backlog items completed during a Sprint and the value
of the increments of all previous Sprints

Owned by
Product Owner

Vision Continue
Iteration 1 Iteration Iteration Iteration
2 3 4
 Definition of Ready & Definition of Done
DEFINITION OF READY (DOR)
Refers to a list of conditions that
must be fulfilled before a Product
Backlog Item (PBI) is considered
ready for a Sprint. The goal is to
ensure that everything is in place
before starting to prevent issues.
The Development Team should
discuss and define the definition
of ready during Sprint 0 and revisit
at every Sprint Planning session.
DEFINITION OF DONE (DOD)
Is a checklist that the team is
expected to complete by the end of
the Sprint, before it can declare its
work to be potentially shippable
SPRINT - that the work is designed,
developed, tested, documented,
and will deliver business value. The
Development Team should confirm
the Definition of Done before each
sprint execution.
 Supporting Artifact
Scrum Board
Physical or virtual board that include all the backlog that need to be done during the sprint. Scrum
Board need to be accessible and visualize to all Scrum Team to encourage Transparency and
openness.

Burndown Chart
A burndown chart is a graphical representation of work left to do versus time
 Supporting Artifact

Impediment List
The list that include all the team impediment, and how to escalate & resolve it.
Impediment list owned by Scrum Master
 Thank You

Agile Mindset & Manifesto

Basic Scrum Framework

Video /
Photo
Scrum Event

Scrum Role

Angga Pratama Scrum Artifact

Senior Agile Coach - Ekipa