InnerSource Presentation

Transcript

1. Establishing an InnerSource Development Model Christian Weber, Senior Solutions Engineer
 github.com/webdog webdog@github.com classicwebdog
2. 1960 Simple Few 100K Few 400K Many Global 10M Team 2.5M 50M Connected 2020 2B Autonomous Today Complex Global 150M Assisted A brief history of time
3. Source: https://www.flickr.com/photos/hades2k/7001927337
4. Collaboration SCM Automation InnerSourcing Mindset
6. So what is InnerSource then? • Takes the best of the Open Source Community • A different way of thinking about Software Development • Empowering People
7. What does it mean to be ‘Inner Source?’ • Open Collaboration • Open Communication • Separating Contributions from Integration
8. Core Tenets of Inner Source • Open by Default Access to Source Code • Transparent development environments • Peer Review • Informal communication channels • Self-Selection • Frequent Releases • “24/7” Development
9. Using GitHub with InnerSource
10. Using GitHub with InnerSource
11. Using GitHub with InnerSource
12. Using GitHub with InnerSource
13. Decrease time to market by leveraging labels, projects and project automation capabilities
14. Improve community collaboration with repository based issues, pull requests, wikis and project boards. Allow community members to vote on features with reactions
15. Unified search across your repositories to leverage the knowledge of your community members and improving reuse
16. Increase knowledge worker efficiency leveraging a pull request workflow with integrated reviewers and assignees
17. Enforce compliance policies with branch statuses, branch protection, required reviews and inline conflict resolution
18. Collaboration By adopting social collaboration tools, companies can raise productivity by 20-25% McKinsey and Co. Study
19. Collaboration statistics PRODUCTIVITY By adopting social collaboration tools, companies can raise productivity by 20-25% FAILURE 96% of execs cite lack of collaboration or ineffective communication as the main source for workplace failures. RETENTION Poor communication and unsupportive company culture is an employee-retention issue for between 20%-30% of organizations. - McKinsey and Co. Study
20. Automation
21. Quality & Security
22. Accelerating the SDLC Workflow to boost Developer Productivity Integrations to Boost Developer Productivity • Developers use their favorite tools • CI/CD automate build and delivery • Give insight to the entire lifecycle • “Best of Breed” vs Opinionated workflow
23. Right Brain Left Brain
24. Collaboration + SCM + Automation =