Slide 1

Slide 1 text

The basic of Scrum 22/7/2016 Tetsuya Taguchi

Slide 2

Slide 2 text

Scrum is •  Productively and creatively delivering products of the highest possible value.

Slide 3

Slide 3 text

Scrum is •  People can address complex adaptive problems.

Slide 4

Slide 4 text

Scrum is •  Lightweight •  Simple to understand •  Difficult to master

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

Planning is adaptive

Slide 7

Slide 7 text

Development is iterative

Slide 8

Slide 8 text

Product Backlog •  An ordered list of everything that might be needed in the product.

Slide 9

Slide 9 text

Product Owner •  Responsible for managing the Product Backlog. •  Ordering the items in the Product Backlog to best achieve goals and missions.

Slide 10

Slide 10 text

Development Team •  Delivering a potentially releasable Increment.

Slide 11

Slide 11 text

Roles blur

Slide 12

Slide 12 text

Self-organizing •  No one tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.

Slide 13

Slide 13 text

Sprint •  Consistent durations throughout a development effort.

Slide 14

Slide 14 text

Sprint Planning

Slide 15

Slide 15 text

Sprint Planning

Slide 16

Slide 16 text

Sprint Backlog •  Set of Product Backlog items selected for the Sprint

Slide 17

Slide 17 text

Increment •  Sum of all the Product Backlog items completed during a Sprint •  It must be in useable condition. •  It must be “Done”

Slide 18

Slide 18 text

Definition of “Done” •  Everyone must understand what “Done” means.

Slide 19

Slide 19 text

Daily Scrum •  To synchronize activities

Slide 20

Slide 20 text

Daily Scrum •  To inspect progress toward the Sprint Goal. •  To improve communications •  To improve Development Team's level of knowledge.

Slide 21

Slide 21 text

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

Slide 22

Slide 22 text

Sprint Review •  The Development Team demonstrates the work that it has “Done”. •  Answers questions about the Increment.

Slide 23

Slide 23 text

Working software is the primary measure of success

Slide 24

Slide 24 text

Sprint Review

Slide 25

Slide 25 text

Scope can vary

Slide 26

Slide 26 text

Sprint Retrospective •  To inspect itself •  To create a plan for improvements to be enacted during the next Sprint.

Slide 27

Slide 27 text

Scrum Master •  is responsible for ensuring Scrum is understood and enacted. •  is a servant-leader for the Scrum Team.

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

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