Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
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
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
84
Docker Pi
tetsuyataguchi
0
170
新卒エンジニアから見たデータセンター移行
tetsuyataguchi
0
1.2k
スクラム開発の広め方
tetsuyataguchi
4
1.2k
Denki de Tenki
tetsuyataguchi
1
380
ポチベル
tetsuyataguchi
1
1.1k
Other Decks in Technology
See All in Technology
.NET WebAssemblyで実現するクライアントサイドAI推論:NuGetからViteまで、2つのエコシステムを繋ぐビルド戦略
yamachu
1
950
Azure Copilot Resiliency Agentをいろいろ試してみる
tomokusaba
0
110
AIエージェントを安全で速い現場監督にする:Jev・Obsidian・メタハーネス
x5gtrn
PRO
0
130
C#未経験の僕がAIに読めるコードを書かせるまで
maguroalternative
0
330
なぜ「決定性」が 決定的に重要なのか? Durable Execution 基盤の数理的理解 #serverlessjp / ServerlessDays Tokyo 2026
ytaka23
4
1.3k
Claude Codeを「使うほど育つ」AI秘書にするノウハウ
minorun365
PRO
32
33k
Goodbye ShellScript, Hello File-based App
shunsock
0
1.2k
エージェントはローカル、検証はMicroVM — Lambda MicroVMsでつくるServerless CI
fujioka6789
3
830
ADKで始める業務改善 - AIエージェント開発時の考えと設計
harappa80
2
300
手を動かして実感する、Kiro が変える開発体験
inariku
0
390
AI Agent入門〜今更聞けないAgentの話〜
hiromimaganuma
0
120
HolmesGPTで始めるSREエージェント入門!プラットフォームの障害調査はAIにお任せ 〜
sanghyuk
0
220
Featured
See All Featured
Statistics for Hackers
jakevdp
799
230k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
141
35k
SERP Conf. Vienna - Web Accessibility: Optimizing for Inclusivity and SEO
sarafernandez
2
1.6k
Building AI with AI
inesmontani
PRO
1
1.3k
Lessons Learnt from Crawling 1000+ Websites
charlesmeaden
PRO
1
1.6k
Leadership Guide Workshop - DevTernity 2021
reverentgeek
1
370
WENDY [Excerpt]
tessaabrams
14
39k
The Cost Of JavaScript in 2023
addyosmani
55
10k
Practical Orchestrator
shlominoach
192
12k
Reality Check: Gamification 10 Years Later
codingconduct
0
2.3k
Documentation Writing (for coders)
carmenintech
77
5.5k
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
11
1k
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