Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
The basic of Scrum
Search
Sponsored
·
Ship Features Fearlessly
Turn features on and off without deploys. Used by thousands of Ruby developers.
→
Tetsuya Taguchi
July 24, 2016
Technology
1
97
The basic of Scrum
The basic of Scrum
Tetsuya Taguchi
July 24, 2016
Tweet
Share
More Decks by Tetsuya Taguchi
See All by Tetsuya Taguchi
どのようにマネージャーを育成するか?
tetsuyataguchi
0
140
わかりやすいブログを書くためにはどうすればよいか?
tetsuyataguchi
1
260
Nginxによるリバースプロキシ
tetsuyataguchi
0
580
Chef
tetsuyataguchi
0
58
Docker Pi
tetsuyataguchi
0
140
新卒エンジニアから見たデータセンター移行
tetsuyataguchi
0
1.2k
スクラム開発の広め方
tetsuyataguchi
4
1.2k
Denki de Tenki
tetsuyataguchi
1
350
ポチベル
tetsuyataguchi
1
1k
Other Decks in Technology
See All in Technology
What happened to RubyGems and what can we learn?
mikemcquaid
0
300
Red Hat OpenStack Services on OpenShift
tamemiya
0
110
SREチームをどう作り、どう育てるか ― Findy横断SREのマネジメント
rvirus0817
0
260
ZOZOにおけるAI活用の現在 ~開発組織全体での取り組みと試行錯誤~
zozotech
PRO
5
5.5k
Frontier Agents (Kiro autonomous agent / AWS Security Agent / AWS DevOps Agent) の紹介
msysh
3
170
顧客との商談議事録をみんなで読んで顧客解像度を上げよう
shibayu36
0
240
Bill One急成長の舞台裏 開発組織が直面した失敗と教訓
sansantech
PRO
2
380
小さく始めるBCP ― 多プロダクト環境で始める最初の一歩
kekke_n
1
420
Context Engineeringが企業で不可欠になる理由
hirosatogamo
PRO
3
590
30万人の同時アクセスに耐えたい!新サービスの盤石なリリースを支える負荷試験 / SRE Kaigi 2026
genda
4
1.3k
Oracle Cloud Observability and Management Platform - OCI 運用監視サービス概要 -
oracle4engineer
PRO
2
14k
AI駆動開発を事業のコアに置く
tasukuonizawa
1
200
Featured
See All Featured
VelocityConf: Rendering Performance Case Studies
addyosmani
333
24k
Test your architecture with Archunit
thirion
1
2.2k
The Language of Interfaces
destraynor
162
26k
Typedesign – Prime Four
hannesfritz
42
2.9k
Digital Ethics as a Driver of Design Innovation
axbom
PRO
1
180
DevOps and Value Stream Thinking: Enabling flow, efficiency and business value
helenjbeal
1
94
Winning Ecommerce Organic Search in an AI Era - #searchnstuff2025
aleyda
1
1.9k
The Power of CSS Pseudo Elements
geoffreycrofte
80
6.2k
How to Get Subject Matter Experts Bought In and Actively Contributing to SEO & PR Initiatives.
livdayseo
0
66
Principles of Awesome APIs and How to Build Them.
keavy
128
17k
Public Speaking Without Barfing On Your Shoes - THAT 2023
reverentgeek
1
310
Noah Learner - AI + Me: how we built a GSC Bulk Export data pipeline
techseoconnect
PRO
0
110
Transcript
The basic of Scrum 22/7/2016 Tetsuya Taguchi
Scrum is • Productively and creatively delivering products of the
highest possible value.
Scrum is • People can address complex adaptive problems.
Scrum is • Lightweight • Simple to understand • Difficult
to master
None
Planning is adaptive
Development is iterative
Product Backlog • An ordered list of everything that might
be needed in the product.
Product Owner • Responsible for managing the Product Backlog. •
Ordering the items in the Product Backlog to best achieve goals and missions.
Development Team • Delivering a potentially releasable Increment.
Roles blur
Self-organizing • No one tells the Development Team how to
turn Product Backlog into Increments of potentially releasable functionality.
Sprint • Consistent durations throughout a development effort.
Sprint Planning
Sprint Planning
Sprint Backlog • Set of Product Backlog items selected for
the Sprint
Increment • Sum of all the Product Backlog items completed
during a Sprint • It must be in useable condition. • It must be “Done”
Definition of “Done” • Everyone must understand what “Done” means.
Daily Scrum • To synchronize activities
Daily Scrum • To inspect progress toward the Sprint Goal.
• To improve communications • To improve Development Team's level of knowledge.
Daily Scrum • Held at the same time and place
each day. • A 15-minute time-boxed event. • What did I do yesterday • What will I do today • What is my problems
Sprint Review • The Development Team demonstrates the work that
it has “Done”. • Answers questions about the Increment.
Working software is the primary measure of success
Sprint Review
Scope can vary
Sprint Retrospective • To inspect itself • To create a
plan for improvements to be enacted during the next Sprint.
Scrum Master • is responsible for ensuring Scrum is understood
and enacted. • is a servant-leader for the Scrum Team.
None
Reference • http://www.scrumguides.org/ • http://www.slideshare.net/Ryuzee/ scrum-14271224 • http://www.agilenutshell.com/ how_is_it_different •
http://www.informit.com/articles/ article.aspx?p=1928232&seqNum=3