Visualizing Agile

Building software is an abstract problem that takes real time and real effort to achieve, but describing what goes into it can be challenging. The common aphorism of Show, Don't Tell is as applicable to delivering technical value as anything else. I'll show you how I've communicated to my team and the business what's happening at a variety of levels, and hopefully you'll learn a new way to communicate.

Transcript

1. Visualizing Agile Joshua Szmajda CTO, Optoro
2. Communication
3. This kinda sucks
4. Words in boxes is a little better
5. Color helps a lot
6. Now you can see this is a roadmap
7. Growth Optoro’s Tech team grew from 6 to 40 over the last 1.5 years
8. JIRA’s good for the low- level
9. But sucks when zoomed out
10. Read this book
11. We tried a Kanban
12. Things start in planning
13. progress to development
14. Go through internal review
15. And QA
16. Final dev review before release
17. Release scheduling
18. Celebrate Delivery
19. Define the columns
20. business-areas to focus on
24. Tech-support allocation
25. Room for metrics and measurement
26. June We’ve iterated over time
27. July adding dates, faces
28. October Where we are now
29. Development Running smoothly
30. Review and Test Later, things stuck in test
31. Later, doing too much, creating fires! —>
32. not online, but not a huge problem
33. Some alternatives
34. Dashboards
36. Tech support with aging tickets
37. Celebrate success!
38. Track business metrics too
39. Communicate team assignments
40. Communicate! • ‘Glanceability' • We improve what we see
41. Experiment!
42. Thanks! • Josh Szmajda • CTO / Optoro • @jszmajda • DCRUG, DC Polyglot Programmers https://github.com/groupon/greenscreen https://github.com/shopify/dashing