Default to Open - TC Agile MeetUp

Companies use hierarchical organizational structures to define areas of responsibility and drive better accountability. These structures can block cross-team interactions and knowledge sharing - slowing innovation and agility. Phil Holleran, from Github, will discuss strategies that use open platforms to drive meaningful development outcomes through increased collaboration and productivity across the organization.

Transcript

1. the best way to build and ship software Default to Open TC Agile Meetup 13 June 2017
2. the best way to build and ship software 2 HTTPS://XKCD.COM/644/
3. ! the best way to build and ship software 3 How to drive more meaningful development outcomes
4. the best way to build and ship software Phil Holleran @pholleran Solutions Engineer 4 "
5. the best way to build and ship software 5
6. ! the best way to build and ship software 6 ! Leader in Open Source Development Data Transparent Collaboration
7. ! the best way to build and ship software 7 How to drive more meaningful development outcomes Without dramatically changing org structures
8. ! the best way to build and ship software 8 Challenges Desired Behaviors
 & Outcomes Strategies
9. ! the best way to build and ship software 9 Challenges: lessons learned from organizations
10. the best way to build and ship software 10 most organizations struggle with awareness of existing enterprise development
11. the best way to build and ship software 11 A classic vertical organization
12. the best way to build and ship software 12 12
13. the best way to build and ship software 13
14. the best way to build and ship software 14 14
15. the best way to build and ship software 15
16. the best way to build and ship software 16
17. the best way to build and ship software 17
18. the best way to build and ship software 18
19. the best way to build and ship software 19 organizational distance between developers directly correlates to bugs and delays
20. ! the best way to build and ship software 20 Developer Churn Easy for individuals, disruptive to teams
21. ! the best way to build and ship software 21 Desired behaviors and outcomes
22. ! the best way to build and ship software 22 reuse & contribution
23. the best way to build and ship software 23
24. ! the best way to build and ship software 24 maintainership culture
25. ! the best way to build and ship software 25 frictionless workflows
26. ! the best way to build and ship software 26 more time coding
27. ! the best way to build and ship software 27 Engaged, productive developers
28. ! the best way to build and ship software 28 Strategies to elicit positive behaviors and outcomes
29. ! the best way to build and ship software 29 reuse & contribution
30. the best way to build and ship software 30 Contributions Open an Issue Improve docs Offer insight in Issue/PR Unsolicited improvements Knock out the backlog/roadmap ! #
31. ! the best way to build and ship software 31 A single platform for collaboration and coordination
32. ! the best way to build and ship software 32 Software Development Design Project Management Operations Security Domain Experts Customer Support Executive Leadership # Let everyone speak software together
33. ! the best way to build and ship software 33 Create context and awareness
34. ! the best way to build and ship software 34
35. ! the best way to build and ship software 35 electron.atom.io
36. ! the best way to build and ship software 36 Experiment with informal teams
37. ! the best way to build and ship software 37 Ad Hoc team creation that isn’t strictly tied to administrators
38. the best way to build and ship software 38 org/devGroupA org/devGroupB org/devGroupC org/javascript-devs
39. the best way to build and ship software 39 org/devGroupA org/devGroupB org/devGroupC org/javascript-devs org/security
40. the best way to build and ship software 40 org/devGroupA org/devGroupB org/devGroupC org/javascript-devs org/security org/SQL
41. ! the best way to build and ship software 41 Search everything from one place
42. ! the best way to build and ship software 42
43. ! the best way to build and ship software 43 Structure repositories, documentation, and team goals in a way that other teams can freely understand what’s going on
44. ! the best way to build and ship software 44 https://github.com/atom
45. ! the best way to build and ship software 45 maintainership culture
46. the best way to build and ship software 46 Maintainers Set vision & direction Document processes Set / maintain tone Approve / collaborate / deny submissions ! # Facilitate shared ownership
47. ! the best way to build and ship software 47 frictionless workflows
48. ! the best way to build and ship software 48 B U I L D C O L L A B O R A T E S H I P
49. ! the best way to build and ship software 49 Integrate chat with your single platform
50. ! the best way to build and ship software 50
51. ! the best way to build and ship software 51 Take ChatOps for a spin
52. ! the best way to build and ship software 52
53. ! the best way to build and ship software 53 ChatOps for everyone
54. ! the best way to build and ship software 54 more time coding
55. ! the best way to build and ship software 55 Time spent In Meetings: Bugs are found: Code Reviews: Deployment: 60 - 85% During code review or QA Once a week Ops and PMO decide 
 when to deploy Example Developer Calendar A bad week looks like this
56. ! the best way to build and ship software 56 This is better!
57. ! the best way to build and ship software 57 Team Radars: a best practice in knowledge sharing
58. ! the best way to build and ship software 58 If everyone is here, then they’re not doing something important somewhere else
59. ! the best way to build and ship software 59 Your weekly/daily standup 
 in asynchronous format
60. ! the best way to build and ship software 60 Cross link interesting information
61. the best way to build and ship software Thank you! please send feedback to pholleran@github.com