defects, tech debt and user stories... they are all the same.

This presentation will dig into the ideas of why teams create different types of cards on the card wall and why they should not. We will explore the idea around making all cards on the wall, regardless of type, as equal citizens on the card wall and discussed accordingly. The ideas of making everything a user story and being happy about it will be explored. With a goal of convincing developers and business people alike... the concept of card equality... and the business benefits afforded by this technique.

Transcript

1. 2.22.2014
2. all the same. tech debt, defects, & user stories
3. dj daugherty @ddaugher
4. dj daugherty @ddaugher
5. dj@pillartechnology.com
6. think.
7. question the norm.
8. i struggle with this idea every day.
9. different types of cards why do teams
10. different types of cards why do teams should they?
11. equal citizens
12. everything is a story.
13. everything is a story.
14. convince business and development the benefits of card equality.
16. all the same.
17. everything is a story.
18. what is a story
19. what is a story… not !
20. not a use case.
21. not a requirements document.
22. what is a story
23. definition of a story what is a story
24. what is a story
25. what is a story
26. what is a story
27. what is a story
28. what is a story
29. what is a story
30. as [user] i want to [do something] so that [reason/benefit] what is a story
31. as [persona] i want to [do something] so that [reason/benefit] what is a story
32. as [persona] i want to [do something] so that [reason/benefit] what is a story
33. a way to plan our work as a small customer-centric process. what is a story
34. a way to plan our work as a small customer-centric process. what is a story
35. a one-or-two line description of work to be produced. what is a story
36. placeholder for a detailed discussion about requirements. what is a story
37. "promissory note for a future conversation.” - Alistar Cockburn what is a story
38. "promissory note for a future conversation.” - Alistar Cockburn what is a story
39. ‘invitation to a conversation’ what is a story
40. what is a defect
41. defect… a deviation from an expectation. what is a defect
42. a variation of the expected functionality. what is a defect
43. what is a defect
44. defects are not the business trying to punish the developers. what is a defect
45. defects are not the business trying to punish the developers. but their concern that the system is deviating from their expectation. what is a defect
46. types of defects what is a defect
47. implementation : wrong story : right what is a defect
48. implementation : wrong story : right what is a defect
49. implementation : right story : bad idea what is a defect
50. implementation : right story : right story needs to change what is a defect
51. defects. what is a defect
52. wedge between development & business what is a defect
53. bugs on the wall on the wall! what is a defect
54. bugs on the wall on the wall! consider the users perspective. what is a defect
55. bugs on the wall the user does not care what you call the work… they just want the application to function as they expect. what is a defect
56. what is tech debt
57. software update. what is tech debt
58. changing frameworks. what is tech debt
59. refactoring what is tech debt
60. tech debt is not the developers trying to punish the business. what is tech debt
62. all the same.
63. everything is a story.
65. and delivers business value
66. think. simpler !
67. planning.
72. A B
73. idea reality
74. idea reality
75. idea reality
76. idea reality
77. idea reality
78. all the same.
79. why should we?
80. why should we? everything is tied to business value.
81. delivery of business value is primary goal. why should we?
82. treat prevention as an investment why should we?
83. no secrets ! why should we?
84. budget within the release. why should we?
85. definition of done. why should we?
86. how about an example?
87. as a developer, i want to replace the current search with a multi-threaded solution so the search will perform better.
88. acceptance criteria - ???
89. as a csr user, i want the system to run multiple searches at the same time, so that i can view the customer’s entire account history.
90. acceptance criteria - single user - 5 searches simultaneously - 4 second response time
91. idea reality
92. everything is a means of delivering business value.
93. for each card that approaches the wall, ask the question… ! what is the value of completing the work defined by the card.
94. all the same. tech debt, defects, & user stories
95. all the same. tech debt, defects, & user stories
96. all the same. tech debt, defects, & user stories
97. all the same. tech debt, defects, & user stories treated
98. as [persona] i want to [do something] so that [reason/benefit]
99. recap here each story needs ‘words’
100. each story needs ‘words’ interpret
101. each story needs ‘words’ interpret estimate
102. each story needs ‘words’ interpret estimate execute
103. recap here all ‘effort’ should be placed on the wall… without this ‘visibility’… focus is too narrow and ‘things’ get missed or worked on and the effort is not accounted for.
104. stories… all of them… are just starters for a conversation… everyone on the team owns the backlog and the stories.
105. “the product owner is inevitably the arbitrator… perfect stories are not the goal… but, realized business value released into the wild… is!”
106. card equality
107. card equality what is the first step?
108. just start. it will suck at first. that’s ok. have a ritual. it is ok to fail. beer helps! eventually it will suck less.
109. thanks
110. q&a
111. http://school.discoveryeducation.com/clipart/images/thinkingcapwhoa.gif