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
Tetsuya Taguchi
July 24, 2016
Technology
1
83
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
110
わかりやすいブログを書くためにはどうすればよいか?
tetsuyataguchi
1
150
Nginxによるリバースプロキシ
tetsuyataguchi
0
550
Chef
tetsuyataguchi
0
43
Docker Pi
tetsuyataguchi
0
120
新卒エンジニアから見たデータセンター移行
tetsuyataguchi
0
1.1k
スクラム開発の広め方
tetsuyataguchi
4
1.1k
Denki de Tenki
tetsuyataguchi
1
250
ポチベル
tetsuyataguchi
1
990
Other Decks in Technology
See All in Technology
今年のRubyKaigiはProfiler Year🤘
osyoyu
0
490
一生覚えておきたい「システム開発=コミュニケーション」〜初めての実務案件振り返りLT〜
maimyyym
3
410
今日からできる!簡単 .NET 高速化 Tips -2024 edition-
xin9le
7
4.6k
生成AIの変革の時代に、直近1年で直面した課題とその解決策
ktc_wada
1
750
Building a RAG-poweredAI chat appwith Python and VS Code
pamelafox
0
170
いいたいことちゃんという
tkengo
0
260
自己改善からチームを動かす! 「セルフエンジニアリングマネージャー」のすゝめ
shoota
6
1.1k
AWS学習者向けにAzureの解説スライドを作成した話
handy
3
210
【基本】データベース設計
oracle4engineer
PRO
2
250
類似ロジック実装をiOS/Android間で合わせる道標No.1
fumiyasac0921
0
110
社内アプリで Cloudflare D1を プロダクト運用してみた体験談(Tokyo)
haochenx
0
130
Babylon.js JAPAN活動紹介 (2024/4)
limes2018
1
120
Featured
See All Featured
5 minutes of I Can Smell Your CMS
philhawksworth
199
19k
Rails Girls Zürich Keynote
gr2m
91
13k
KATA
mclloyd
16
12k
Clear Off the Table
cherdarchuk
85
310k
Optimising Largest Contentful Paint
csswizardry
13
2.4k
GraphQLの誤解/rethinking-graphql
sonatard
56
9.3k
Designing with Data
zakiwarfel
96
4.8k
The Brand Is Dead. Long Live the Brand.
mthomps
49
29k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
188
16k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
9
1.3k
Building Flexible Design Systems
yeseniaperezcruz
320
37k
StorybookのUI Testing Handbookを読んだ
zakiyama
13
4.6k
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