book

Bridging the Gap: Turning Agile and DevOps Initiatives into Board-Level Wins

Name: Bridging the Gap: Turning Agile and DevOps Initiatives into Board-Level Wins
Author: Leo Bardelli
ISBN: 9798868820717

by Leo Bardelli

January 2026

Intermediate to advanced

436 pages

6h 37m

English

Apress

Read now

Unlock full access

Bridging the Gap
Introduction
Why Does a Company Need to Follow a Model?The Architects’ StoryWhat This Book Will Help You DoThe Missing Ingredients
Table of Contents
About the Author
1. The Agile Mirage
The Transformation GridlockAssessment Focus AreasFrom Assessment to ActionConnecting the DotsAgile Matrix AssessmentWhy Build ≠ DeployA Quick (but Important) Technical DetourBuildReleaseDeployWhy We Get This Wrong (and How to Fix It)The Strangulation PatternPhased ModernizationThe Hidden Business Impact of Build QualityThe Fragility TaxOutcome: A Prioritized Tech Debt Roadmap AddressingTime to Check How Your Deployment Strategy IsQuality and AcceptanceWhy It MattersGround Truth It CapturesKey Takeaways
2. Stakeholder Engagement
Why It WorksNumbers Don’t LieFinancial Translation GuideProfit and Loss (P&L) StatementCash FlowBalance SheetSaaS MetricsReframing Costs As Efficiency DividendsStep Justification FrameworkExecutive Dashboards That WorkThe Quarterly Executive Check-InBonus: Internal Tool Justification TemplateBuild Time ReductionMTTR ImprovementTest AutomationWhy These Acronyms MatterBeyond the BasicsFinancial Metrics Cheat SheetReady-to-Use FrameworksThe Real-LifeThe Channel ProblemCustomer Voice PortalStakeholder ScorecardsRoadmap HubThe Quarterly Planning RhythmThe KPI Dashboard That Wins Budget BattlesReport ThisKey Takeaways
3. Building a Culture of Transparency
Before the MetricsHow to Motivate Without ManipulatingTie Code to CashRadical Priority TransparencyIn Search of ValorFive-Step Cheat-SheetTo Delegate Is Not to Dump and WaitWhy Roles Come Before ReportsMetrics Don’t Need a Data-Science PhDTransparency As a Trust AcceleratorFrom Talking to Tracking—A 2-Week Starter PlanLooking OutsideKey Takeaways
4. From Travel Agents to Algorithms: Tourism Has Embraced the Digital Runway
Why Non-functional Requirements (NFRs) Make or Break Transformations1. Navigating Legacy Systems: Taming Technical DebtWhy It HurtsProactive ControlsMetrics of Success2. Incremental Modernization: Strangler Patterns and Hybrid ApproachesWhy It HurtsProactive Controls3. Cloud Migration and Data Integration: Avoiding Compliance PitfallsWhy It HurtsMetrics of SuccessBuilt-In CheckpointsIt Could Be a Spreadsheet, but a Dashboard Makes the Data TalkBridging the Gap: Analogies That ResonateKey Takeaways for Leaders
5. Making the Data Be Your Storytelling
Translating Tech to ROI, Operational Efficiency, and Competitive EdgeThe Now-Next-Later lensMore Tech Narrative Examples for the BoardLet’s Frame the KPIs from the Stakeholder PerspectiveChief Marketing Officer (CMO)/MarketingChief Operating Officer (COO)/OperationsChief Financial Officer (CFO)/FinanceChief Technology Officer (CTO)/EngineeringChief Revenue Officer (CRO)/SalesElevator Pitches and Board-Level OKRsOne North Star, Three HorizonsThe Sixty-Second PitchManaging Up: Process, Cadence, NarrativeUsing the Data Storytelling Arc to Win Boardroom DecisionsWhat Is the Arc?Why Use It with Our Board?Integrating Jobs to Be DoneArc Example: Friction-Free OnboardingContextAha MomentActionConnecting Features to Outcomes with Jobs to Be DoneJTBD and the Simple OutputsThree Real Use-Case ExamplesRecap Before You Move to the DevOps-Focused ExamplesDevOps Through the Same JTBD and ARC LensContext, the Job Behind Every DevOps DollarAha Moment, Three Levers That Turn Deployment Speed into MarginAddressing the Three Objections That Always SurfaceFolding DevOps into the Storytelling ArcMapping DevOps Levers Back to Stakeholder KPIsSeamless BridgeKey Takeaways
6. Mastering Metrics and Quality Control: Selling the Vision to Executives
A Metrics StoryKey KPIs: Lead Time, Release Frequency, Stakeholder SatisfactionIntroduction: The Right Metrics at the Right TimeLead Time: The Pulse of Delivery EfficiencyWhy Measure Lead Time?Implementing Lead Time TrackingRelease Frequency: Measuring the Heartbeat of DeliveryWhy Track Release Frequency?Capturing and Improving Release FrequencyStakeholder Satisfaction: Connecting Delivery to Customer ValueImportance of Stakeholder SatisfactionMeasuring Stakeholder SatisfactionConnecting the KPIs to Actionable DashboardsIntegrating with Multi-level Testing and Risk-Based Release ManagementReal-World Application: An Iterative ApproachThe Metrics Integration CycleWhy TAGs MatterWhat We StandardizeBusiness impactRisk If We Skip ItGovernance and ControlEffortHow the Data FlowsStandards That Make This WorkOperating RhythmTimeline and EffortGovernance and OwnershipSecurity and ComplianceCostsRisks and MitigationsSuccess Criteria for the First 60 DaysWhy This MattersSimple Read of the Deploys vs. NPS ChartConclusion: Strategic Clarity Through Focused KPIsKey KPIs—Multi-level Testing (Development, Regression, Integration, Acceptance)Understanding Multi-level TestingLevel 1: Development TestingWhat It IsWhy It MattersHow to Measure EffectivenessLevel 2: Regression TestingWhat It IsWhy It MattersHow to Measure EffectivenessLevel 3: Integration TestingWhat It IsWhy It MattersHow to Measure EffectivenessLevel 4: Acceptance Testing (Business-Driven Development)What It IsWhy It MattersHow to Measure EffectivenessMetrics in Practice: A Real-World Application of a Simple Test FrameworkIterative Improvement of Testing PracticesConclusion: Multi-level Testing Metrics As Strategic EnablersKey KPIs (Risk-Based Release Management—Matrix of Low to Critical)IntroductionWhy Heavy Risk Management Processes Are Detrimental in AgileSimplified Risk Assessment Within Agile QAUsing the Risk Matrix EffectivelyIntegrating Risk Assessment into Agile Testing LevelsDevelopment Testing (Unit and Code Reviews)Regression TestingIntegration TestingAcceptance TestingAgile-Friendly KPIs for Risk-Based Release ManagementTransparent Communication in Release NotesTwelve-Factor Alignment for Agile Risk ManagementPractical Example: Simplified Agile Risk ManagementIterative Improvement of Risk ProcessesConclusion: Agile Risk Management for Strategic Quality ControlBridging the Gap: Simple Metaphors That StickKey Takeaways for LeadersWhat to Say When the Data ConflictsFinal ThoughtWhy Does This Work Better

7. Launching OKRs and Managing Iterative Development
S.M.A.R.T. Examples (From Individual to Product Level)Bridging the Gap from Assessment to ActionWhy S.M.A.R.T. Is the Bridge Between Onboarding, Motivation, and GrowthS.M.A.R.T. Refresher and Anti-patternsGoal Cascade: Individual ➤ Squad ➤ Product ➤ BusinessConcrete Examples by Role (Onboarding ➤ Ramp ➤ Growth)Product OwnerArchitectEngineerQA/TestingUX/DesignMetric Patterns That MatterFlow MetricsQuality MetricsProduct MetricsS.M.A.R.T. Example LibraryLevel 1: Individual Annual GoalsLevel 2: Squad Quarterly GoalsLevel 3: Product Quarterly GoalsLevel 4: Business Semi-Annual OKRsCalibration and FairnessPractices for Effective CalibrationOnboarding Playbook Anchored in S.M.A.R.T.30/45/60-Day Onboarding ChecklistFirst 30 Days (Understand)First 45 Days (Contribute)First 60 Days (Own and Improve)Onboarding Support MechanismsHandoff Summary for Upcoming SectionsArtifacts ProducedHow S.M.A.R.T. Goals Enable Next StepsConclusion: The Clarity and Power of S.M.A.R.T.Turning S.M.A.R.T. Goals into Focused ActionDefining Value Stream MappingHow to Conduct a Value Stream Mapping SessionStep 1: Gather the Right TeamStep 2: Define the Scope ClearlyStep 3: Map the Current StateStep 4: Quantify Each StepStep 5: Identify Immediate IssuesStep 6: Prioritize Improvement OpportunitiesCommon Value Stream BottlenecksIdle Time Between Teams (Handoffs)Manual Approval DelaysTesting and Quality Assurance BacklogsEnvironment AvailabilityConnecting VSM Findings to S.M.A.R.T. GoalsUsing Dashboards to Identify Bottlenecks in Real TimeReal-world Example: Reducing Idle Time Between TeamsPrioritizing Bottlenecks Clearly and PracticallyDefined Ownership for Bottleneck ResolutionPreparing for the Next Step: Continuous Improvement and Feedback LoopsConclusion: From Insight to ActionContinuous Process Improvements and Feedback LoopsSustaining Improvement for Long-Term SuccessThe Importance of Continuous Process ImprovementBuilding Continuous Improvement from Your Maturity AssessmentCreating Effective Feedback Loops: Types and CadencesDaily Operational Feedback: The Daily StandupWeekly Tactical Feedback: Team RetrospectivesMonthly Strategic Feedback: KPI and Goal ReviewsQuarterly Executive Alignment: OKR RecalibrationAlignment Artifact: Continuous Improvement to Organizational GoalsMeasuring Continuous Improvement with PrecisionCase Study: Reducing Handoff Idle Time Through Continuous ImprovementStructuring Rituals for Sustainable Continuous ImprovementWeekly Improvement RetrospectivesBi-Weekly Cross-Squad Check-InsMonthly Continuous Improvement ShowcaseQuarterly Strategic Improvement ReviewClear Accountability: Tracking Improvement ActionsOvercoming Common Barriers to Continuous ImprovementResistance to ChangeAmbiguity or Unclear OwnershipInformation Overload or Data ConfusionLack of Consistent Follow-UpReal-World Application: Continuous Improvement in PracticeReinforcing Continuous Improvement with Leadership SupportPractical Leadership ActionsEnsuring Long-term Success: Revisiting and Refreshing Goals RegularlyRecommended Goal Refresh CadenceConclusion: Continuous Improvement As a Cultural NormKey Takeaways for LeadersFinal ThoughtWhy This Works Better
8. Enabling Continuous Integration and Automated Testing
Branching and Workflow Patterns (Main/Feature, Latest/Stable)Setting the Stage for Seamless IntegrationThe Problem We SolvedThe Pattern at a GlanceMain and Feature Branches: Rules That Keep the FlowRelease Candidates, Phased AdoptionHow the RC Fits the FlowLatest and Stable Tags: Simple Control PointsWhat These Tags MeanHow the Workflow Runs, End to EndRoles and OwnershipDefining Acceptance Early and Why It Belongs in a Branching StrategyChange Logs and Release Notes, Done by the PipelineGovernance: The Few Rules That MatterHow Does This Support Fast UAT Without Creating a Bottleneck?Hotfixes and RollbacksCommunications and Customer ImpactMetrics to Prove It WorksWhat Executives Should ExpectOperating Model and ScaleRisks and How We Mitigate ThemWhat Leaders Should Do NextA Day in the Life with Main, Feature, Latest, StableFrom Fifteen-Plus Activities to Fewer Than Five StepsTag Policy That Leaders Can TrustRelease Notes and Change Logs, Built by AutomationQuality Built in, Not Bolted OnThe Risk Matrix, from Analysis to ActionGovernance That Scales Across Teams and VendorsCompliance and Audit, Made Easier by TagsHotfix and Incident PlaybookHandling Edge Cases Without Extra BranchesTraining and Change ManagementMetrics, Targets, and What Good Looks LikeObjections You Will Hear, and Clear Responses“This Adds Work for Developers”“We Still Need UAT at the End”“Release Notes Never Reflect Reality”“Rollbacks Are Complicated”Cost and ROI in Plain TermsHow This Supports Business OutcomesPractical Checklist for LeadersSummary: The Executive ViewCI/CD Pipelines and Tooling (Automatic Checks, Fast Feedback)What and WhyHow We Got HereCI, the Integration PipelineWhat Runs on CICD, from Integrated Code to Deployed ProductWhat Runs on CDThe Acceptance Engine, Behaviors That RunTooling Choices: Keep It Simple and IntegratedService Levels for Feedback, What “Fast” MeansRelease Notes, Change Logs, and the Risk MatrixLatest, Stable, and, When Useful, RCCD Safety, Rollbacks, and HotfixesPeople and Roles, the Pipeline Does the BusyworkGuardrails That Keep the Pipeline FastWhat Leaders See and How to Read ItCost and ROI, Where the Value Comes FromRisks and How the Pipeline Reduces ThemPutting It to Work Next WeekA Week in the New FlowWhat “Fast Feedback” Means in PracticeAcceptance That Speaks BusinessThe Risk Matrix That Drives the Right EffortLatest, Stable, and When to Use RCAutomation That Removes BusyworkA Simple Playbook for Hotfix and RollbackAnti-patterns We Removed, and What Replaced ThemEnvironments and Data, What We StandardizedPeople, Roles, and the Handoffs We RemovedCosts, Limits, and How We Stayed PragmaticRollout Path That Works Across Teams and VendorsThe Executive Checklist for the PipelineSummary of the Business StoryWhite-Box vs. Black-Box Testing, Shifting LeftWhat Leaders Need to Know About the Two ViewsA Table for Quick OrientationWhy Shifting Left MatteredWhere Each Test Level LivesA Concrete Before and AfterRisk-Driven Depth, and When to Add an RCPeople and Roles, Fewer Handoffs, Clearer OwnershipWhat Leaders Watch to Govern Without a Long MeetingWhy This Is a Business Story, Not a Tooling StoryHow Does This Connect Back?How the Two Views Work TogetherQuick Orientation for LeadersShifting Left, As a Habit, Not a SloganWhere Each Level Lives, and WhyA Concrete Before and AfterRisk-Driven Depth, and When to Add an RCPeople and Ownership, Fewer HandoffsSignals Leaders Should WatchThe Business Impact, Not a Tooling StoryBridging the Gap: Flow That Leaders Can GovernKey Takeaways
9. Fostering Product Thinking and Marketing Savvy
Why Do the Majority of Tech Leaders in Non-Digital-Native Enterprises Fail to Connect Their Systems to Revenue?The Venn Diagram of UX, Tech, Business, and CustomersThe Discovery: Diagnosing the Silo SicknessIntroducing the Venn Diagram: The Common Language of ValueThe Core: The “Sweet Spot” (UX + Tech + Business + Customers)Shifting Mindsets: From “Or” to “And”Making It ConcreteOperationalizing the Framework: From Theory to Daily PracticeEmbedding in Roadmapping and PrioritizationRitualizing the Four-Lens DialogueEvolving Artifacts and DocumentationShifting Accountability: Shared Ownership of the CenterPerformance Metrics and Incentives Began to Reflect This Cross-Functional Accountability and Start to Be MeasuredMeasuring the Impact: From Alignment to ResultsThe Critical Role of LeadershipPitfalls to AvoidKey Takeaways for Senior LeadershipThe Foundation for Sustainable AdvantageMaking Prioritization Stick—Ownership, Cadence, and AdaptationOperationalizing the Roadmap: The Three PillarsMeasuring Success: Beyond Shipping FeaturesConnecting to the Bigger Picture: Value Prop and GTMWrapping UpProduct Marketing Basics (Value Proposition and Go-to-Market)From Overlap to Market ImpactSetting the Stage: Why Product Marketing Matters NowPart 1: Crafting the Irresistible Hook—The Value PropositionBuilding the Value Proposition CanvasFrom Discussion to Construction Using a Simple but Powerful Tool: Value PropositionRefining the PropositionBeyond the Statement: Value Messaging PillarsTesting and ValidationDon’t Assume—Validate the VP RuthlesslyLeadership Takeaway (Value Proposition)Turning Promise into Profit—The Go-to-Market StrategyDefining Go-to-Market (GTM): Beyond the Launch PartyThe Five Pillars of an Effective GTM StrategyOperationalizing GTM: The Pilot and MetricsLeadership Takeaway (Go-to-Market)Let Me Summarize the Strategic FlowConclusion: The Product Marketing Imperative
10. Collaboration and Risk Management
Change Did Not Hurt Us; Surprise DidWhat This Section DeliversWhy This Matters NowThe Plain DefinitionsHow We Made Surprise OptionalThe Core MethodWhy It WorksHow Does It Run in Your Existing CadenceThe Tech Trends Board: Your RadarWhat It IsWhat Belongs on ItColumns That Keep It ActionableWhy It Works for the BusinessHow the Two Boards Work TogetherOperating Rules That Keep Both Boards HonestAnti-patterns to Avoid, and Fast FixesRoles That Make This WorkLeadership Moves That Create HabitsPractical Walk-Through: From Trend to DecisionAt-a-Glance Scope ChecksA Weekly and Biweekly Rhythm That SticksMeasures That Prove a Unified Direction Is WorkingTwo Short Narratives You Can Reuse with Your TeamsNarrative A: Protect the Tuesday 30Narrative B: Life Cycle Without DramaCommon QuestionsExecutive Recap: What, Why, So What, NextThe Readiness Strategy, ExpandedWhat It Covers, with Clear SourcesWhy It WorksHands-On Time: The Readiness BoardDesign and DisciplineMinimum ColumnsCadence That Keeps It RealThe Tech Trends Board: Radar That Keeps Us HonestWhat Belongs on It and Where It Comes FromWorking Together: Radar to Action to ResultExecutive Lens: What, Why, So What, NextFour Common Scenarios, Handled the Same WayRole Clarity, with RACI As the Tie-BreakerKeep the Beats, Keep the BenefitsTable: Readiness Maturity LadderAdoption Playbook, 90 DaysDays 1 to 10: Stand Up and SeedDays 11 to 30: Make It the AgendaDays 31 to 60: Tighten Ownership and FlowDays 61 to 90: Measure and ImproveAnti-patterns and Fast FixesLeader FAQsMeasures That Prove a Unified Direction Is WorkingReadiness ItemTech Trends ItemMake Meetings Work for You, Not Against YouWhat to Do When Things Go Off ScriptHow Does This Support Product Thinking and Marketing SavvyInitiative Definition, Execution, Release, and FeedbackTwo Tuesdays, Two OutcomesInitiative Definition—the Collaboration HandshakeThe 30-minute Definition FlowExecution—Working Together Without FrictionInside the Squad, Five HabitsAcross Squads, Three Light TouchesHandling Late Change Without ChaosRelease—Trust Is a Team SportKeep the Gates Light and RealMake the Message SimpleFeedback—Change the Plan in PublicCollaboration Contract, at a GlanceLeader Moves That Make This RealExecutive RecapA Sharper Collaboration Toolkit, Built for ExecutivesDefinition, Done in 30 Minutes, Shared on One PageDefinition Handshake, Fillable One-PagerPatterns for Three Initiative TypesA. Compliance or Policy ResponseB. User-Facing ImprovementC. Shared Platform ChangeLeader Coaching Scripts for Challenging Moments
11. Budgeting and Operational Forecasting
Cost Forecasting and Resource Efficiency (Cost per Feature)Why: A Budget Is a Strategy Written in NumbersSo What: What Changes TodayHow to Implement in Six Weeks, Then MatureWeek 1: Choose the UnitsWeek 2: Map the CostsWeek 3: Measure the DriversWeek 4: Compute the First Cost per FeatureWeek 5: Forecast Next QuarterWeek 6: Decide and ActWe Need Plain DefinitionsSo What: What Changes TodaySix Weeks to First Numbers, Then MatureWeek 1: Choose the UnitsWeek 2: Map CostsWeek 3: Select DriversWeek 4: Compute First CostsWeek 5: Forecast Next QuarterWeek 6: Decide and ActWhat the Table Tells UsForecasting: From Unit Costs to the Following Quarter NumbersCost per Feature in Crisis and GrowthIn a CrisisIn GrowthWho Does What and WhenCadence that worksCommon Traps and How to Avoid ThemMake Quality, Reliability, and Security Part of the Feature CostTie the Cost per Feature to OKRs and RoadmapsA Short Playbook for CommitmentsPlatform and Infrastructure CostsWhy: Shared Costs distort Unit Economics Unless You Show the RuleSo What: Create a One-Page “Platform Rate Card” and a Two-Column LedgerScenario Worksheet for Cost ControlLimits and Alerts That Protect the PlanHow to Explain This to the Board in Five MinutesExecutive Q and ARole Clarity and IncentivesCulture Signals That Make It StickWhen to Step in As a Senior LeaderBuild Once, Reuse Many TimesA Short Training Plan for ManagersOnce More, in Plain TermsTagging Rules (Again), Four Lines, No ExceptionsPrioritizing Technical Debt vs. InnovationWhat: Clear Definitions and a Shared RuleWhy: The Board Cares About Time, Risk, and MoneySo What: What Changes TodayNext: A Simple Scoring Method You Can Run in One MeetingPut Real Examples on the TableDebt CandidatesInnovation CandidatesSet a Quarterly Ratio, Then Allow for a Controlled SwingUse Cost per Feature As the Anchor MetricDecide with a One-Page Business CaseDebt That Always Jumps to the TopInnovation That You Should Not StarveCadence: a Weekly Triage and a Monthly Portfolio CouncilTie Incentives to the BalanceAvoid Traps That Waste Time and MoneyHow the Two Stories Guide the BalanceA Compact Dashboard for ExecutivesA One-Page Template You Can CopyQuick Math You Can Do in the RoomPortfolio Guardrails That Keep You SafeClose with a Short Checklist
12. The Unfinished Highway: Why Scaling DevOps Isn’t About Fixing Potholes (But Building Highways)
Growing Teams and Communities (Squads, Tribes, Guilds)The StructureInternal Development Platform As the Backbone for ReuseExecutive View of ReuseOnboarding That Scales Culture and SpeedA Simple 30-45-60 PlanMake Onboarding RealAutonomy with Guardrails, Definitions, and CadenceCommunities That Compound Knowledge, Not MeetingsFlow and Cost Awareness, Unit Economics at the Team LevelAnti-patterns and Recovery MovesReal-Life ExampleExecutive Playbook: What, Why, So What, NextThe Six Operating MovesContinuous Improvement and Long-Term StrategySpeed: The Currency of Competitive MarketsWhy Executives CareRevenue and Cost: The Bottom LineContinuous Improvement and Long-Term Strategy: Building the Next Generation HighwayOKRs: Your Strategic BlueprintEmerging Tech: The Future-Proofing DilemmaTechnology Roadmaps: The Manager’s Navigation SystemListening to Builders: Engineers As Your CompassConclusion: The Journey from Potholes to Highways
Index

Content preview from Bridging the Gap: Turning Agile and DevOps Initiatives into Board-Level Wins

About the Author

Leo Bardelli

A person wearing a white shirt is holding a pair of glasses in front of a bookshelf filled with various books. The individual is looking directly at the camera with a neutral expression. The background features a variety of book spines, suggesting a setting related to study or work.

is a seasoned technology leader with more than two decades of experience across Agile and DevOps transformations, cloud engineering, enterprise architecture, and large-scale product strategy. As Head of Product Engineering at Saint-Gobain, a global enterprise with 190,000 employees, he aligns strategic vision with hands-on delivery to push performance boundaries. Bardelli has led end-to-end architecture designs, a greenfield company ramp-up in China, massive cloud migrations, automated infrastructure deployments, and strategic M&A integrations. He is known for unifying dispersed stakeholders around measurable outcomes ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9798868820717Purchase Link Publisher Website

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Bridging the Gap: Turning Agile and DevOps Initiatives into Board-Level Wins

by Leo Bardelli

About the Author

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.