Scrum Master

Course 02 - Introduction to Scrum

Slide 1

Introduction to Scrum

Topics Covered

What is Scrum

Key Principles

Course

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 2

Learning Objectives

• You will learn

– The reasons for Agile Development methods

– The benefits of Scrum

– The 6 Key Scrum Principles

– The 5 Scrum Aspects

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 3

Terms to Know

• Adaptation

• Agile Manifesto

• Information Radiator

• Inspection

• Portfolio

• Program

• Project

• Scrum

• Scrum Guidance Body

• Time-boxing

• Transparency

• Waterfall

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 4

Scrum Overview

Topics Discussed

Overview

History

Benefits

Scalability

Aspects

Processes

Topic

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 5

Scrum Overview

• Projects are a management tool

– Manage resources

• People

• Time

– Produce products or services that deliver value to stakeholders

– Require engagement of multiple groups of stakeholders

– Produce “artifacts” and “deliverables”

– Project Management Frameworks provide

• Structure

• Control

• Management

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 6

Project Management as a Discipline

• Project Management is a discipline

– Planning

– Organizing

– Motivating

– Control of resources

• Project Management achieves a specific goal

InitiationPlan

& Design

ExecuteMonitor

& ControlClose/Com

plete?

A traditional phased approach identifies a sequence of steps to be completed. In the "traditional approach.” there are five developmental components of a project (four stages plus control):1. initiation2. planning and design3. execution and construction4. monitoring and controlling systems5. completion

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 7

Software Development Lifecycle Management

• Execute projects and integrate software solutions

• Combines requirements, design, development (or

acquisition), integration testing, validation, and (possibly)

deployment

• Produces a product or service with a lifecycle of its own

• Product or service changes as business and customer

needs change

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 8

Traditional PM

• Based on a delegation

approach (that includes

waterfall)

• Places more value on

planning than outcomes

• Not the best method for

software development

– Predictive not adaptive

– Doesn’t easily

accommodate rate of

change

– Elapsed calendar time

doesn’t equate to percent

complete

Requirements

Design

Development

Integration

Testing

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 9

Agile History

• Agile Manifesto – February 2001

• Resetting the Value Proposition

We value these more than the items on the right

We value these, but not as much as the items on the left

Individuals and Interactions Processes and Tools

Working Software Comprehensive Documentation

Customer Collaboration Contract Negotiation

Response to Change Following a Plan

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 10

Agile Manifesto Principles 1-5

• Customer satisfaction is the highest priority

– Achieved through early & continuous delivery of valuable

software

• Accommodating change provides the customer with a

competitive advantage.

• Deliver working software frequently

– Within short time frames

• Business people and developers work together daily

• Build projects around motivated individuals.

– Give them the environment and support they need

– Trust them to get the job done.

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 11

Agile Manifesto Principles 6-12

• Face-to-face conversation

– Most efficient and effective way to communicate with & within the

development team.

• Working software is the primary measure of progress

• Agile processes promote sustainable development

– Sponsors, developers, and users should maintain a constant pace

indefinitely

• Continuous attention to technical excellence enhances agility

• Simplicity is essential

– Maximize the amount of work not done

• The best architectures, requirements, and designs emerge

from self-organizing teams

• Teams reflect regularly on how to become more effective, and

adjusts their behavior accordingly

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 12

Agile Methods

• Many Agile methods exist, with different areas of

emphasis

– Lean Kanban

– Extreme Programming (XP)

– Crystal

– Dynamic Systems Development Method (DSDM)

– Feature Driven Development (FDD)

– Test Driven Development (TDD)

– Adaptive Software Development (ASD)

– Agile Unified Process (AUP)

– Domain-Driven Design (DDD)

• In the course, we will focus on Scrum, which leverages

techniques from many of the others

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 13

Scrum History

• Begins in 1980s with Takeuchi and Nonaka

– Working as a team – a holistic or “rugby” approach vs a relay

race (‘passing the baton”)

• Expanded in 1995 by Schwaber and Sutherland

– Initial proposal of what would become the Scrum approach

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 14

Scrum Benefits

• Scrum provides– Adaptability

– Transparency

– Continuous feedback

– Continuous Improvement

– Continuous Delivery of Value

– Sustainable Pace

– Early Delivery of High Value

– Efficient Development Process

– Motivation

– Faster Problem Resolution

– Effective Deliverables

– Customer Centric

– High Trust Environment

– Collective Ownership

– High Velocity

– Innovative Environment

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 15

Scrum Scalability

• Effective Scrum teams are 6-10 members

• Scrums of Scrums enable scalability to larger scope

projects, programs, and portfolios

• Use of a Scrum Guidance Body

Standard for 1 Meter1 Meter = 1,650,763.73

wavelengths of light from a specific transition in krypton 86

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 16

Scrum Concepts & Principles

Topics Discussed

Concepts

Principles

Aspects

Topic

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 17

Scrum Principles

• Empirical Process Control

• Self-organization

• Collaboration

• Value-based Prioritization

• Time-boxing

• Iterative Development

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 18

Empirical Process Control

• Transparency – All facets of a Scrum process can be

observed by anyone

– Meetings

– Artifacts

– Information Radiators

• Inspection – Constant means of feedback from

stakeholders

• Adaptation – Through Inspection we then adapt solutions

to meet evolving customer needs

– Quality

– Risk

– Change

– Expert Guidance

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 19

Self-Organization

• Scrum is grounded in self-organization: participants seek

and take greater responsibility

• Leadership approach is based on “servant leaders”

– Scrum Master as coach, facilitator, team protector

• Seeks to create

– Team buy-in and shared ownership

– Motivation, which drives improved performance

– Innovative, creative environment conducive to growth

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 20

Collaboration

• Play off each other to produce outputs greater than the

sum of the parts

• Core dimensions are

– Awareness – Visibility into one another’s work

– Articulation – Partitioning and re-integration of work

– Appropriation – Adapt technology to fit the situation

• Drives

– Clarification of requirements

– Reduced need for Change

– Risk Identification and Mitigation

– Continual Improvement

• Colocation Preferred

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 21

Value-Based Prioritization

• Focus on ongoing prioritization of features and

capabilities based on business value

• Uses Prioritized Product Backlog as the basis for Sprint

Planning and value delivery

• Considers

– Value to the business

– Risk

– Dependencies

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 22

Time-Boxing

• Time is valuable!

• Many Scrum activities are intentionally constrained to a particular amount of time

• Benefits include– Efficient Development

– Less Overhead

– High(er) velocity for team performance

• Scrum Time-boxes– Sprint – 1-6 weeks

– Daily Standup Meeting – 15 minutes

– Sprint Planning Meeting – 4 hours for 2 week Sprint, 8 hours for one month Sprint

– Sprint Review Meeting – 2 hours for 2 week Sprint, 4 hours for one month Sprint

– Retrospect Sprint Meeting – 2 hours for 2 week Sprint, 4 hours for one month Sprint

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 23

Iterative Development

• Iterative models reflect real-world issues with

development

– Requirements change

• Changes might lead to reprioritization

– Higher value deliverables are delivered sooner

– Risks identified and mitigated sooner

• By using iterative development, we acknowledge these

“moving targets” and work to keep the team constantly

focused on delivering optimized business value

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 24

Scrum Aspects

• Organization

• Business Justification

• Quality

• Change

• Risk

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 25

Scrum Phases & Processes

Topics Discussed

Initiate

Plan & Estimate

Implement

Review & Retrospect

Release

Topic

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 26

Scrum Phases

• Initiate

• Plan & Estimate

• Implement

• Review & Retrospect

• Release

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 27

Initiate

• Create Product Vision

• Identify Scrum Master and Stakeholders

• Form Scrum Team

• Develop Epic(s)

• Create Prioritized Product Backlog

• Conduct Release Planning

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 28

Plan & Estimate

• Create User Stories

• Approve, Estimate, and Commit User Stories

• Create Tasks

• Estimate Tasks

• Create Sprint Backlog

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 29

Implement

• Create Deliverables

• Conduct Daily Standup

• Groom Prioritized Product Backlog

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 30

Review & Retrospect

• Convene Scrum of Scrums

• Demonstrate and Validate Sprint

• Retrospect Sprint

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 31

Release

• Ship deliverables

• Retrospect Project

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 32

Introduction to Scrum Summary

Topics Discussed

What is Scrum

Benefits

Scalability

Key Principles

Aspects

Phases & ProcessesSummary

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 33

Introduction to Scrum Summary

• What is Scrum

• Benefits

• Scalability

• Key Principles

• Aspects

• Processes

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Slide 34

Course Quiz

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Review Questions:

1. Which of the following is NOT a Scrum principle?

A. Self-organizing teams

B. Value-based prioritization

C. Continued business-based justification

D. Self-organizing teams

2. Why is Empirical Process Control (EPC) vitally important to Scrum?

A. Visibility means artifacts are visible to everyone with a stake in the

outcomes. There is a common language and agreement to what

constitutes, Done. Inspecting everything builds quality into the

development process by measuring current against expectation. If

inspection reveals an out of tolerance area, appropriate changes can be

made

B. EPC is the basis for planning Sprints, the Daily Standup and the

review/retrospect processes

C. EPC is no more critical to Scrum than any of the other principles

D. The real focus of EPC is common language and process understanding. It

is the basis of the organizational change that is required for successful

Scrum efforts

3. You are the Scrum Master on a project; what, if any, are the differences in team

selection compared to traditional project management?

A. There isn't really a difference, both approaches to project management

(traditional and Scrum) use cross-functional teams

B. Scrum requires the use of specially trained developers who understand

Scrum processes

C. Because there is no project manager on a Scrum project, team selection

doesn't require the same formal approvals as traditional project

management

D. Traditional project management schedules resources and capabilities

while scrum efforts focus on more to include building collaborating teams

4. What is the focus of the tasks that are created in the Create Tasks process (part

of the Plan & Estimate phase)?

A. The tasks are focused on what it will take to estimate the effort

B. The tasks are focused on decomposing epics into estimate-able stories

C. The tasks define what is required to create the deliverables for the Sprint

D. Create Tasks focuses on both defining tasks to estimate the effort and

assigning ownership for them

5. What is the difference between the product backlog and the Sprint backlog?

A. The Sprint backlog contains an overall description of work; the product

backlog is the effort within a timebox

B. The Sprint backlog contains the work for a specific timebox; the product

backlog is the description of the overall work

C. The Sprint backlog contains stories for the Sprint; the product backlog

contains all stories

D. The Sprint backlog contains all stories; the product backlog contains

stories for a Sprint

Answer Key:

1. C

While C is important, it's not a specific Scrum principle; it is part of value-based

prioritization.

2. A

While there is an element of truth in answers B through D, answer A is the only

one that focuses on all three elements of EPC.

3. D

Team selection in Scrum focuses on more to include building collaborating

teams.

4. A

While there may be elements of B included, the overall effort is determining what

the team can handle in this Sprint -- estimating what it can do.

5. B

The Sprint Backlog shows the stories and tasks committed for "this" Sprint. The

product backlog is a prioritized list of all stories (and epics) for the project.