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
87
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
120
わかりやすいブログを書くためにはどうすればよいか?
tetsuyataguchi
1
190
Nginxによるリバースプロキシ
tetsuyataguchi
0
560
Chef
tetsuyataguchi
0
50
Docker Pi
tetsuyataguchi
0
130
新卒エンジニアから見たデータセンター移行
tetsuyataguchi
0
1.2k
スクラム開発の広め方
tetsuyataguchi
4
1.1k
Denki de Tenki
tetsuyataguchi
1
300
ポチベル
tetsuyataguchi
1
1k
Other Decks in Technology
See All in Technology
Kotlin Multiplatformのポテンシャル
recruitengineers
PRO
2
150
.NET 最新アップデート ~ AI とクラウド時代のアプリモダナイゼーション
chack411
0
200
Oracle Base Database Service:サービス概要のご紹介
oracle4engineer
PRO
1
16k
JAWS-UG20250116_iOSアプリエンジニアがAWSreInventに行ってきた(真面目編)
totokit4
0
140
新卒1年目、はじめてのアプリケーションサーバー【IBM WebSphere Liberty】
ktgrryt
0
140
JuliaTokaiとJuliaLangJaの紹介 for NGK2025S
antimon2
1
130
Amazon Route 53, 待ちに待った TLSAレコードのサポート開始
kenichinakamura
0
180
GoogleのAIエージェント論 Authors: Julia Wiesinger, Patrick Marlow and Vladimir Vuskovic
customercloud
PRO
0
160
デジタルアイデンティティ人材育成推進ワーキンググループ 翻訳サブワーキンググループ 活動報告 / 20250114-OIDF-J-EduWG-TranslationSWG
oidfj
0
550
Docker Desktop で Docker を始めよう
zembutsu
PRO
0
180
PaaSの歴史と、 アプリケーションプラットフォームのこれから
jacopen
7
1.5k
[IBM TechXchange Dojo]Watson Discoveryとwatsonx.aiでRAGを実現!座学①
siyuanzh09
0
110
Featured
See All Featured
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
280
13k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
33
2k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
98
18k
The MySQL Ecosystem @ GitHub 2015
samlambert
250
12k
For a Future-Friendly Web
brad_frost
176
9.5k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
132
33k
BBQ
matthewcrist
85
9.4k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
113
50k
StorybookのUI Testing Handbookを読んだ
zakiyama
28
5.4k
What's in a price? How to price your products and services
michaelherold
244
12k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
27
1.5k
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