Jay Lyman 451 ResearchBrent Beer GitHubSteven Anderson Sendachi talk about these topics:
Cloud, DevOps, agile development capability and adoption of containers are all important in both perception and reality.
Enterprise adoption of cloud computing, DevOps, agile development and containers are all growing, including production use.
Modernizing applications to SaaS & migrating them to the cloud are equally important as net-new, so-called ‘cloud-native’ applications.
Advantages and benefits of these technologies and methodologies center on: flexibility and speed, cost reduction, improvements in resiliency and reliability and fitness for new/emerging applications.
Barriers center on: lack of internal skills, immaturity, lack of familiarity, satisfaction with current technology, cost and security.
2. www.sendachi.com
House Keeping Items
• A copy of the presentation will be made available to attendees.
• There will be a Q&A session after the presentations.
• To ask a question, just click the “Questions” button on the webinar
interface to submit your question.
• We will answer as many questions as possible.
• Please provide feedback at the conclusion of the webinar.
3. www.sendachi.com
451 Perspective on DevOps
• Cloud, DevOps, agile development capability and adoption of
containers are all important in both perception and reality.
• Enterprise adoption of cloud computing, DevOps, agile development
and containers are all growing, including production use.
• Modernizing applications to SaaS & migrating them to the cloud are
equally important as net-new, so-called ‘cloud-native’ applications.
• Advantages and benefits of these technologies and methodologies
center on: flexibility and speed, cost reduction, improvements in
resiliency and reliability and fitness for new/emerging applications.
• Barriers center on: lack of internal skills, immaturity, lack of familiarity,
satisfaction with current technology, cost and security.
4. www.sendachi.com
Technology Adoption
Source: 451 Research, Voice of
the Enterprise: SDI Q4 2015
Which of the following
best describes your
organization’s approach
to new technology
adoption?
9.4%
38.9%
41.7%
10.0%
We are among the first adopters of a new technology
We are in the early majority of adopters
We are in the late majority of adopters
We are among the last adopters of a new technology
n = 748
All Respondents
5. www.sendachi.com
Adoption of Public Cloud
Source: 451 Research, Voice of
the Enterprise: SDI Q4 2015
Which of the following
best describes your
organization's adoption
of public cloud?
21.0%
17.0%
9.3%
23.9%
12.9%
15.8%
Discovery and Evaluation
Running Trials/Pilot Projects
In Test and Development Environment
Initial Implementation of Production
Applications
Broad Implementation of Production
Applications
Not In Plan/Never Considered/No Interest
n = 804
Infrastructure Respondents
6. www.sendachi.com
Implementation of Containers
Source: 451 Research, Voice of
the Enterprise: SDI Q4 2015
Please indicate your
organization’s
implementation status
for Containers (e.g.
Docker, CoreOS).
16.6%
17.9%
3.6%
5.4%
6.1%
50.3%
In-Use (Not Including Pilots)
In Pilot/Proof of Concept
Planning to Implement In the Next 6 Months
Planning to Implement In the Next 12 Months
Planning to Implement In the Next 24 Months
Not In Plan
n = 553
Infrastructure Respondents
7. www.sendachi.com
Agile Development Metholodogies
Source: 451 Research, Voice of
the Enterprise: SDI Q4 2015
Does your organization
utilize agile
development
methodologies for
application
development?
65.1%
34.9%
Yes
No
n = 670
Infrastructure Respondents
8. www.sendachi.com
DevOps
Source: 451 Research, Voice of
the Enterprise: SDI Q4 2015
Does your organization
currently utilize DevOps
approaches?
39.6%
60.4%
Yes
No
n = 568
Infrastructure Respondents
9. www.sendachi.com
Application Deployment in the Cloud
Source: 451 Research, Voice of the
Enterprise: Cloud Computing, Q3
2015
What is your
organization's most
common approach to
application
deployment within a
cloud environment?
36.6%
32.1%
31.3%
Modernizing existing applications by moving to
hosted software or Saas
Deploying new applications that we didn’t have
before cloud
Migrating existing applications to cloud
infrastructure
n = 1040
Cloud Respondents
10. www.sendachi.com
Application Types Moved to SDI
Source: 451 Research, Voice of
the Enterprise: SDI Q4 2015
What types of
applications have you
moved to Software-
Defined Infrastructure at
your organization?
56.9%
43.1%
32.6%
31.5%
29.8%
28.7%
24.3%
3.9%
16.0%
New Applications
Application Testing and Development
Custom, In-House Applications
Non-Critical Applications
Packaged, Off-The-Shelf Applications
Legacy Applications
Mission-Critical Applications
Other
None
n = 181
Infrastructure Respondents
11. www.sendachi.com
Benefits of SDI
Source: 451 Research, Voice of
the Enterprise: SDI Q4 2015
What do you believe
are the key benefits
of implementing
Software-Defined
Infrastructure?
65.1%
38.4%
32.4%
24.4%
12.9%
6.3%
4.4%
1.7%
0.4%
Improvement in Agility/Flexibility (e.g. Roll-out New
Applications/Services Faster)
Reduction in Management/Overhead Costs Through Greater
Automation, Standardization
Improvement in Infrastructure Resilience/Reliability
Reduction in Hardware Costs by Moving to
Standard/Commodity Hardware
Better Fit for New/Emerging Applications
Improvement in Security
Reduction in Vendor Lock-in
There are No Benefits in Software-Defined Infrastructure
Other
n = 544
Infrastructure Respondents
12. www.sendachi.com
SDI Barriers
Source: 451 Research, Voice of
the Enterprise: SDI Q4 2015
What do you believe are
the key barriers to
adopting Software-
Defined Infrastructure at
your organization?
42.2%
39.5%
31.1%
20.2%
16.9%
16.7%
15.1%
13.8%
10.7%
7.3%
6.7%
6.4%
5.3%
4.0%
Lack of Internal Skills
Low Maturity
Lack of Familiarity
Current Technology is Sufficient
Too Expensive
Increased Risks in Security
Over-hyped Technology
Management Resistance
Not the Right Timing
Increased Risks in Resiliency/Uptime
Too Disruptive
Not a Good Fit
There are No Barriers
Other
n = 550
Infrastructure Respondents
13. www.sendachi.com
Top IT Pain Points
Source: 451 Research, Voice of
the Enterprise: SDI Q4 2015
What are the top three
IT pain points at your
organization?
79.2%
41.7%
41.7%
33.3%
31.3%
20.8%
14.6%
12.5%
10.4%
Cost/Budget
Insufficient Staff
Legacy Software Issues
Aging Infrastructure
Organizational Issues
Infrastructure Management
VM Monitoring and
Management
Capacity Planning
Vendor Management
n = 48
Infrastructure Respondents
14. www.sendachi.com
What is GitHub?
• GitHub is the platform for collaboration for developers
• It’s not just some place for holding your code, but it’s where you talk
about your code, and find out what you’re shipping next
• It’s where people experiment on new ideas and before those
experiments go live, they communicate to the correct teams to let
them know about those ideas
• It’s what you plug your tools into to keep everyone in the loop and
save on context switches
21. www.sendachi.com
Increasing Developer Happiness
• Let developers focus on the code not the meeting
• Let the developers use the tools that they are comfortable with and
happy with
• Microsoft said in 2015, “We have been absolutely thrilled with the
pull-requests we have been receiving.”
23. www.sendachi.com
What Do Enterprises Need to Accomplish?
• Solve the hard problems
• Accelerate development efforts
• Reduce costs
• Eliminate the barriers between business and tech
• Execute against strategy for more effectiveness in a technology
driven competitive environment
• Drive the perpetual creation of lasting value through real change
• Pair up to educate and enable continued evolution
24. www.sendachi.com
Here’s the Current State
• Industry is in the midst of a sea change where software development is a highly integrated
activity across the business
• The creation of software is becoming less segregated/individualized and more
collaborative/socialized
• Formerly novel concepts around methodologies, tools, technologies and frameworks are
now proven value drivers:
• Agile
• Lean
• XP
• Microservices
• Virtualization/containerization
• Cloud
• Automation
26. www.sendachi.com
GitHub Represents an Enterprise Inflection Point
• As enterprises demand greater responsiveness the following is
necessary:
• Large teams broken down into a matrix of smaller teams working
more efficiently on smaller pieces
• Increased collaboration and visibility across the software
development domain is the MOST CRITICAL component of success
• The lines between technical and formerly non-technical
contributions need to be blurred (i.e. document sharing along side
coding as part of the same value chain process)
27. www.sendachi.com
What Needs to Change?
• To take full advantage of the power of GitHub as the nexus of your collaborative software development efforts, your organization needs to:
• Culturally embrace collaboration as a key tenet
• Executive/leadership sponsorship and support
• Internal evangelism
• Train at the IC, team and organizational levels on the value that collaboration creates, not just on the use of the tool
• Train on how GitHub can be used to facilitate collaboration and visibility
• Consistently reiterate that collaborative software/product development on Github creates value for the developers, for the team, for the company and for the
customers
• Showcase wins where GitHub and collaboration created:
• Reduced effort
• More velocity
• Less time/money/effort required to do more of the right things
• Higher customer satisfaction
• Higher quality
• Restructure teams if necessary, modeling after team structures (internal or external examples) that more effectively exemplify value creation and execution
against goals
• Skills blended teams (across functional areas) with common goals
• All team members utilizing GitHub as the platform of record
• Tune/modify methodologies if necessary
• Make the KPIs visible
• Cycle times
• Customer sat
• Overall effort
Probably also going to talk about collaboration
These things are true for doing work with the open source community, but that aspect of community can happen on GitHub Enterprise as well
Quick view from a microsoft project.
See the integration with detecting if cla is needed, cross referencing another issue (using issues for project management and keeping the pieces tied together)
CI is passing, but then review happens
- Review comes in, edits come in after that. CI passes!
- We get a :+1: and merge it in.
- GitHub of course is this collaboration platform, but it’s also a place for your tools to work with you too, not just CI but code quality as well
Even a test coverage app as well.
and these could be used in conjunction with our feature of protected branches to ensure these things have a good status before we can merge. It can be flexible
Deployment of applications into a cloud environment doesn’t have to happen in a silo
Integrate this into the same workflow you had with any of your other applications.
Heroku is a great platform to use for applications. Their ability to integrate with GitHub is phenomenal and something worth looking into
https://blog.heroku.com/archives/2015/9/3/heroku_flow_pipelines_review_apps_and_github_sync
This is Waffle. It is one of the great examples of our integrations directory and a tool that integrates right along side your workflow
You want Agile? Be flexible in your workflow, use a tool that allows developers to test something out and work fast and get relevant feedback fast
Collaboration is key on GitHub
Collaboration happens asynchronously in the pull request. This means that if I ask for someone to look over my change, they can get to it in 5 minutes or whenever is convenient for them. I don't have to interrupt everyone with meetings just to look over code. Our code review meetings don't need to interrupt our regular day. This allows the developer to not be interrupted so they can be happier and produce more work. We want to produce great code and features, not be in meetings to talk about the features we are working on
Developer happiness is something I hear constantly being brought up when companies talk about GitHub. When you’re talking about retaining some of the top talent, one of the ways you do this is by keeping them happy. You do that by keeping GitHub close
Quote: We have been absolutely thrilled with the pull-requests we have been receiving (shout outs: BradBarnich, mrange) as well as the engagement on language design. We cannot thank you all enough for joining us on our exciting journey into open source.
https://blogs.msdn.microsoft.com/dotnet/2015/07/02/thank-you-for-your-contributions/
- Need notes from 451
Probably also going to talk about collaboration
These things are true for doing work with the open source community, but that aspect of community can happen on GitHub Enterprise as well
- Need notes from 451
Probably also going to talk about collaboration
These things are true for doing work with the open source community, but that aspect of community can happen on GitHub Enterprise as well
- Need notes from 451
Probably also going to talk about collaboration
These things are true for doing work with the open source community, but that aspect of community can happen on GitHub Enterprise as well
- Need notes from 451
Probably also going to talk about collaboration
These things are true for doing work with the open source community, but that aspect of community can happen on GitHub Enterprise as well