SCRUM Framework

Created by :

Dhona Arytama – CSM (Certificate ID 000556817)

 BIODATA

• Dhona Arytama (Ary)

• Married, have 2 sons
• Graduation from University of Indonesia
• Professional working experience around 16
years at IT project (network, system,
application)
• Professional trainer motivation, education,
team work, soft skill, project management
• As Delivery Head
Agreement

• Phones on silent, take calls outside

• All participant must be active
• It is OK to be wrong, learn from mistakes
GOAL

Have good knowledge about Scrum

Implementation Scrum on project properly

 AGENDA

PROJECT KNOWLEDGE TRIPLE CONSTRAINT SCRUM FRAMEWORK

1. Project definition 1. Triple constraint project 1. Scrum definition

2. Product & project 2. Mind mapping :
scope Scrum Values
3. Type structure Roles
project Events
Artifact
3. DOD
PROJECT KNOWLEDGE - Project Definition

A project is a temporary
endeavor undertaken to
create a unique product,
service, or result

TEMPORARY
FINISH
PRODUCT
START OR or
PROCESS
SERVICES
STOP
P.K- Product & Project Scope
P.K - Type Structure Project
P.K - Type Structure Project
Project Life Cycle

Software Development Life Cycle (SDLC)

• Includes implementation preparation,
• Perform application development to meet implementation of the system into
business requirements production environment, and resolution of
• convert a design into complete information the problems identified in the integration
system include acquiring and installing and test phases
systems environment, creating and testing
databases
• Perform procurement activities 6 7. Operation,
• Perform Quality Assurance (preparing test Maintenance and
case procedure, test files, coding, refining Closing
program, readiness review)
6. Implementation
4 7
• Discover detailed business requirement and
solutions 5. Testing • Describe tasks to operate and maintain
• Define the goals for a single / Multiple
implementation phase • Analyses user needs and create detailed information systems in a production
• Concept of proposal is created requirement document environment. include post implementation
• Define the scope or Boundary of the 4. Build and in-process reviews
Concepts 5 • Conduct training, and perform help desk
2
• Develop project plan and other planning • describe end-of system activities, emphasis
documents 3. Design • Validate the application for appropriate is given to proper preparation of data
implementation of business processes
1 • Demonstrates that developed system
2. Analysis conforms to requirements as specified in
3 the requirements document, conducted by
quality assurance staff and users.
1. Initiating and • Design solutions created to the business • Produces test analysis reports
Planning requirements
• Transform detailed requirements into
complete, detailed systems design
document focuses on how the deliver the
required functionality
Triple Constraint Project

Manage QUALITY :
1. People
2. Process
3. Equipment
S.F - Scrum Definition
Scrum is a framework within which people can address complex adaptive problems,
while productively and creatively delivering products of the highest possible value.

Scrum is:

Lightweight
Simple to understand
Difficult to master
S.F – 5 Scrum Value
For agility to thrive, the culture of the organization must support the fundamental concepts of agility. A practitioner will
understand both the Scrum Values - Focus, Respect, Openness, Commitment, and Courage - and demonstrate that they
can apply them in the reality of organizations whose values do not match those of Scrum. By living the Scrum Values and
helping others to apply them, learners will create an environment where empirical process, self- organization, and
continual improvement will be more successful.

Focus : Everyone focus on the work of the sprint and the goals of the scrum
Focus Respect Respect : Scrum team member respect each other to be capable, independent people
Openness : The scrum team and its stakeholder agree to be open about at the work and the challenges
with performing the work
Courage : Scrum team member have courage to do the right thing and work on tough problems
Openness Courage Commitment : People personally commit to achieving the goals of the scrum team

Commitment
S.F – 3 Roles
Development Team :
Product Owner Product Owner :
Characteristic :
Characteristic : 1. Cross-functional
1. Owner of the product 2. 5 to 9 people
2. Authority over product decisions 3. Organizes and manages itself and its work
Development
3. Accountable for the success of the product 4. Stable, full-time, dedicated
Team
5. No titles
Responsibilities : 6. T-Shaped, generalizing specialist
1. Define product features
Scrum Master 2. Prioritize features according to market value Responsibilities :
3. Decides release dates & content 1. Decide how the work is to be performed (how)
4. Adjust features & priority every iteration, as needed 2. Estimate how much effort is needed
5. Accept or reject work result 3. Delivery to commitment every sprint
Scrum Master:
4. Review work result with the Product Owner
5. Improve effectiveness in delivering value
Characteristic :
1. Shield team from external interferences
2. Encourage team communication

Responsibilities :
1. Daily scrum standup meeting
2. Board update with team
3. Review backlog with team
4. Sprint Planning/ Review with team
5. Sizing session with team
6. Story splitting session
S.F – 5 Events

Sprint Planning Daily Scrum Event Scrum Definition

Sprint Planning Is an event in the Scrum framework where the team determines the
product backlog items they will work on during that sprint and discusses
their initial plan for completing those product backlog items.

Sprint Review Sprint Daily Scrum The Daily Scrum is a 15-minute time-boxed event for the Development
Retrospective Team to synchronize activities and create a plan for the next 24 hours

Sprint Review Is an informal meeting which the development team, the scrum master,
the product owner and the stakeholders will attend. The team gives a
Product Backlog demo on the product and will determine what are finished and what
aren't.
Refinement
Sprint Retrospective The Sprint Retrospective occurs after the Sprint Review and prior to
the next Sprint Planning. This is at most a three-hour meeting for one-
month Sprints

Product Backlog Product Backlog refinement is the act of adding detail, estimates and
Refinement order to items in the Product Backlog
S.F – 3 Artifact
Product Backlog Artifact Definition

Product Backlog A product backlog is a list of the new features, changes to

existing features, bug fixes, infrastructure changes or other
activities that a team may deliver in order to achieve a
Sprint Backlog specific outcome.

Sprint Backlog The sprint backlog is a list of tasks identified by

the Scrum team to be completed during the Scrum sprint.
Increment During the sprint planning meeting, the team selects some
number of product backlog items, usually in the form of
user stories, and identifies the tasks necessary to complete
each user story.

Increment increment is the process of increasing by a specific

amount, or the amount by which something increases.
Thank You!