Devops for business : Efficiency & Innovation

Devops for business : Efficiency & Innovation

• 1.
  DEVOPS Drive for Efficiency& Innovation Technology & Business
• 2.
  Product, IT, HR,finance, Sales, etc. - everyone in the chain adds value to the business. DevOps : - is not a set of tool or platform - continuous drive for efficiency. - is a commitment to keep removing inefficiencies in the entire chain by adopting evolving best practices. Very deliberate choice, requires commitment & discipline, benefits over time. Benefits the organization just as evolving diet & exercise benefits your overall physical & mental health. You can survive without it but never enjoy the benefits. Devops enables the business to commit to short rapid bursts of change Needs a tight collaborative team to react & deliver that change. Starts with building a technology tool set but it does not end with technology. Not pursuing efficiency in the entire business negates the value of adopting devops in IT. Business has a key role to play.
• 3.
  Commitment to DevOpscan manifest as a need for: - continuous engagement with customers, - continuous evolution of services, product, business capability offerings - continuous reaction to competitive market dynamics - faster changes than legacy silos/structures would allow Results: - rapid business decisions, faster service/product innovations , Reduced TTM - cultural shift in how teams work to deliver all of the above to a rapidly evolving digital market. DevOps lacks a definition or prescriptive approach Challenges conventional thinking to "define structure & eliminate risk" Instead its about maintaining flexible structures, managing the risks of constant short- lived change.
• 4.
  Proactive & Innovative Innovation (not routine) adds new value to an organization.  Innovation is ‘change’ by definition  Innovation has to be pursued by people (won’t happen itself) Free up peoples time to be proactive & innovative to add value. Remove Inefficiencies: Easy win - Completely automate routine processes that don’t generate new value. (generating routine reports, app deployments, regression/sanity testing) Manual processes should always focus on adding new value (defining new business opportunity, creating new designs or code) Have a long term vision but focus on executing short bursts of change every sprint.
• 5.
  Disciplined & Collaborative: Agile ois timed short bursts of progress, rapid decisive re/action & execution to add immediate value. o is applying a lot of rigour to defining immediate requirements, solutions & immediate delivery. o does not allow procrastinating, indecisiveness, changing decisions mid-way, lack of rigour Reliable & punctual o All teams deliver to sprint timelines – agree to stick to it. o Don’t procrastinate to achieve the "Perfect solution" or "future proof solution" - its a myth. o more time = more costs + higher risks + lost revenues, it dilutes the value generated over time. Collaborative & thorough o Collaborate pro-actively to be thorough - demand to leverage the expertise across teams o Discourage internal politics/competition - it is highly demoralizing & kills all collaboration o Aim to get it right the first time. Re-work chokes delivery, has incremental costs (time & money) o Actively break down team boundaries - Pursue the ideal of "one team - one dream“ o Its easy when everyone takes the initiative.
• 6.
  Fail fast ifyou must o Identify the reason & fix failure points as early as possible. o Retrospectives make sense only when you stick to a time-line. o Lack of rigour or collaboration are never acceptable reasons in devops. Improve cost efficiency: o Every company needs infrastructure, people, services, software, consultancy o Mixture of build, buy, lease – Try to pay for what you use & when you want to use it Improve market insight: o automated real-time data mining, o sentiment analysis, o trend analysis, o market reports o Know your customer (not just compliance)
• 7.
  SECURITY is MESSY!! onot a differentiator, does not generate revenue o but protection is absolutely critical to business cost of security breach / getting hacked o best case - deep reputational damage! o at worst - destroys the business! security is responsibility of all teams o Sales, Compliance, Product, IT – channels, regulation, features, technology o CISO should provide guidance to various groups. o Keep abreast of new security developments - online courses, certifications, webinars, meetups. cost of fixing a security bug: o least in dev, 15 times in testing, 100 times in production o embed security collaboration into sprints o product & BA should include security requirements. o security screening in code build pipelines, product pen-testing Prioritize security backlog & get over the hill.
• 8.
  Anti-patterns / warningsigns Project Heroes: o extraordinary effort from small number of people to save project at the nth hour o leads to cutting corners & mediocre results o ad-hoc deadlines are not sustainable and eventually leads to resentment o hides recurring problems like poor insight / planning / drive o talented people who are fire-fighting in silos cannot collaborate & innovate Devops Silo: o small team of people dedicated to devops for a long time o sends the message that "devops is not for everyone" o start with a silo but involve everyone gradually o everyone should adopt the principles, collaborate across team silos to innovate better
• 9.
  Anti-patterns / warningsigns Start Automating everything: o Impossible to automate everything together, don’t try this. o Common criteria: - most repetitive tasks - takes most time to automate, - highest ROI work first Kick the can forward: o Devops is "Continuous Improvement" in short bursts every sprint (not next sprint) o Retrospectives are important for business – Identify & deliver improvements each month o If your team is saying, "We'll do better next time. Right now we just need to hurry," they're not continuously improving. o If consecutive projects keep running into problems, we haven’t been continuously improving. o take individual responsibility to identify project risks very early in the cycle.
• 10.
  How Dev pursuesAgility & Innovation: o continuous learning & certifications. o version control, release branching strategies o continuous integration, continuous testing, o automated deployment, session replication, automatic failovers o deeper stack automation: infrastructure as code(machines, network, security, etc.), o performance/reliability metrics, automatic scalability o results: reliability, predictability, metrics, responsive, quicker remediation o keep teams fluid, spread the knowledge & skills, normalize the stack How infrastructure pursues Agility & Innovation: o continuous learning & certifications. o new tool set for managing VMs/servers, packer, terraform o automated provisioning & configuration of hardware & network o very deep collaboration with security teams (internal & external) - Zero Trust model o new monitoring software - Eset, Zabbix, Dynatrace, DC Agent & more o Role based Access Control (RBAC) at every layer - AD integration, NTP, sudo etc. o immutable Secure images at presentation & business layer. Target Benefits: Throughput & Stability •‘n’ deployments / day •TTM < 1 hour •MTTR < 1 hour •Change failure < 15%
• 11.
  How will businesschoose to implement Agility & Innovation? For each business leader to reflect on: o are routine processes adding new value ? o are internal team structures flexible ? o are you killing the internal politics (collaboration & performance, not silos & blame)? o are you leveraging collaboration with other teams ? o are you thorough & getting it right the first time ? o what does continuous learning look like in your teams ? o how do you measure efficiency ? o are you able to read & respond to competition/regulation quickly ? o what does innovation (i.e. Value addition) look like for teams ? •Speed to Market •Customer relevance •Product quality •Costs •Revenue •Market Share What Benefits will you measure?