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
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
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
150
わかりやすいブログを書くためにはどうすればよいか?
tetsuyataguchi
1
270
Nginxによるリバースプロキシ
tetsuyataguchi
0
580
Chef
tetsuyataguchi
0
75
Docker Pi
tetsuyataguchi
0
160
新卒エンジニアから見たデータセンター移行
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
GitHub Copilot 最新アップデート – 「一歩先」の実践活用術
moulongzhang
5
1.5k
脱SaaS!FDEを支えるプロビジョニングと分離設計
knih
0
240
AI-DLCを “そのまま導入しなかった”話 ~組織に合わせてアジャストした 私たちの実践共有~
hiroramos4
PRO
0
220
Kiroで書いた 設計書 が AI レビューの 採点基準 になる
ezaki
0
130
Flow 不死:AI 時代 DevOps 的不變本質
cheng_wei_chen
2
340
iAEONの段階的リアーキテクト戦略 / iAEON's_Gradual_Re-architecture_Strategy
aeonpeople
0
230
小さく始める AI 活用推進 ― 日経電子版 Web チームの事例/nikkei-tech-talk47
nikkei_engineer_recruiting
0
300
日本 Fintech 未来予測レポート 2027〜2028年(手動編集版)
8maki
1
2.5k
フィジカル版Github Onshapeの紹介
shiba_8ro
0
290
AIチャット検索改善の3週間
kworkdev
PRO
2
140
2026TECHFRESH畢業分享會 - Lightning Talk - E起 See See : 電商推薦讀心術? 數據說了算
line_developers_tw
PRO
0
1.3k
SONiCで構築・運用する生成AI向けパブリッククラウドネットワーク ~実装編~
sonic
0
280
Featured
See All Featured
Game over? The fight for quality and originality in the time of robots
wayneb77
1
200
A Tale of Four Properties
chriscoyier
163
24k
Building Applications with DynamoDB
mza
96
7.1k
We Have a Design System, Now What?
morganepeng
55
8.2k
Redefining SEO in the New Era of Traffic Generation
szymonslowik
1
340
Navigating Weather and Climate Data
rabernat
0
220
Rails Girls Zürich Keynote
gr2m
96
14k
Keith and Marios Guide to Fast Websites
keithpitt
413
23k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
Building a Modern Day E-commerce SEO Strategy
aleyda
45
9.1k
VelocityConf: Rendering Performance Case Studies
addyosmani
333
25k
Amusing Abliteration
ianozsvald
1
210
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