Introduce Scrum Based on Behavior Analysis

>100 Views

January 09, 19

スライド概要

profile-image

Frontier Soft 代表

シェア

またはPlayer版

埋め込む »CMSなどでJSが使えない場合

関連スライド

各ページのテキスト
1.

Introduce Scrum based on Behavior Analysis Lifematics Inc. Takuo Doi

2.

Today’s Goal Scrum is: • Lightweight • Simple to understand • Difficult to master 2019/1/9 Regional Scrum Gathering Tokyo 2019 From Scrum Guide 2

3.

Today’s Goal Scrum is: • Lightweight • Simple to understand • Difficult to master From Scrum Guide But 2019/1/9 Regional Scrum Gathering Tokyo 2019 3

4.

Takuo Doi Lifematics Inc. CTO National Institute of Informatics 2019/1/9 Regional Scrum Gathering Tokyo 2019 4

5.

Translated the book アジャイルイントロダクション 2018/12/28 バートランド・メイヤー (著) 石川冬樹 (監修) 土肥拓生, 前澤悠太, 末永俊一郎 (翻訳) 2019/1/9 Regional Scrum Gathering Tokyo 2019 5

6.

2019/1/9 Regional Scrum Gathering Tokyo 2019 6

7.

Once more the experience in CSD course … 2019/1/9 Regional Scrum Gathering Tokyo 2019 7

8.

Explicit Introduce Scrum based on Behavior Analysis Management Technieques How to create a self-organized team? Scrum for Programmers 2019/1/9 Implicit Regional Scrum Gathering Tokyo 2019 8

9.

? t l u c i f f i D s i m u r c S g n i r e t s a Why m ? s i s y l a n A r o i v ha e B s i What s i s y l a n A r o i v ha e B n o d e s a b Scrum 2019/1/9 Regional Scrum Gathering Tokyo 2019 9

10.

Why mastering Scrum is Difficult? 2019/1/9 Regional Scrum Gathering Tokyo 2019 10

11.

It depends 2019/1/9 Regional Scrum Gathering Tokyo 2019 11

12.

Why“It depends”? 2019/1/9 Regional Scrum Gathering Tokyo 2019 12

13.

Reasons why It depends • Various • Various • Various • Various • Various persons teams organization product status in the project Only following the specific process is not a solution. 2019/1/9 Regional Scrum Gathering Tokyo 2019 13

14.

Scrum is a process framework that has been used to manage work on complex products From Scrum Guide Individuals and interactions over processes and tools From Agile Manifesto 2019/1/9 Regional Scrum Gathering Tokyo 2019 14

15.

Too rigid Ideal Difficult to figure out the correct combination of practices. (Scrum) process flexible Feasible solution But, since Ideal depends on the situation, mastering is to difficult. Framework 2019/1/9 Practices (XP) thoughts flexible rigid rigid Process (Water Fall) Too flexible Manifesto (Agile) Focus on Regional Scrum Gathering Tokyo 2019 15

16.

Too rigid rigid rigid Process (Water Fall) Ideal Practices (XP) Difficult to figure out the correct combination of practices. thoughts flexible 2019/1/9 flexible 手順 =Behavior Analysis The way to find the ideal considering to the situations Framework (Scrum) Too flexible Manifesto (Agile) Focus on Regional Scrum Gathering Tokyo 2019 16

17.

What is Behavior Analysis? 2019/1/9 Regional Scrum Gathering Tokyo 2019 17

18.

Behavior Analysis One of the Psychologies, which focus on the behaviors. There is a methodology to look for the factors which have effect the behaviors throughout the experiments. In Behavior Analysis, personalities and characters are not the reason why a person can not do something. 出典: 使える行動分析学: じぶん実験のすすめ 2019/1/9 Regional Scrum Gathering Tokyo 2019 18

19.

Behavior: Something that dead body can not do 2019/1/9 Regional Scrum Gathering Tokyo 2019 19

20.

ABC Analysis Antecedent 2019/1/9 Behavior Regional Scrum Gathering Tokyo 2019 Consequence 20

21.

Contingency Reinforcement:stimulus which strengthen the behavior Punishment: stimulus which weaken the behavior As consequence: If reinforcement occurs, the behavior is strengthen If reinforcement disappear, the behavior is weaken If punishment occurs, the behavior is weaken If punishment disappear, the behavior is strengthen 2019/1/9 Regional Scrum Gathering Tokyo 2019 21

22.

Example of contingency • Antecedent Child is crying • Behavior Shout • Consequence Child stop to cry: reinforcement 2019/1/9 Regional Scrum Gathering Tokyo 2019 22

23.

Example of contingency • Antecedent Joining the meeting • Behavior Argue the opinions which does not match the opinions of the boss • Consequence Boss become angry: punishment 2019/1/9 Regional Scrum Gathering Tokyo 2019 23

24.

Example of contingency • Antecedent Hungry • Behavior Eat snacks • Consequence Satisfied: Reinforcement Get fat:Punishment 2019/1/9 Regional Scrum Gathering Tokyo 2019 24

25.

Contingency • Reinforcement like “The mountain if dust also Piled”or Reinforcement in the future does not strengthen the behavior too much. • If Exercise everyday, you will get thin • If Work hard, your salary will increase in future • Probabilistic occurrence of the reinforcement help to continue the behavior • Management by punishment have an effect immediately. But it easy cause the decrease of the motivation. 2019/1/9 Regional Scrum Gathering Tokyo 2019 25

26.

How to use contingency • Focus on the behavior • Character is not the reason • Figure out the target behavior • Strengthen / Weaken the target behavior • Based on the ABS analysis, change the environment and reinforcement occur and punishment disappear • Observe the target behavior and measure and evaluate it 2019/1/9 Regional Scrum Gathering Tokyo 2019 26

27.

Example of contingency management Since members are low-energy, no one say his own opinions during meetings. Antecedent In the meeting Behavior Say one’s own opinions Consequence Boss become angry Colleague laugh Refused the options without explanation Get rubbished What do you do in this situation? 2019/1/9 Regional Scrum Gathering Tokyo 2019 27

28.

Scrum based on Behavior Analysis 2019/1/9 Regional Scrum Gathering Tokyo 2019 28

29.

What is going on if Scrum does not work well? 2019/1/9 Regional Scrum Gathering Tokyo 2019 29

30.

Scrum Roles Product Owner Development Team Scrum Master Events Sprint Planning Daily Scrum Sprint Review Retrospective Artifacts Product Backlog Sprint Backlog Increment If Scrum does not work well: • Fail to operate events • Artifacts is not created correctly 2019/1/9 Regional Scrum Gathering Tokyo 2019 30

31.

Our team takes too much time for Sprint Planning. Argue about the user story Slow Planning Poker Argue the same things again and again Antecedent Does not understand User Story well. Behavior Consequence Argue about the User Story Understand the User Story: Reinforcement Product Backlog Refinement Antecedent Behavior Understand the User Story Argue about the User Story: Weaken 2019/1/9 Regional Scrum Gathering Tokyo 2019 Consequence 31

32.

Retrospective of our team does not work well. No one say improvement Criticize other persons Does not decide the next try Use negative words Unhappy Antecedent Retrospective Behavior Consequence Say something get a dirty look Hand-clap after talk Antecedent Behavior Retrospective Say something (強化) 2019/1/9 Regional Scrum Gathering Tokyo 2019 Consequence Hand-clap : Reinforcement 32

33.

Retrospective of our team does not work well. No one say improvement Criticize other persons Does not decide the next try Use negative words Unhappy Eat donuts during retrospective Antecedent ⾏動 Eat Donuts Smile 2019/1/9 Regional Scrum Gathering Tokyo 2019 後続事象 33

34.

Estimation of Sprint Backlog is not correct. Development team usually fails to complete all of the user stories. Make a forecast too much Antecedent Planning Team leave things unfinished Behavior Consequence Make a forecast too much Product Owner become happy: Reinforcement Discouraged in the end: Punishment Measure the Expectation and Result and visualize it Antecedent Behavior Planning Make a forecast too much : Weaken 2019/1/9 Regional Scrum Gathering Tokyo 2019 Consequence The measurement become better: Reinforcement 34

35.

エンジニアのスキルが低く、インクリメントの品質 が悪い。特に、よくデグレしているとクライアント からクレームが入る。 回帰テストを実施する テストコードを書く コードレビューを実施する Antecedent 実装中 ⾏動 後続事象 テストコードを書く プロダクトコードに避け る時間が減る (嫌⼦) バグが発⽣したら検知で きる(好⼦) カバレッジや、ミューテーションスコア などを計測、可視化する Antecedent ⾏動 実装中 テストコードを書く 2019/1/9 Regional Scrum Gathering Tokyo 2019 後続事象 数値化された安⼼感を確 認できる(好⼦) 35

36.

Scrum and Behavior Analysis Improvement Plan is Hypothesis If the target behavior is not changed, we need re-planning for improvement It is compatible the feedback loop of Sprint 2019/1/9 Regional Scrum Gathering Tokyo 2019 36

37.

Experiments in Lifematics I want work with a person of high motivation and good engineer What does “high motivation” mean? What does “good engineer” mean? 2019/1/9 Regional Scrum Gathering Tokyo 2019 37

38.

“Learning” 2019/1/9 Regional Scrum Gathering Tokyo 2019 38

39.

Record the learning 2019/1/9 Regional Scrum Gathering Tokyo 2019 39

40.

Evaluate Learning Commend the engineers who learn much. Share the learnings in a week 2019/1/9 Regional Scrum Gathering Tokyo 2019 40

41.

“It depends” • Reinforcement and Punishment depend a person • Consequence depends team • Consequence depends organization • The target behavior depends on product • The target behavior depends on situation of the project 2019/1/9 Regional Scrum Gathering Tokyo 2019 41

42.

Figure out the target behavior which prevents the Scrum. Then Design the consequence based on the reinforcement and punishment of the team members. 2019/1/9 Regional Scrum Gathering Tokyo 2019 42

43.

Too rigid rigid rigid Process (Water Fall) Ideal Practices (XP) Difficult to figure out the correct combination of practices. thoughts flexible flexible 手順 Hypothesis Verification from the point view of Behavior Analysis Framework (Scrum) 2019/1/9 Too flexible Manifesto (Agile) Focus on Regional Scrum Gathering Tokyo 2019 43

44.

Think based on Behavior Analysis 2019/1/9 Regional Scrum Gathering Tokyo 2019 44

45.

2019/1/9 Regional Scrum Gathering Tokyo 2019 45

46.

Any Questions? 2019/1/9 Regional Scrum Gathering Tokyo 2019 46