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
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Tetsuya Taguchi
July 24, 2016
Technology
120
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
The basic of Scrum
The basic of Scrum
Tetsuya Taguchi
July 24, 2016
More Decks by Tetsuya Taguchi
See All by Tetsuya Taguchi
どのようにマネージャーを育成するか?
tetsuyataguchi
0
160
わかりやすいブログを書くためにはどうすればよいか?
tetsuyataguchi
1
290
Nginxによるリバースプロキシ
tetsuyataguchi
0
590
Chef
tetsuyataguchi
0
82
Docker Pi
tetsuyataguchi
0
170
新卒エンジニアから見たデータセンター移行
tetsuyataguchi
0
1.2k
スクラム開発の広め方
tetsuyataguchi
4
1.2k
Denki de Tenki
tetsuyataguchi
1
370
ポチベル
tetsuyataguchi
1
1.1k
Other Decks in Technology
See All in Technology
Sony-DroidKaigi2026
sony
1
310
なぜSRE・セキュリティは評価されないのか?守りの組織を事業成長エンジンに変えた実践
cscengineer
PRO
2
2.1k
はじめてのDatabricks:技術者向けワークショップ / beginner-workshop
databricksjapan
PRO
0
140
Guerilla InnerSource in enterprises, during the AI hype
onenashev
PRO
0
150
#jawssonic2026 あの時代が悪かった ~動かなかったSageMakerと共に迎えたイベント当日~
ktkn1129
0
130
AI時代におけるプロダクト横断勉強会の設計
zozotech
PRO
0
150
Webとヘルスデータ
yukukotani
0
170
Azure App Service / Container Apps の組み込み認証
kuniteru
0
190
リージョンの壁を越える、 ちょっと変わったAWSサービスの話
falken
PRO
0
200
When Token Pruning is Worse than Random: Understanding Visual Token Information in VLLMs
sansantech
PRO
0
250
Bet AI Day 2026丨AIによって本質に戻るシステムリスク管理
layerx
PRO
0
790
作り直せるコードは迅速に 作り直せないDBは慎重に - AI時代のプロダクトエンジニアが「判断の不可逆性」で開発速度を変える話
kinosuke01
0
190
Featured
See All Featured
Why Mistakes Are the Best Teachers: Turning Failure into a Pathway for Growth
auna
0
240
The Art of Programming - Codeland 2020
erikaheidi
57
14k
How to Get Subject Matter Experts Bought In and Actively Contributing to SEO & PR Initiatives.
livdayseo
0
180
Intergalactic Javascript Robots from Outer Space
tanoku
273
27k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
12
1.8k
Java REST API Framework Comparison - PWX 2021
mraible
34
9.7k
The Straight Up "How To Draw Better" Workshop
denniskardys
239
140k
The Hidden Cost of Media on the Web [PixelPalooza 2025]
tammyeverts
2
490
Reality Check: Gamification 10 Years Later
codingconduct
0
2.3k
HDC tutorial
michielstock
2
840
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
16
2.1k
Test your architecture with Archunit
thirion
2
2.4k
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