Universal Principles of Scrum that Engage Developers

Connect surprising results of behavioral psychology to understand how the Scrum software development methodology is well suited to engage developers

Transcript

1. Engaging Developers Music City Agile Jeffrey Hicks 2017
2. Engaging Developers? •  Not about engaging developers for an open source community •  Not about a9rac:ng developers to a pla;orm, API etc. •  This talk is about engaging the employed developer.
3. About Me •  Developer Turned Developer & Manager •  Organize Li9le Rock ReactJS Meetup •  I Prac:ce Scrum •  Write soNware for crises management @jrhicks
4. Origins of this Talk
5. Abridged List of Models and Agile Methodologies Models Agile •  Waterfall •  Spiral •  RAD •  Agile •  Lightweight •  Scrum •  Kanban •  XP •  ….
6. Crises Management
7. Incident Command System ICS
8. SCRUM & ICS
9. Some Surprising Similari:es Chlorine Train Derailment Flappy Birds IOS Game
10. Glucksberg (1962)
11. Glucksberg (1962)
12. Glucksberg (1962)
13. Glucksberg (1962) Average Time (Minutes) % Failure Tacks In Box 7.41 31% Tacks Outside the Box 4.99 18%
14. Non Incen:vized Average Time (Minutes) % Failure Tacks In Box 7.41 31% Tacks Outside the Box 4.99 18% Incen:vized ($5, $20) Average Time (Minutes) % Failure Tacks In Box 11.08 50% Tacks Outside the Box 3.67 6% Glucksberg (1962)
15. Glucksberg (1962) Giving $160 performance incen:ve for 7 minutes of insight work
16. Glucksberg (1962) Giving $160 performance incen:ve for 7 minutes of insight work Time 49% Failure 60%
17. Managing Flow
18. How does SCRUM Improve Flow?
19. The Sprint
20. Product Backlog Sprint Backlog Sprint Epics and Stories Selected Stories with Task Breakouts Fixed deadline & deliverables SCRUM
21. The Backlog
22. Product Backlog Sprint Backlog Sprint Epics and Stories Selected Stories with Task Breakouts Fixed deadline & deliverables Incident PrioriAes Incident AcAon Plan OperaAonal Period Objec:ves Selected Objec:ves with Tac:cal Assignments Fixed deadline & deliverables SCRUM ICS
23. Intrinsically Sa:sfying Sprint
24. Planning Poker (The Process) •  Product Owner Reads A Story •  Each es:mator is holding a deck of cards with values like 0, 1, 2, 3, 5, 8, 13, 21, 34 ... •  ANer a short discussion •  Each player privately reveals their es:mate •  Repeat un:l consensus
25. Pin the Tail on the Es:mate
26. Pin the Tail on the Es:mate 1 3 21
27. Pin the Tail on the Es:mate 1 3 21
28. Pin the Tail on the Es:mate 1 3 21
29. Pin the Tail on the Es:mate 1 3 21
30. Pin the Tail on the Es:mate 1 3 21
31. Pin the Tail on the Es:mate 1 3 21 0, 1, 2, 3, 5, 8, 13, 21, 34 ..
32. Pin the Tail on the Es:mate 500lb 3.5k lb 21k lb 0, 1, 2, 3, 5, 8, 13, 21, 34 .. 12-15k lb
33. Ross et al. (1988)
36. Ross et al. (1988) Most Likely Least Likely 80% 16% 8% 0%
37. Ross et al. (1988) Most Likely Least Likely 80% 16% 8% 0%
38. Ross et al. (1988) Dear Jeffrey Hicks Dear Student Most Likely Least Likely
39. Ross et al. (1988) 81% 17% Dear Jeffrey Hicks Dear Student Most Likely Least Likely
40. Ross et al. (1988) 81% 80% 17% 16% Dear Jeffrey Hicks Dear Student Most Likely Least Likely
41. Ross et al. (1988) 81% 80% 17% 16% 42% Dear Jeffrey Hicks Dear Student Most Likely Least Likely
42. Ross et al. (1988) 81% 80% 17% 16% 42% 25% Dear Jeffrey Hicks Dear Student Most Likely Least Likely
43. Ross et al. (1988) 81% 80% 17% 16% 42% 8% 25% Dear Jeffrey Hicks Dear Student Most Likely Least Likely
44. Ross et al. (1988) 81% 80% 17% 16% 42% 8% 25% 0% Dear Jeffrey Hicks Dear Student Most Likely Least Likely
45. Ross et al. (1988) 81% 80% 17% 16% 42% 8% 25% 0% Dear Jeffrey Hicks Dear Student Most Likely Least Likely
46. Ross et al. (1988) 81% 80% 17% 16% 42% 8% 25% 0% Dear Jeffrey Hicks Dear Student Most Likely Least Likely
47. Ross et al. (1988) 81% 80% 17% 16% 42% 8% 25% 0% Dear Jeffrey Hicks Dear Student Most Likely Least Likely
48. Ross et al. (1988) Results in a 12 to 1 Error Rate Belief that personality has a bigger impact than situa:on
49. How can Scrum Improve Specificity >
50. How can Scrum Improve Specificity Stories conforming to the templates describe the what and why. As a [user role] I want [the ability] for [business value] >
51. How can Scrum Improve Specificity •  Sprints with a fixed start and stop provide specific when >
52. How can Scrum Improve Specificity •  Task breakouts provide the How >
53. Specificity Micro Management THE WHEN & WHO OF THE HOW
54. When: Sprint Planning Who: Developers SCRUM Stories Tasks
55. When: TacAcs MeeAng Who: OperaAons ICS ObjecAves Work Assignments
56. How can Scrum Provide a Clear Map
57. How can Scrum Provide a Clear Map
58. How can Scrum “Personalize it”
59. How can Scrum “Personalize it”
60. How can Scrum “Personalize it” Dear Developer Dear Jeff
61. How can Scrum “Personalize it” Daily stand-ups Each developer •  Progress •  Plans •  Impediments Dear Developer Dear Jeff
62. Takeaways •  Being specific is more engaging. – As long as you don’t micromanage •  Task boards show the path. •  Daily stand-ups personalize it.
63. D. Ariely et al (2008)
64. D. Ariely et al (2008) MEANING
65. D. Ariely et al (2008) Paperwork
66. D. Ariely et al (2008) Paperwork $0.55
67. D. Ariely et al (2008) Paperwork $0.55 $0.50
68. D. Ariely et al (2008) Paperwork $0.55 $0.50 $0.45
69. D. Ariely et al (2008) Paperwork $0.55 $0.50 $0.45 …
70. D. Ariely et al (2008)
71. D. Ariely et al (2008)
72. D. Ariely et al (2008)
73. D. Ariely et al (2008)
74. D. Ariely et al (2008)
75. D. Ariely et al (2008)
76. D. Ariely et al (2008)
77. How can SCRUM provide meaning?
78. How can SCRUM provide meaning? The Review •  Held at end of sprint •  Product owner required •  Can invite others •  Always let the doers present
79. How can SCRUM provide meaning?
80. How can SCRUM provide meaning? Shipping •  Defini:on of done •  Says easy does hard •  Not shipping == shredding
81. What did I miss? •  Glucksberg - Candle Problem –  Sprints (Well es:mated) •  Ross et al - Disposi:on vs Situa:on –  Well wri9en stories and tasks –  Taskboards and burndowns for guidance –  Standups for planning and personalizing •  Ariely et al – Shredding Mo:va:on – Reviews – Working Increment of SoNware
82. Thank You •  Jeffrey Hicks •  Twi9er: @jrhicks •  Github: @jrhicks •  Email: jrhicks@gmail.com