The issue we face today is that technology is moving its foundation. Almost every platform you grew up with was built for on premise use. With the introduction of cloud computing, the way that programs are created and deployed needed to change - and it has! Deployments and updates need to be happening in measurements of seconds and hours - not days and weeks and development cycles need to be completed in a matter of days and weeks, not months and years.
When people hear about the term "Development Operations " they immediately think of automation and automating themselves out of a job. The reality is that nothing could be further from the truth. This section is dedicated to shining some light on this area to help the community at large understand why development operations is essential to your future SharePoint landscape.
To understand the benefit of development operations fully you must first understand the problem, which is driven by a need.
The problem with most IT organisations today is that they amass very large amounts of Technical Debt
Technical Debt - is usually brought on by failure to deliver on previous promises and compounded by future over commitments to make things "right" - The business functions get promised more and less is delivered.
This cycle continues until the technical debt is so large that the business either writes it off as a "White Elephant" or they move in another direction. Needless to say IT are generally blamed and that's yet another black mark against the department.
Since the major economic crash in 2008, everyone is under pressure to deliver more with less IT projects costing millions and delivering nothing are just not tolerated.
Development Operations was conceived around this time and helps to reduce the technical debt, streamline the delivery process and automate operations.
DevOps is a software development method that emphasizes communication, collaboration (information sharing and web service usage), integration, automation, and measurement of cooperation between software developers and other IT professionals. The method acknowledges the interdependence of software development, quality assurance (QA), IT operations, and aims to help an organization rapidly produce software products and services and to improve operations performance.
The Goal of Dev Ops?
The specific goal of a DevOps approach is to span the entire delivery pipeline. They include improved deployment frequency, which can lead to faster time to market, lower failure rate of new releases, shortened lead time between fixes, and faster mean time to recovery in the event of a new release crashing or otherwise disabling the current system. Simple processes become increasingly programmable and dynamic, using a DevOps approach, which aims to maximize the predictability, efficiency, security, and maintainability of operational processes. Very often, automation supports this objective.
What does all that actually mean?
Opportunities are usually identified in a post-mortem conducted at the end of each sprint or deployment.
If appropriate, the ability to automate the opportunities is triaged; the ones that save the most re-occurring
time are completed first.
This then speeds up the next sprint or deployment. The saved time is then invested in more automation, thereby saving more time creating a fly wheel effect.
Over a short period of time this approach allows you to finally reduce the yechnical debt within your organisation.