Scribd
Upload
301 views26 pages

Scrum Keynote

This document provides an overview of Scrum, an agile framework for delivering work incrementally in sprints. It describes Scrum roles like the Product Owner, Scrum Master, and self-organizing cross-functional team. Key Scrum ceremonies are covered such as sprint planning, daily stand-ups, sprint reviews, and retrospectives. Scrum artifacts like the product backlog, sprint backlog, and burndown charts are also summarized. Finally, it discusses how Scrum can scale to larger projects through coordination of multiple Scrum teams.

Uploaded by

Samy Hawi
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
301 views26 pages

Scrum Keynote

This document provides an overview of Scrum, an agile framework for delivering work incrementally in sprints. It describes Scrum roles like the Product Owner, Scrum Master, and self-organizing cross-functional team. Key Scrum ceremonies are covered such as sprint planning, daily stand-ups, sprint reviews, and retrospectives. Scrum artifacts like the product backlog, sprint backlog, and burndown charts are also summarized. Finally, it discusses how Scrum can scale to larger projects through coordination of multiple Scrum teams.

Uploaded by

Samy Hawi
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/ 26

Scrum at Chip

Agenda

❖ Scrum Summed Up

❖ Scrum Roles & Responsibilities

❖ Scrum Ceremonies

❖ Scrum Artefacts

❖ Scrum at Scale
Scrum Summed Up
❖ Agile framework that focuses on delivering business
value incrementally (every 2 weeks).

❖ Teams - not individuals - accept responsibility for


their achievements and failures.

❖ Encourages constant reflection and growth.

❖ Allows teams to be more responsive to change.

❖ Works well with DevOps, CI / CD.


The Agile Manifesto–a
statement of values
Individuals and over Process and tools
interactions

Comprehensive
Working software over
documentation

Customer over Contract negotiation


collaboration

Responding to change over Following a plan

Source: www.agilemanifesto.org
Waterfall vs Agile

Value of Delivery
Risk of failure
Scrum 24 hours

2 week
Sprints
Sprint goal

New Saves
Sprint Potentially shippable
backlog product increment

Checkout

Service Goals
KYC
Product
backlog
No changes during a sprint

Change

• Plan sprint durations around how long you can


commit to keeping change out of the sprint
Scrum framework
Roles
• Product Owner
• Scrum Master
• Dev Team Ceremonies
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily scrum meeting
Artefacts
• Product backlog
• Sprint backlog
• Burndown charts
Scrum framework
Roles
• Product Owner
• Scrum Master
• Dev Team Ceremonies
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily scrum meeting
Artefacts
• Product backlog
• Sprint backlog
• Burndown charts
Product owner
• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the
product (ROI)
• Prioritise features according to market value
• Adjust features and priority every iteration, as
needed 
• Accept or reject work results
The Scrum Master
• Responsible for enacting Scrum values and
practices
• Removes impediments
• Ensure that the team is fully functional and
productive
• Enable close cooperation across all roles and
functions (including stakeholders)
• Shield the team from external interferences
• Represents management to the project
The team
• Typically 5-9 people
• Cross-functional:
• Programmers, testers, user experience designers, etc.
• Members should be full-time
• May be exceptions (e.g., database administrator)
• Teams are self-organising
• Ideally, no titles but rarely a possibility
• Membership should change only between sprints
Scrum framework
Roles
• Product Owner
• Scrum Master
• Dev Team
Ceremonies
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily scrum meeting
Artefacts
• Product backlog
• Sprint backlog
• Burndown charts
The daily scrum
• Parameters
• Daily
• 15-minutes
• Stand-up
• Not for problem solving
• Whole world is invited
• Only team members, Scrum Master and Product
Owner can talk
• Helps avoid other unnecessary meetings
Everyone answers 3 questions
1
What did you do yesterday?

2
What will you do today?

3
Is anything in your way?

• These are not a status update for the ScrumMaster


• They are commitments in front of peers
Sprint planning
• Team selects items from the product backlog they can
commit to completing
• Sprint backlog is created
• Tasks are identified and each is estimated
• Collaboratively, not done alone by the ScrumMaster
• High-level design is considered
As a Chip user, I want [iOS] Create tab for goals (2)
to be able to set up a [iOS] Build create goal functionality (3)
[Android] Create tab for goals (2)
goal, so that I can [Android] Build create goal functionality (3)
achieve my financial [Backend] Build goals functionality Rhillor
(13)
goals with Chip.
The sprint review
• Team present what they have accomplished in
the past sprint
• Typically takes the form of a demo of new
features or underlying architecture
• Informal
• Whole team participates
• Invite the world
Sprint retrospective
• Periodically take a look at what is and is not
working
• Typically 30– 45 minutes
• Done after every sprint
• Whole team participates
• Scrum Master
• Product Owner
• Team
Start / Stop / Continue
• Whole team gathers and discusses what they’d
like to:
Start doing

Stop doing
This is just one
of many ways Continue doing
to do a sprint
retrospective.
Scrum framework
Roles
• Product Owner
• Scrum Master
• Dev Team Ceremonies
• Sprint planning
• Sprint review
• Sprint retrospective
• Daily scrum meeting
Artefacts
• Product backlog
• Sprint backlog
• Burndown charts
Product backlog
Sprint backlog
Burndown chart
Scalability
• Typical individual team is 7 ± 2 people
• Scalability comes from teams of teams
• Factors in scaling
• Type of application
• Team size
• Team dispersion
• Scrum has been used on multiple 500+ person
projects
Scaling through the Scrum
of scrums

You might also like