What businesses should know about DevOps
Many organizations are failing their software projects. Failure in delivering on time, on budget, on promises. These failures are often related to challenges in software development processes and delivery methodologies. To resolve this, this requires the use of an innovative and more effective approach: DevOps.
Things to consider when implementing DevOps
- The DevOps approach is supported by Agile Scrum, ITSM and Lean practices amongst others, whereby an adaptive, incremental approach is used to deliver continuous business value, as efficiently as possible.
- Besides the “technical” side of DevOps, it will also bridge the gap between the development team and operations teams to establish efficiencies and remove bottlenecks and obstacles between the two groups, whether cultural or technical.
- However, DevOps is not about culture change only! It is a business transformation driven by people, processes, and products.
- A deployment pipeline should be established ensuring:
- A common lifecycle is followed by the development team
- Continuous feedback is used to align and realign development results with business outcomes
- A tools chain is in place to support end-to-end DevOps value streams
- With more and more customers directly interfacing with business processes and services, an ongoing delivery of business value is required
- A clarification of DevOps concept and associated methods, values, principles are required
- If you practice Agile Scrum, Lean, ITIL, EA, then DevOps introduction is a natural evolution for your organization. DevOps is supported and enabled by most (if not all) of these best practices.
To DevOps or Not DevOps?
The items below are meant to help you trigger the discussions on DevOps.
- What is the nature and scope of your applications?
- What is the frequency of deployment/releases required by the business?
- How often are applications successfully released?
- How heavy is the organization on control processes, documentation, and governance?
- Do you currently follow or have Agile Scrum/Lean IT practices in place?
- Do you have any challenges associated with escalation of incidents and problems between helpdesk and Level 2 & 3?
- Do you have backlog associated with Change Management activities?
- Do you have clear roles and responsibilities defined within the development and operation functional groups?
Signs Your Organisation Needs DevOps
- There is no code integration. Coding synergy is missing amongst developers
- There is no configuration management or code repository
- Lack of testing model, automation, or challenges trying to capture delivery timeline or meet budget constraint
- ADLC/SDLC is not followed, or followed without the “shifting left model”
- Tools are not integrated and do not have a proper end-to-end support
- There are always issues in terms of escalating incidents and problems; sometime disappearing into a blackhole
- Always late delivering, delaying business outcome/value
- Unhappy customers
- Clashing culture/people (pointing fingers), no trust amongst different teams
- Lost market share
- Constant re-work, bottlenecks, too much governance/micromanagement, rigid processes, overwhelming (or complete lack of) documentation
- Development team has conflicting priorities,
- Tedious development cycle whereby business complains and considers outsourcing
- Lack of measurements/feedback
- Requirements are always changing and needing to start over
If you think DevOps can help transform your organisation to be leaner, better organised, more efficient, DevOps may be the solution for you.