Upcoming SlideShare
×

# Scaling the card wall

1,069 views

Published on

2 Likes
Statistics
Notes
• Full Name
Comment goes here.

Are you sure you want to Yes No
• Be the first to comment

Views
Total views
1,069
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
7
0
Likes
2
Embeds 0
No embeds

No notes for slide

### Scaling the card wall

1. 1. I love the smell of Sharpies in the morning or, how I learnt to stop worrying and love the card wall.Friday, 2 March 12
2. 2. or, Scaling the card wallFriday, 2 March 12
3. 3. About meFriday, 2 March 12
4. 4. About me • Politics wonkFriday, 2 March 12
5. 5. About me • Politics wonk • Developer on GreenHopper at AtlassianFriday, 2 March 12
6. 6. About me • Politics wonk • Developer on GreenHopper at Atlassian • @jameshatherly on twitterFriday, 2 March 12
7. 7. Friday, 2 March 12
8. 8. Card walls are awesomeFriday, 2 March 12
9. 9. Card walls are awesome • ... but they’re absolutely terribleFriday, 2 March 12
10. 10. Card walls • “We dont learn to do arithmetic using a calculator.  No, one starts with simple addition and by the time your ready to learn division it is done using pencil and paper (long division old school).  Requiring the student to do the hard work of the long division process may help them to understand the conceptual division problem and the solution technique.”Friday, 2 March 12
11. 11. What makes me tickFriday, 2 March 12
12. 12. What makes me tick • What growing pains can we expect?Friday, 2 March 12
13. 13. What makes me tick • What growing pains can we expect? • How have others overcome similar growing pains?Friday, 2 March 12
14. 14. What makes me tick • What growing pains can we expect? • How have others overcome similar growing pains? • What are the common patterns to these solutions?Friday, 2 March 12
15. 15. OutlineFriday, 2 March 12
16. 16. Outline • BackgroundFriday, 2 March 12
17. 17. Outline • Background • ExperimentFriday, 2 March 12
18. 18. Outline • Background • Experiment • Further ResearchFriday, 2 March 12
19. 19. Outline • Background • Experiment • Further Research • Commonalities and ApplicationsFriday, 2 March 12
20. 20. Why card wallFriday, 2 March 12
21. 21. Why card wall • Low frictionFriday, 2 March 12
22. 22. Why card wall • Low friction • Low barrier to entryFriday, 2 March 12
23. 23. Why card wall • Low friction • Low barrier to entry • SimpleFriday, 2 March 12
24. 24. Why card wall • Low friction • Low barrier to entry • Simple • High transparencyFriday, 2 March 12
25. 25. Why card wall • Low friction • Low barrier to entry • Simple • High transparency • High visibilityFriday, 2 March 12
26. 26. Why not?Friday, 2 March 12
27. 27. Why not? • Forces teams to be co-locatedFriday, 2 March 12
28. 28. Why not? • Forces teams to be co-located • Visibility/transparency argument not so strongFriday, 2 March 12
29. 29. Why not? • Forces teams to be co-located • Visibility/transparency argument not so strong • Requires data entry to get tooling beneﬁtsFriday, 2 March 12
30. 30. Manifesto for Agile Software Development • “Individuals and interactions over processes and tools”Friday, 2 March 12
31. 31. How we rollFriday, 2 March 12
32. 32. Scrum shock therapyFriday, 2 March 12
33. 33. Scrum shock therapy • http://rapidscrum.com/shock.phpFriday, 2 March 12
34. 34. Scrum shock therapy • http://rapidscrum.com/shock.php • For educationFriday, 2 March 12
35. 35. Scrum shock therapy • http://rapidscrum.com/shock.php • For education • For self improvementFriday, 2 March 12
36. 36. Cat-fooding a physical card wallFriday, 2 March 12
37. 37. FindingsFriday, 2 March 12
38. 38. Findings • Most ﬁndings were unsurprisingFriday, 2 March 12
39. 39. Findings • Most ﬁndings were unsurprising • Card walls are ﬁddlyFriday, 2 March 12
40. 40. Findings • Most ﬁndings were unsurprising • Card walls are ﬁddly • Seriously lo-ﬁFriday, 2 March 12
41. 41. FindingsFriday, 2 March 12
42. 42. Findings • Serious hindrance to working from home/ working remotelyFriday, 2 March 12
43. 43. Findings • Serious hindrance to working from home/ working remotely • No persistenceFriday, 2 March 12
44. 44. Findings • Serious hindrance to working from home/ working remotely • No persistence • No searchFriday, 2 March 12
45. 45. Findings • Serious hindrance to working from home/ working remotely • No persistence • No search • No linkingFriday, 2 March 12
46. 46. FindingFriday, 2 March 12
47. 47. Finding • ToolingFriday, 2 March 12
48. 48. Finding • Tooling • MylynFriday, 2 March 12
49. 49. Finding • Tooling • Mylyn • Linking commits back to storiesFriday, 2 March 12
50. 50. Finding • Tooling • Mylyn • Linking commits back to stories • Reporting & chartingFriday, 2 March 12
51. 51. My favourite quote from the experiment • “handwriting is not a talent shared by everyone”Friday, 2 March 12
52. 52. So what was good?Friday, 2 March 12
53. 53. So what was good? • Collaboration and discussion became synchronisedFriday, 2 March 12
54. 54. So what was good? • Collaboration and discussion became synchronised • Better communication on issues and subtasksFriday, 2 March 12
55. 55. Where to from here?Friday, 2 March 12
56. 56. Where to from here? • Card wall with manual synchronisationFriday, 2 March 12
57. 57. Where to from here? • Card wall with manual synchronisation • batchedFriday, 2 March 12
58. 58. Where to from here? • Card wall with manual synchronisation • batched • manual data entryFriday, 2 March 12
59. 59. Where to from here? • Card wall with manual synchronisation • batched • manual data entry • fragmented discussionFriday, 2 March 12
60. 60. Really?Friday, 2 March 12
61. 61. That’s it?Friday, 2 March 12
62. 62. So what are the alternatives?Friday, 2 March 12
63. 63. So what are the alternatives? • Let’s reconsider our old wallboardFriday, 2 March 12
64. 64. So what are the alternatives? • Let’s reconsider our old wallboard • self-synchronisingFriday, 2 March 12
65. 65. So what are the alternatives? • Let’s reconsider our old wallboard • self-synchronising • inherently distributedFriday, 2 March 12
66. 66. So what are the alternatives? • Let’s reconsider our old wallboard • self-synchronising • inherently distributed • can include extras - builds, etcFriday, 2 March 12
67. 67. So what are the alternatives? • Let’s reconsider our old wallboard • self-synchronising • inherently distributed • can include extras - builds, etc • non-interactive - deal breakerFriday, 2 March 12
68. 68. Same goes for...Friday, 2 March 12
69. 69. Same goes for... • sprint.lyFriday, 2 March 12
70. 70. Same goes for... • sprint.ly • TrelloFriday, 2 March 12
71. 71. Same goes for... • sprint.ly • Trello • ScrumblrFriday, 2 March 12
72. 72. Same goes for... • sprint.ly • Trello • Scrumblr • any web-based cardwall/taskboard toolFriday, 2 March 12
73. 73. Same goes for... • sprint.ly • Trello • Scrumblr • any web-based cardwall/taskboard tool • If you’re used to a physical card wall, the interaction model just isn’t quite rightFriday, 2 March 12
74. 74. AlternativesFriday, 2 March 12
75. 75. Alternatives • Smart whiteboards and other touch-capable screensFriday, 2 March 12
76. 76. Alternatives • Smart whiteboards and other touch-capable screens • ExpensiveFriday, 2 March 12
77. 77. Alternatives • Smart whiteboards and other touch-capable screens • Expensive • Again, the interaction model is just wrongFriday, 2 March 12
78. 78. AlternativesFriday, 2 March 12
79. 79. Alternatives • QR codes on your card wallFriday, 2 March 12
80. 80. Alternatives • QR codes on your card wall • batched synchronizationFriday, 2 March 12
81. 81. Alternatives • QR codes on your card wall • batched synchronization • no data entry, automated reportingFriday, 2 March 12
82. 82. Alternatives • QR codes on your card wall • batched synchronization • no data entry, automated reporting • stories & tasks are addressableFriday, 2 March 12
83. 83. Alternatives • QR codes on your card wall • batched synchronization • no data entry, automated reporting • stories & tasks are addressable • still a problem for working from homeFriday, 2 March 12
84. 84. Alternatives • QR codes on your card wall • batched synchronization • no data entry, automated reporting • stories & tasks are addressable • still a problem for working from home • no audit trail - not really a problem for agile teamsFriday, 2 March 12
85. 85. ExamplesFriday, 2 March 12
86. 86. AlternativesFriday, 2 March 12
87. 87. Vodafone web team card wallFriday, 2 March 12
88. 88. Vodafone web team card wall • Winner of 2010 ultimate wallboard competitionFriday, 2 March 12
89. 89. Vodafone web team card wall • Winner of 2010 ultimate wallboard competition • Pretty much the coolest thing everFriday, 2 March 12
90. 90. Vodafone web team card wall • Winner of 2010 ultimate wallboard competition • Pretty much the coolest thing ever • RFID chips for each card, readers update in software back-end on status changeFriday, 2 March 12
91. 91. Vodafone web team card wall • Winner of 2010 ultimate wallboard competition • Pretty much the coolest thing ever • RFID chips for each card, readers update in software back-end on status change • Changes which bypass the card wall trigger a change printoutFriday, 2 March 12
92. 92. Vodafone web team card wall • Winner of 2010 ultimate wallboard competition • Pretty much the coolest thing ever • RFID chips for each card, readers update in software back-end on status change • Changes which bypass the card wall trigger a change printout • A whole lot moreFriday, 2 March 12
93. 93. Vodafone web team card wallFriday, 2 March 12
94. 94. Vodafone web team card wall • Hands-on set up - RFID cards, RFID readers, label printer, projector, video cameraFriday, 2 March 12
95. 95. Vodafone web team card wall • Hands-on set up - RFID cards, RFID readers, label printer, projector, video camera • Non-portableFriday, 2 March 12
96. 96. Vodafone web team card wall • Hands-on set up - RFID cards, RFID readers, label printer, projector, video camera • Non-portable • Minor lag of changes getting onto the wallFriday, 2 March 12
97. 97. Vodafone web team card wall • Hands-on set up - RFID cards, RFID readers, label printer, projector, video camera • Non-portable • Minor lag of changes getting onto the wall • Contains some ‘hacks’Friday, 2 March 12
98. 98. Vodafone web team card wall • Hands-on set up - RFID cards, RFID readers, label printer, projector, video camera • Non-portable • Minor lag of changes getting onto the wall • Contains some ‘hacks’ • Still, awesome.Friday, 2 March 12
99. 99. Potential alternativesFriday, 2 March 12
100. 100. Potential alternatives • SAP research InnoBoardFriday, 2 March 12
101. 101. Potential alternatives • SAP research InnoBoard • Cool tech, really nice potential card wall replacementFriday, 2 March 12
102. 102. Potential alternatives • SAP research InnoBoard • Cool tech, really nice potential card wall replacement • Platform developed, ref-app is based on collaboration, not agile development.Friday, 2 March 12
103. 103. Potential alternatives • SAP research InnoBoard • Cool tech, really nice potential card wall replacement • Platform developed, ref-app is based on collaboration, not agile development. • They want to do other applications on top of their platform, agile makes senseFriday, 2 March 12
104. 104. CommonalitiesFriday, 2 March 12
105. 105. Commonalities • Bi-directional propagation of changesFriday, 2 March 12
106. 106. Commonalities • Bi-directional propagation of changes • Real-time (or near-to) updatesFriday, 2 March 12
107. 107. Commonalities • Bi-directional propagation of changes • Real-time (or near-to) updates • Central and tangibleFriday, 2 March 12
108. 108. Commonalities • Bi-directional propagation of changes • Real-time (or near-to) updates • Central and tangible • Allow for changing status, assigning to someone, adding new cards (kanban speciﬁc)Friday, 2 March 12
109. 109. CommonalitiesFriday, 2 March 12
110. 110. Commonalities • No manual steps (other than set-up)Friday, 2 March 12
111. 111. Commonalities • No manual steps (other than set-up) • Some level of traceabilityFriday, 2 March 12
112. 112. Commonalities • No manual steps (other than set-up) • Some level of traceability • Automated reporting & chart generationFriday, 2 March 12
113. 113. Enter: Microsoft KinectFriday, 2 March 12
114. 114. We’ve tried this beforeFriday, 2 March 12
115. 115. We’ve tried this before • My colleague Shihab and I worked on this last yearFriday, 2 March 12
116. 116. We’ve tried this before • My colleague Shihab and I worked on this last year • Blinded by cool tech, we lost sight of the “solve one problem and solve it well” idealFriday, 2 March 12
117. 117. We’ve tried this before • My colleague Shihab and I worked on this last year • Blinded by cool tech, we lost sight of the “solve one problem and solve it well” ideal • Shipped a tech demo, got some positive feedback, went nowhere with itFriday, 2 March 12
118. 118. Keen to try againFriday, 2 March 12
119. 119. Keen to try again • But curious as to whether analog-or-death types agree with me that there’s valueFriday, 2 March 12
120. 120. Keen to try again • But curious as to whether analog-or-death types agree with me that there’s value • Feel free to share your thoughts afterwardsFriday, 2 March 12
121. 121. RecappingFriday, 2 March 12
122. 122. Recapping • Card walls face problems, not just as the team grows, but also as the organisation the team exists within growsFriday, 2 March 12
123. 123. Recapping • Card walls face problems, not just as the team grows, but also as the organisation the team exists within grows • Current alternatives can’t solve every problem, but they might solve your’sFriday, 2 March 12
124. 124. Recapping • Card walls face problems, not just as the team grows, but also as the organisation the team exists within grows • Current alternatives can’t solve every problem, but they might solve your’s • No silver bulletFriday, 2 March 12
125. 125. Recapping • Card walls face problems, not just as the team grows, but also as the organisation the team exists within grows • Current alternatives can’t solve every problem, but they might solve your’s • No silver bullet • No free lunchFriday, 2 March 12