Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Introduce Scrum Based on Behavior Analysis

English version of Slides in the presentation in Regional Scrum Gathering Tokyo 2019

  • Be the first to comment

Introduce Scrum Based on Behavior Analysis

  1. 1. Introduce Scrum based on Behavior Analysis Lifematics Inc. Takuo Doi
  2. 2. 2019/1/9 Regional Scrum Gathering Tokyo 2019 2 Scrum is: • Lightweight • Simple to understand • Difficult to master From Scrum Guide Today’s Goal
  3. 3. 2019/1/9 Regional Scrum Gathering Tokyo 2019 3 Scrum is: • Lightweight • Simple to understand • Difficult to master From Scrum Guide Today’s Goal But
  4. 4. 2019/1/9 Regional Scrum Gathering Tokyo 2019 4 Takuo Doi Lifematics Inc. CTO National Institute of Informatics
  5. 5. 2019/1/9 Regional Scrum Gathering Tokyo 2019 5 Translated the book アジャイルイントロダクション 2018/12/28 バートランド・メイヤー (著) 石川冬樹 (監修) 土肥拓生, 前澤悠太, 末永俊一郎 (翻訳)
  6. 6. 2019/1/9 Regional Scrum Gathering Tokyo 2019 6
  7. 7. 2019/1/9 Regional Scrum Gathering Tokyo 2019 7 Once more the experience in CSD course …
  8. 8. 2019/1/9 Regional Scrum Gathering Tokyo 2019 8 Scrum for Programmers How to create a self-organized team? Introduce Scrum based on Behavior Analysis ManagementTechnieques Explicit Implicit
  9. 9. 2019/1/9 Regional Scrum Gathering Tokyo 2019 9
  10. 10. 2019/1/9 Regional Scrum Gathering Tokyo 2019 10 Why mastering Scrum is Difficult?
  11. 11. 2019/1/9 Regional Scrum Gathering Tokyo 2019 11 It depends
  12. 12. 2019/1/9 Regional Scrum Gathering Tokyo 2019 12 Why“It depends”?
  13. 13. Reasons why It depends • Various persons • Various teams • Various organization • Various product • Various status in the project 2019/1/9 Regional Scrum Gathering Tokyo 2019 13 Only following the specific process is not a solution.
  14. 14. 2019/1/9 Regional Scrum Gathering Tokyo 2019 14 Scrum is a process framework that has been used to manage work on complex products Individuals and interactions over processes and tools From Scrum Guide From Agile Manifesto
  15. 15. 2019/1/9 Regional Scrum Gathering Tokyo 2019 15 Process (Water Fall) Manifesto (Agile) thoughts rigidflexible rigid flexible Practices (XP) Ideal process Too flexible Focus on Too rigid Feasible solution But, since Ideal depends on the situation, mastering is to difficult. Framework (Scrum) Difficult to figure out the correct combination of practices.
  16. 16. 2019/1/9 Regional Scrum Gathering Tokyo 2019 16 Process (Water Fall) Manifesto (Agile) thoughts rigidflexible rigid flexible Practices (XP) Ideal 手順 Too flexible Focus on Too rigid Framework (Scrum) The way to find the ideal considering to the situations =Behavior Analysis Difficult to figure out the correct combination of practices.
  17. 17. 2019/1/9 Regional Scrum Gathering Tokyo 2019 17 What is Behavior Analysis?
  18. 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. 19. 2019/1/9 Regional Scrum Gathering Tokyo 2019 19 Behavior: Something that dead body can not do
  20. 20. 2019/1/9 Regional Scrum Gathering Tokyo 2019 20 ABC Analysis Antecedent Behavior Consequence
  21. 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. 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. 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. 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. 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. 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. 27. Example of contingency management Since members are low-energy, no one say his own opinions during meetings. 2019/1/9 Regional Scrum Gathering Tokyo 2019 27 Antecedent Behavior Consequence In the meeting Say one’s own opinions Boss become angry Colleague laugh Refused the options without explanation Get rubbished What do you do in this situation?
  28. 28. 2019/1/9 Regional Scrum Gathering Tokyo 2019 28 Scrum based on Behavior Analysis
  29. 29. 2019/1/9 Regional Scrum Gathering Tokyo 2019 29 What is going on if Scrum does not work well?
  30. 30. 2019/1/9 Regional Scrum Gathering Tokyo 2019 30 Scrum Roles Events Artifacts Product Owner Development Team Scrum Master Sprint Planning Daily Scrum Sprint Review Retrospective Product Backlog Sprint Backlog Increment If Scrum does not work well: • Fail to operate events • Artifacts is not created correctly
  31. 31. 2019/1/9 Regional Scrum Gathering Tokyo 2019 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 Behavior Consequence Does not understand User Story well. Argue about the User Story Understand the User Story: Reinforcement Antecedent Behavior Consequence Understand the User Story Argue about the User Story: Weaken - Product Backlog Refinement
  32. 32. Retrospective of our team does not work well. 2019/1/9 Regional Scrum Gathering Tokyo 2019 32 No one say improvement Criticize other persons Use negative words Does not decide the next try Unhappy Antecedent Behavior Consequence Retrospective Say something get a dirty look Antecedent Behavior Consequence Retrospective Say something (強化) Hand-clap : Reinforcement Hand-clap after talk
  33. 33. Retrospective of our team does not work well. 2019/1/9 Regional Scrum Gathering Tokyo 2019 33 Antecedent 行動 後続事象 Eat Donuts Smile Eat donuts during retrospective No one say improvement Criticize other persons Use negative words Does not decide the next try Unhappy
  34. 34. Estimation of Sprint Backlog is not correct. Development team usually fails to complete all of the user stories. 2019/1/9 Regional Scrum Gathering Tokyo 2019 34 Make a forecast too much Team leave things unfinished Antecedent Behavior Consequence Planning Make a forecast too much Product Owner become happy: Reinforcement Discouraged in the end: Punishment Antecedent Behavior Consequence Planning Make a forecast too much : Weaken The measurement become better: Reinforcement Measure the Expectation and Result and visualize it
  35. 35. エンジニアのスキルが低く、インクリメントの品質 が悪い。特に、よくデグレしているとクライアント からクレームが入る。 2019/1/9 Regional Scrum Gathering Tokyo 2019 35 テストコードを書く 回帰テストを実施する Antecedent 行動 後続事象 実装中 テストコードを書く プロダクトコードに避け る時間が減る (嫌子) バグが発生したら検知で きる(好子) Antecedent 行動 後続事象 実装中 テストコードを書く 数値化された安心感を確 認できる(好子) カバレッジや、ミューテーションスコア などを計測、可視化する コードレビューを実施する
  36. 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. 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. 38. 2019/1/9 Regional Scrum Gathering Tokyo 2019 38 “Learning”
  39. 39. 2019/1/9 Regional Scrum Gathering Tokyo 2019 39 Record the learning
  40. 40. 2019/1/9 Regional Scrum Gathering Tokyo 2019 40 Evaluate Learning Commend the engineers who learn much. Share the learnings in a week
  41. 41. 2019/1/9 Regional Scrum Gathering Tokyo 2019 41 • 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 “It depends”
  42. 42. 2019/1/9 Regional Scrum Gathering Tokyo 2019 42 Figure out the target behavior which prevents the Scrum. Then Design the consequence based on the reinforcement and punishment of the team members.
  43. 43. 2019/1/9 Regional Scrum Gathering Tokyo 2019 43 Process (Water Fall) Manifesto (Agile) thoughts rigidflexible rigid flexible Practices (XP) Ideal 手順 Too flexible Focus on Too rigid Framework (Scrum) Difficult to figure out the correct combination of practices. Hypothesis Verification from the point view of Behavior Analysis
  44. 44. 2019/1/9 Regional Scrum Gathering Tokyo 2019 44 Think based on Behavior Analysis
  45. 45. 2019/1/9 Regional Scrum Gathering Tokyo 2019 45
  46. 46. 2019/1/9 Regional Scrum Gathering Tokyo 2019 46 Any Questions?

×