Concept to Code to Run - Simplify Enable Exploit

Explore the transformative journey from concept to code to runtime, unraveling the power of DevOps.

Discover how synergies between Architecture, Engineering, and DevOps simplify, enable, and exploit innovation in a highly regulated environment.

Srivatsan - Transformation leader and full stack technologist with 20 years of experience in Technology Management and Operations including Strategy, Architecture, Governance, Design, Delivery, Automation and Runtime management across major financial institutions globally.

Transcript

1. Concept to Code to Run Simplify, Enable & Exploit - Srivatsan
2. What I do Head, Architecture, Engineering and DevOps - Fix Architectural Contradictions and Engineering Enigmas - Make solutions and systems more Predictable and Measurable - Constant exploration into enabling people to win Business Value, Productivity and Quality Battle - Add more evidence based opinions to opinionated developers clash in an epic quest for productivity (& hobby) - Handling constant storm of Architectural visions, Engineering constraints and occasional Existential crisis – Cloud vs On-Prem, Agile vs Waterfall, Mainframes were better
3. What if I Say Tweaking Branching Strategy will reduce my change related issues by 30% and increases code convergence by 60% Of every 1$ spent on Software Build and Delivery, 30-35 cents are wasted due to various in-efficiencies Standardizing Application Profiles to 3-5 patterns can give Developers and DevOps team 4 more hours of sleep, reduce build time by 40% and reduces code complexity by 30-40% Silo teams are ok, Waterfall is ok, legacy code is ok , on-prem ok provided they follow standard patterns and deliver value. 50% of initiatives fail as we end up using wrong solution for right problem and vice versa.
4. Lets take one Application Profile There are multiple attributes we need to bring together for an application of this profile - Functional Disposition - Application Design - Coding Architecture - Data - Security - Testing Problem with Distributed System is that it is distributed for flexibility Flexibility comes with Discipline and Accountability https://microservices.io/patterns/microservices.html
5. Anchor DevOps Differently From Enabler to Influencer Each player type has a strategic impact throughout the game, just as different DevOps principles affect the software development lifecycle. • Attacking Midfielder: Innovation, concept exploration, rapid prototyping, upstream influence on how to design and build applications • Deep Lying Midfielder: Standardization, architectural considerations, frameworks (Development Framework, Developer Portal), Software Delivery Methodology Optimization, Influencing Estimation Process • Holding Midfielder: Automated processes, CI/CD, deployment pipelines, maintenance and administration of tools • Defensive Midfielder: Security, testing, proactive monitoring, Value Stream Mapping Emphasizing again: Bringing positive impact to both Top-Line Business Value and Bottom Line Efficiencies
6. Let us take an example – Application Architecture and Design Standard Application Builds (3-5 Patterns) Satellites are built to comply with Satellite Launch Vehicles Standards (or Constraints) •Precision Engineering can be enforced in Pipeline Discipline in application development to ensure reliability and cost optimization. •Reusable Components/Unwanted Components Standardized Modules or Libraries can be enforced for software development needs a similar approach to promote efficiency and consistency via Developer Portal / Development Framework •Consequences of Failure Fail the builds if they don’t comply with design, coding and security quality needs. Influence Architects to comply with 3-5 Application Profiles (Similar to Satellites and Launch Vehicles)
7. What all these have to do with ”Concept to Code to Run”
8. Let us go through Software Delivery Methodology Software Factory with • Multiple Software Assembly Lines • Measurable KPI’s • Mechanisms to remove wastes & bottlenecks • Automated Approaches to Testing • Differentiated Approaches to release Diagram Reference from – Driving Digital Transformation – By Dennis Khoo Who can bring all these stages and process together?
9. What can DevOps provides across the stages Concept Application Design and Coding Code Quality Analysis Build Quality Assurance Deployment Ideation and Collaboration Tools Journey Design Tools Requirement Lifecycle Management Tools IDE & Development Workplace Development Standard Developer Portal API Lifecycle Software Component Catalogue Configuration / Infrastructure Provisioning Static Code Analysis Software Composition Analysis SAST Code Quality Insights Build Tools Source Code Management Repo Test Management Unit Test Automation Test Data Management Test Virtualization Load/Stress/ Vulnerability Change Management Deployment Orchestration Software Delivery Lake (Mapping from initiatives to Epics to Functions Points/Stories to Commit ID/Test Cases all the way till Deployment) Assistance Tools using AI (Codellama, Mistral, Co-Pilot etc) Value Stream Insights Enable and Influence with evidence based approach - Application Design - Convergence - Standards across value chain - Defining Application Profiles - Reduction of Cycle Time in Everything
10. What Insights Satisfaction Customer Satisfaction (CSAT) Financial Cost Per Customer Efficiency Time spent to build new features vs running existing features Revenue Technology Spend vs Revenue Innovation Time taken to bring new services to market Cost Trend Analysis of cost of product sold NPS Net Promoter Score Security Security Incidents per month Agility Time to provision new application and features Release App releases per day/week Cycle Time Cycle Time across each stage of development to deployment Defect Leakage Defect Leakage across each stage of development to deployment Stability/ Resiliency App Uptime (%), Mean Time to Repair/Recover Failures Reverted Deployments (%) Performance Performance before and after releases NDS Net Developer Score for Developer Experience Cost Total Cost of Ownership Performance Performance before and after (response, latency and contention) Efficiency % of infrastructure running on-demand Capacity Capacity Consumed (%) vs Remaining (%) Utilization & Consolidation Rightsizing Savings (%) and Workload per host (%) Lifecycle Management Platforms N-1 version or above Stability/Resiliency App Uptime (%), Mean Time to Repair/Recover Automation % Automated Provisioning Cost Total Cost of Ownership Top Line Business Growth Bottom Line Efficiencies Design Thinking / Lean 6-Sigma or whichever methodology Agile at Scale or Waterfall (Metrics Could Differ) Identify your sources of growth and prioritises initiatives for rapid and tangible results.