The document discusses ways to promote collaborative development through knowledge sharing and reuse. It suggests establishing ad-hoc teams, guilds, and hubs of information to make work and expertise discoverable. It also emphasizes the importance of inclusion and adopting practices like InnerSource to engage diverse talent.

1. Collaborative
Development
TheOnlyCDThatMatters
BrentBeer
@brntbeer

2. Collaborative
Development
TheCDthatyoushouldreallycareaboutbefore
youstartworkingonotherthingssothatthose
otherthingsworkreallywelltoo!
BrentBeer
@brntbeer

3. Hello!

4. OH I LOVE GITHUB. IT’S REALLY CHANGED
THE WAY SOFTWARE DEVELOPMENT
HAPPENS
YEAH! I LOVE IT TOO. ARE YOU USING
GITHUB AT WORK?
NOPE. I WISH, BUT IT’S JUST TOO HARD FOR
ME TO CHANGE THINGS HERE AT ACME
CORP.
:(

5. Quick Poll!

6. “
”
AS WELL AS ENHANCED COLLABORATIVE WORKING AMONG
PROJECT TEAMS, DEVELOPERS CAN ALSO SEARCH AND
REUSE CODE THAT ALREADY EXISTS ACROSS THE
ORGANIZATION. THIS AVOIDS REINVENTING FIELD-TESTED
SOLUTIONS DEVELOPED FOR OTHER PROJECTS
- CARLOS GONCALVES HTTPS://GITHUB.COM/BUSINESS/CUSTOMERS/
SOCIETE-GENERALE

7. “
”
OUR IT GROUP WANTED TO OFFICIALLY SUPPORT A
SOLUTION SO THAT DEVELOPERS COULD CONTINUE
WORKING THE WAY THEY PREFERRED
- BERTHOLD BÄUML HTTPS://GITHUB.COM/BUSINESS/CUSTOMERS/DLR

8. “
”
SAP’S SUCCESS IS TIED CLOSELYTO THE RELATIONSHIPS
AND COLLABORATION BETWEEN ALL OF THOSE DISTRIBUTED
DEVELOPMENT TEAMS.
- DOMINIK TORNOW HTTPS://GITHUB.COM/BUSINESS/CUSTOMERS/SAP

9. Previously, off the
Internet

10. By Dugsong at en.wikipedia -Transferred from en.wikipedia by SreeBot, Public Domain, https://commons.wikimedia.org/w/index.php?curid=16786574

11. http://www.thedigitalprojectmanager.com/how-to-run-a-great-internal-project-kickoff-meeting/

12. KnowledgeSharing

13. “
”
A RISING TIDE LIFTS ALL
BOATS
- JOHN F. KENNEDY

14. How much does it cost to
train a new team member?

15. “
”
ITTAKES TIME FOR PEOPLE TO GET USED TO WORKING WITH
EACH OTHER AND A RAPID RAMP UP CAN STOP A LARGE
TEAM FROM FORMING THE RELATIONSHIPS IT NEEDS TO
SUCCEED.
- MARTIN FOWLER , “PREMATURERAMPUP”, HTTPS://MARTINFOWLER.COM/
BLIKI/PREMATURERAMPUP.HTML

16. ChatOps: do your work in
the open!

17. Solution: ChatOps

18. Solution: ChatOps

20. Solution: ChatOps

21. Team Discussions: have a
place to have your discussions

22. Solution: Team Discussions

23. Team Radars: a best practice
in knowledge sharing

24. Solution: Team Radar

25. Solution: Team Radar

26. Solution: Team Radar

27. GitHub Pages and READMEs:
a beautiful way to read about
a project

28. Solution: READMEs

29. Solution: READMEs

30. Solution: GitHub Pages

31. Allowotherstolearn
fromyourwork
Moveoperationsintoyourchat,visibleteam
discussions,teamradars,andpromotionalsites
toallowpeopletoshareknowledge

32. ReuseandDiscovery

33. What is anyone else
even working on?

37. Form Guilds to promote
sharing information
between informal groups

38. Solution: Guilds
Reference: Spotify Engineering Culture Part 1: https://vimeo.com/85490944

39. Create teams fast with an
easy way to reference them
Javascript-devs, SQL-ninjas
2014-security-event, auth-refactor-devs

40. org/devGroupA org/devGroupB org/devGroupC

41. org/devGroupA org/devGroupB org/devGroupCorg/devGroupA org/devGroupB org/devGroupC
org/javascript-devs
Solution: Ad-hoc Teams

42. org/devGroupA org/devGroupB org/devGroupCorg/devGroupA org/devGroupB org/devGroupC
org/javascript-devs
org/devGroupA org/devGroupB org/devGroupC
org/javascript-devs
org/security
Solution: Ad-hoc Teams

43. org/devGroupA org/devGroupB org/devGroupCorg/devGroupA org/devGroupB org/devGroupC
org/javascript-devs
org/devGroupA org/devGroupB org/devGroupC
org/javascript-devs
org/security
org/devGroupA org/devGroupB org/devGroupC
org/javascript-devs
org/security
org/SQL
Solution: Ad-hoc Teams

44. org/devGroupA org/devGroupB org/devGroupCorg/devGroupA org/devGroupB org/devGroupC
org/javascript-devs
org/devGroupA org/devGroupB org/devGroupC
org/javascript-devs
org/security
org/devGroupA org/devGroupB org/devGroupC
org/javascript-devs
org/security
org/SQL
org/javascript-devs
org/devGroupA org/devGroupB org/devGroupC
org/security
org/SQL
Reports to devGroupA
Part of security and SQL
teams
Solution: Ad-hoc Teams

45. org/javascript-devs
org/devGroupA org/devGroupB org/devGroupC
org/security
org/SQL
Reports to devGroupC
Part of javascript devs and
SQL teams
Solution: Ad-hoc Teams

46. Establish hubs of information
where people regularly visit

47. Solution: Established Hubs

48. Solution: Established Hubs

49. Solution: Established Hubs

50. Solution: Established Hubs

51. Solution: Established Hubs

52. Enableothersto
easilyfindthework
Setupguilds/ad-hocteamstoallowfor
smootherinformationsharing andempower
yourcoworkerstofindwhattheyneedtoget
thejobdone

53. Diversity,Inclusion,
andBelonging

54. Reference: https://www.mckinsey.com/business-functions/organization/our-insights/why-diversity-matters

55. “
”
THE INNOVATIONS DO NOT HAVE TO BE REVOLUTIONARY OR
THE EXCLUSIVE DOMAIN OF NEW OR IMPROVED PRODUCTS.
THE IMPROVEMENTS CAN BE INCREMENTAL AS THEY ARE AT
TOYOTA, OR THEY CAN BE IN BUSINESS SYSTEMS AND
PROCESSES AS THEY WERE AT DELL.
- IRA KALB, MARSHALL SCHOOL OF BUSINESS, USC HTTP://
WWW.BUSINESSINSIDER.COM/INNOVATE-OR-DIE-A-MANTRA-FOR-EVERY-
BUSINESS-2013-7?IR=T

56. Adopt InnerSource to
take ownership of your
work

57. Adopt InnerSource to
take ownership of your
work

58. Software
Development
Design
Project
Management
Operations
Security
Domain
Experts
Customer
Support
Executive
Leadership
!
Solution: Adopt InnerSource

59. Solution: Adopt InnerSource
Reference:https://paypal.github.io/InnerSourceCommons/

60. Establish an inclusive
workflow that is structured
to be welcoming

61. “
”
RESULTS: MEN WHO SPOKE UP WITH IDEAS WERE SEEN AS
HAVING HIGHER STATUS AND WERE MORE LIKELYTO EMERGE
AS LEADERS. WOMEN DID NOT RECEIVE ANY BENEFITS IN
STATUS OR LEADER EMERGENCE FROM SPEAKING UP,
REGARDLESS OF WHETHER THEY DID SO PROMOTIVELY OR
PROHIBITIVELY
- SEAN R. MARTIN HTTPS://HBR.ORG/2017/11/RESEARCH-MEN-GET-CREDIT-
FOR-VOICING-IDEAS-BUT-NOT-PROBLEMS-WOMEN-DONT-GET-CREDIT-FOR-
EITHER

62. Solution: Establish an Inclusive Workflow

63. Solution: Establish an Inclusive Workflow

64. Solution: Establish an Inclusive Workflow

65. Solution: Establish an Inclusive Workflow

66. Form a team devoted to
making sure everyone at
your company feels included

67. “
”
ONE WAYTO ADDRESS THIS CHALLENGE WOULD BE FOR
MANAGERS TO AMPLIFY WOMEN’S IDEAS BY INTENTIONALLY
GIVING EXTRA ATTENTION TO THEIR SUGGESTIONS. AFTER
ALL, IF OUR NATURAL TENDENCY IS TO GIVE LESS
RECOGNITION TO WOMEN’S IDEAS, THEN WE WILL NEED TO
MAKE AN EXTRA EFFORTTO OVERCOME THIS BIAS.
- SEAN R. MARTIN, HTTPS://HBR.ORG/2017/11/RESEARCH-MEN-GET-CREDIT-
FOR-VOICING-IDEAS-BUT-NOT-PROBLEMS-WOMEN-DONT-GET-CREDIT-FOR-
EITHER
Solution: Form a Team

68. Solution: Form a Team

69. Makeiteasyfor
everyonetobetheir
best
AdoptInnerSource,chooseaninclusive
workflow,anddevoteateamtothecause

70. TheNextFrontier

71. References
• “Javaretrainingcostswillbehigh”, http://www.computerweekly.com/feature/Java-retraining-costs-will-
be-high
• JulietteReindersFolmer “Promoteyouropensourceprojects”,https://speakerdeck.com/jrf/promote-
your-open-source-project-with-github-pages
• “WhyDiversityMatters”,https://www.mckinsey.com/business-functions/organization/our-insights/why-
diversity-matters
• “InnovationIsn'tJustAboutBrainstormingNewIdeas”,http://www.businessinsider.com/innovate-or-die-a-
mantra-for-every-business-2013-7?IR=T
• “TakeOwnershipofYourWork:AdoptInnerSource”,https://medium.com/@baspeters/take-ownership-
of-your-work-adopt-innersource-55e57c0dc8f5
• “Research:MenGetCreditforVoicingIdeas,butNotProblems.WomenDon’tGetCreditforEither”,
https://hbr.org/2017/11/research-men-get-credit-for-voicing-ideas-but-not-problems-women-dont-get-
credit-for-either
• “CollaborationWillDrivetheNextWaveofProductivityGains”,https://hbr.org/2012/05/collaboration-will-
drive-the-n