[{"data":1,"prerenderedAt":520},["ShallowReactive",2],{"/en-us/the-source/platform/finops-balancing-financial-responsibility-and-innovation":3,"footer-en-us":50,"the-source-banner-en-us":384,"the-source-navigation-en-us":390,"article-site-categories-en-us":413,"the-source-newsletter-en-us":415,"finops-balancing-financial-responsibility-and-innovation-article-hero-category-en-us":422,"finops-balancing-financial-responsibility-and-innovation-the-source-source-cta-en-us":448,"finops-balancing-financial-responsibility-and-innovation-article-hero-author-en-us":457,"finops-balancing-financial-responsibility-and-innovation-category-en-us":480,"finops-balancing-financial-responsibility-and-innovation-the-source-resources-en-us":493},{"id":4,"title":5,"body":6,"category":7,"config":8,"content":14,"description":6,"extension":41,"meta":42,"navigation":43,"path":44,"seo":45,"slug":46,"stem":47,"type":48,"__hash__":49},"theSource/en-us/the-source/platform/finops-balancing-financial-responsibility-and-innovation.yml","Finops Balancing Financial Responsibility And Innovation",null,"platform",{"layout":9,"template":10,"author":11,"featured":12,"sourceCTA":13},"the-source","TheSourceArticle","lee-faus",false,"transform-your-software-development",{"title":15,"date":16,"description":17,"timeToRead":18,"heroImage":19,"keyTakeaways":20,"articleBody":24,"faq":25},"FinOps: Balancing financial responsibility and innovation","2024-11-26","Explore how FinOps harmonizes financial accountability with business objectives, promoting cost-effective innovation in modern enterprises.","5 min read","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463866/i27a3wecdhplvd9wbxqr.png",[21,22,23],"FinOps fosters collaboration between finance, engineering, and business teams, aligning cloud investments with strategic business goals for maximum value.","By enhancing financial transparency, FinOps empowers organizations to make swift, data-driven decisions that reduce cloud costs.","Implementing FinOps creates a balance between innovation and cloud cost management, easing tension between product development and operations teams.","When cloud spending grows alongside your engineering teams, a painful trade-off often emerges: push developers to ship faster, or rein in escalating costs. But imagine boosting developer productivity by 30% while slashing project costs by 25%. That might sound impossible, yet it’s a realistic goal for organizations that adopt FinOps (Financial Operations) - a data-driven approach that applies DevOps principles and practices to optimize the costs associated with people, process, and technology across the software development lifecycle.\n\nI’ve seen firsthand how FinOps transforms organizations by bringing financial clarity to every aspect of software development. I recently met with the DevOps team at an insurance company that is beginning its FinOps journey. Early discussions included determining basic measurements such as cloud spend and identifying other revenue-driving, cost-reducing metrics through value stream management. These conversations are critical for FinOps practitioners to evaluate how teams and resources are organized and allocated, and which processes and tools may be implemented to drive change.\n\nFrom team structures to development processes to technology choices, this visibility helps leaders optimize investments across their entire operation. By bringing together finance, product, and engineering teams, FinOps enables CFOs, CPOs, and CTOs to make informed decisions - improving efficiency across the business.\n\nImproving efficiency and optimizing costs isn’t just a technical challenge - it’s also a strategic business imperative, especially as organizations invest more money in the cloud. FinOps brings necessary financial accountability to the cloud’s variable spend model. Let’s walk through the benefits of FinOps frameworks and how you can begin incorporating FinOps methodologies into your operational workflows.\n\n## What is FinOps?\nFinOps, short for Financial Operations, succeeds by transforming how finance, engineering, technology, and business teams operate. Through real-time data and analytics, teams gain immediate visibility into how they are using resources (such as cloud resources) and can take action before costs escalate. This proactive approach to financial accountability enables quick informed decisions about resource allocation, leading to measurable cost savings.\n\nAt its core, FinOps is a cultural practice that makes this transformation sustainable. By establishing clear processes and shared metrics, teams ensure their daily technology decisions support broader business objectives.\n\n## Why is FinOps so popular right now?\nAs many companies focus on generative AI and developer productivity, they need guardrails, such as automated workflows and reusable templates, on the delivery side of the equation to ensure [paved pathways](https://about.gitlab.com/the-source/platform/driving-business-results-with-platform-engineering/) are adopted. This becomes essential for organizations that are modernizing their applications and scaling cloud architectures in production.\n\nThe challenge intensifies when managing non-production costs, such as continuous integration (CI) costs. Companies that have adopted a data-driven approach can gain deep visibility into their CI costs. They can see the financial implications of scaling CI horizontally or vertically across different processor architectures. By implementing standards like ephemeral testing environments, they ensure code quality and security while optimizing spending.\n\nProduct owners, who normally own the budget for a product line, can also work with IT teams and engineering leads to provide transparency metrics. This collaboration allows leaders to roll up budget projections across multiple services and ensure that infrastructure resources are being leveraged at their optimal capacity. The result: finance teams can finally see which applications generate the most investment return.\n\n## Bridging technical and financial domains\nCreating a FinOps model can involve both a carrot and stick approach. The carrot approach fosters a more collaborative and transparent environment. The stick approach, on the other hand - for example, reprimanding development teams for overspending - most often leads to a breakdown in processes. You want FinOps to account for what developers need to do their work and how it impacts the company’s bottom line, not just monitor their use of cloud resources.\n\nI recently met with a major airline that was spending close to $5 million a year on CI runner fleets. Security scans, dependency scans, and token scanning all ran inside these runner fleets. They could have skipped the security step to reduce their spend, but the [potential for security issues](https://about.gitlab.com/the-source/security/how-to-strengthen-security-by-applying-devsecops-principles/) was a much bigger concern than spending the money on the runner fleets. Instead of skipping the security step, the company needed to identify ways to make their runner fleets as a whole more efficient to reduce their spend _and_ encourage developers to experiment and innovate.\n\nA successful FinOps program does not require a centralized team of full-time FinOps professionals. FinOps serves as a strategic liaison among cross-functional teams such as finance, product, and engineering. A typical FinOps program includes various job roles and functions, such as a CTO or VP of Engineering, a finance leader, and one or more engineering leaders who regularly collaborate to evaluate issues, identify new efficiency opportunities, and build remediation plans.\n\nAligning technical operations with financial objectives helps ensure that cloud infrastructure and software development investments yield the highest possible return. This can demonstrate to DevSecOps teams how their work contributes directly to increasing revenue, how they may be able to reduce costs, or both.\n\n## Smart financial control in developer workflows\nFinOps monitors resource consumption from both a user and operational standpoint to help optimize developer workflows. One way to accomplish this is to analyze CI jobs and identify which ones cost more than their value justifies. Every software development pipeline contains multiple jobs, each requiring an execution resource like a virtual machine (VM) or container. The longer each job takes to execute, the higher the cost. FinOps helps developers understand which jobs are performing poorly so they know which ones they need to refactor.\n\nThis creates a self-service model that frees technology teams to work within clear guidelines. For example, a policy might prohibit someone from provisioning $100,000 worth of resources on AWS, but they can spin up an EC2 image to conduct testing. However, if they can justify why they need to provision $100,000 worth of resources, they can submit a request explaining how the project will potentially generate revenue for the company. If approved, they can begin their work.\n\nHowever, I want to reassure DevSecOps professionals that FinOps isn't about restricting innovation through monitoring. Instead, it provides full visibility into your organization’s cloud usage and spending, helping teams identify opportunities to improve cloud productivity. In addition to fostering collaboration among finance, technology, and business teams, FinOps analyzes usage patterns and forecasts demand to anticipate whether resources need to be scaled up or down to meet future needs before overspending occurs.\n\n## Easing the tension\nThere’s a constant tug-of-war between engineering and operations teams. Engineering’s mission is to drive innovation that generates new revenue streams while creating great customer experiences. The operations team focuses on maximizing productivity while saving money. FinOps eases the tension between these groups by increasing developer productivity while reducing wasteful spending - aligning technical efficiency with financial prudence.\n\nFinOps helps business leaders think in precise numbers, not subjective costs. It’s imperative to approach software development with a clear understanding of its financial impact on the organization to make informed decisions on project continuance based on two key criteria: will the project increase revenue or reduce costs?\n\nAt its core, FinOps isn’t just about cutting cloud costs; it’s also about optimizing the entire software development lifecycle and making continuous improvements. The goal is to help engineers and operations consider financial effectiveness alongside technical innovation so they understand how their work maps to boosting the organization’s bottom line.\n\n_Read more about FinOps on the [FinOps Foundation website](https://www.finops.org/introduction/what-is-finops/)._",[26,29,32,35,38],{"header":27,"content":28},"What are the key benefits of adopting FinOps?","Adopting FinOps leads to cost savings, improved resource allocation, and better cross-team collaboration. Organizations gain financial transparency, allowing them to scale cloud services efficiently, reduce waste, and ensure that every technology investment supports business growth and profitability.",{"header":30,"content":31},"How does FinOps align financial objectives with DevSecOps?","FinOps helps DevSecOps teams balance security and efficiency by ensuring that cost-saving measures do not compromise essential security processes. Instead of cutting security scans to save money, organizations use FinOps to optimize infrastructure, making security operations more cost-effective while maintaining compliance.",{"header":33,"content":34},"Why is FinOps important?","FinOps, short for Financial Operations, is a framework that helps organizations balance financial accountability with innovation by optimizing cloud spending and software development costs. It enables teams to make data-driven financial decisions while maintaining agility, improving collaboration between finance, engineering, and product teams.",{"header":36,"content":37},"What role do engineering teams play in a FinOps strategy?","Engineering teams are crucial in FinOps, as they make decisions that directly impact cloud costs. FinOps encourages developers to take ownership of cost efficiency by monitoring resource consumption, refactoring inefficient CI jobs, and leveraging automation to optimize deployments. The goal is to foster a culture where financial awareness becomes a natural part of development.",{"header":39,"content":40},"How does FinOps improve cloud cost management?","FinOps provides real-time visibility into cloud spending, allowing organizations to track resource utilization and prevent unnecessary costs. By integrating financial insights into DevOps workflows, companies can identify inefficiencies, optimize continuous integration (CI) costs, and ensure that infrastructure investments deliver maximum value.","yml",{},true,"/en-us/the-source/platform/finops-balancing-financial-responsibility-and-innovation",{"title":15,"description":17,"ogImage":19},"finops-balancing-financial-responsibility-and-innovation","en-us/the-source/platform/finops-balancing-financial-responsibility-and-innovation","article","4k2vmEN-3VawKsLdbq7hwFDMukpIQ2JDK9nAvZcnAjI",{"data":51},{"text":52,"source":53,"edit":59,"contribute":64,"config":69,"items":74,"minimal":373},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":54,"config":55},"View page source",{"href":56,"dataGaName":57,"dataGaLocation":58},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":60,"config":61},"Edit this page",{"href":62,"dataGaName":63,"dataGaLocation":58},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":65,"config":66},"Please contribute",{"href":67,"dataGaName":68,"dataGaLocation":58},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":70,"facebook":71,"youtube":72,"linkedin":73},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[75,132,189,248,311],{"title":76,"links":77,"subMenu":93},"Pricing",[78,83,88],{"text":79,"config":80},"View plans",{"href":81,"dataGaName":82,"dataGaLocation":58},"/pricing/","view plans",{"text":84,"config":85},"Why Premium?",{"href":86,"dataGaName":87,"dataGaLocation":58},"/pricing/premium/","why premium",{"text":89,"config":90},"Why Ultimate?",{"href":91,"dataGaName":92,"dataGaLocation":58},"/pricing/ultimate/","why ultimate",[94],{"title":95,"links":96},"Contact Us",[97,102,107,112,117,122,127],{"text":98,"config":99},"Contact sales",{"href":100,"dataGaName":101,"dataGaLocation":58},"/sales/","sales",{"text":103,"config":104},"Support portal",{"href":105,"dataGaName":106,"dataGaLocation":58},"https://support.gitlab.com","support portal",{"text":108,"config":109},"Customer portal",{"href":110,"dataGaName":111,"dataGaLocation":58},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"text":113,"config":114},"Status",{"href":115,"dataGaName":116,"dataGaLocation":58},"https://status.gitlab.com/","status",{"text":118,"config":119},"Terms of use",{"href":120,"dataGaName":121,"dataGaLocation":58},"/terms/","terms of use",{"text":123,"config":124},"Privacy statement",{"href":125,"dataGaName":126,"dataGaLocation":58},"/privacy/","privacy statement",{"text":128,"config":129},"Cookie preferences",{"dataGaName":130,"dataGaLocation":58,"id":131,"isOneTrustButton":43},"cookie preferences","ot-sdk-btn",{"title":133,"links":134,"subMenu":145},"Product",[135,140],{"text":136,"config":137},"DevSecOps platform",{"href":138,"dataGaName":139,"dataGaLocation":58},"/platform/","devsecops platform",{"text":141,"config":142},"AI-Assisted Development",{"href":143,"dataGaName":144,"dataGaLocation":58},"/gitlab-duo/","ai-assisted development",[146],{"title":147,"links":148},"Topics",[149,154,159,164,169,174,179,184],{"text":150,"config":151},"CICD",{"href":152,"dataGaName":153,"dataGaLocation":58},"/topics/ci-cd/","cicd",{"text":155,"config":156},"GitOps",{"href":157,"dataGaName":158,"dataGaLocation":58},"/topics/gitops/","gitops",{"text":160,"config":161},"DevOps",{"href":162,"dataGaName":163,"dataGaLocation":58},"/topics/devops/","devops",{"text":165,"config":166},"Version Control",{"href":167,"dataGaName":168,"dataGaLocation":58},"/topics/version-control/","version control",{"text":170,"config":171},"DevSecOps",{"href":172,"dataGaName":173,"dataGaLocation":58},"/topics/devsecops/","devsecops",{"text":175,"config":176},"Cloud Native",{"href":177,"dataGaName":178,"dataGaLocation":58},"/topics/cloud-native/","cloud native",{"text":180,"config":181},"AI for Coding",{"href":182,"dataGaName":183,"dataGaLocation":58},"/topics/devops/ai-for-coding/","ai for coding",{"text":185,"config":186},"Agentic AI",{"href":187,"dataGaName":188,"dataGaLocation":58},"/topics/agentic-ai/","agentic ai",{"title":190,"links":191},"Solutions",[192,196,201,206,211,215,220,223,228,233,238,243],{"text":193,"config":194},"Application Security Testing",{"href":195,"dataGaName":193,"dataGaLocation":58},"/solutions/application-security-testing/",{"text":197,"config":198},"Automated software delivery",{"href":199,"dataGaName":200,"dataGaLocation":58},"/solutions/delivery-automation/","automated software delivery",{"text":202,"config":203},"Agile development",{"href":204,"dataGaName":205,"dataGaLocation":58},"/solutions/agile-delivery/","agile delivery",{"text":207,"config":208},"SCM",{"href":209,"dataGaName":210,"dataGaLocation":58},"/solutions/source-code-management/","source code management",{"text":150,"config":212},{"href":213,"dataGaName":214,"dataGaLocation":58},"/solutions/continuous-integration/","continuous integration & delivery",{"text":216,"config":217},"Value stream management",{"href":218,"dataGaName":219,"dataGaLocation":58},"/solutions/value-stream-management/","value stream management",{"text":155,"config":221},{"href":222,"dataGaName":158,"dataGaLocation":58},"/solutions/gitops/",{"text":224,"config":225},"Enterprise",{"href":226,"dataGaName":227,"dataGaLocation":58},"/enterprise/","enterprise",{"text":229,"config":230},"Small business",{"href":231,"dataGaName":232,"dataGaLocation":58},"/small-business/","small business",{"text":234,"config":235},"Public sector",{"href":236,"dataGaName":237,"dataGaLocation":58},"/solutions/public-sector/","public sector",{"text":239,"config":240},"Education",{"href":241,"dataGaName":242,"dataGaLocation":58},"/solutions/education/","education",{"text":244,"config":245},"Financial services",{"href":246,"dataGaName":247,"dataGaLocation":58},"/solutions/finance/","financial services",{"title":249,"links":250},"Resources",[251,256,261,266,271,276,281,286,291,296,301,306],{"text":252,"config":253},"Install",{"href":254,"dataGaName":255,"dataGaLocation":58},"/install/","install",{"text":257,"config":258},"Quick start guides",{"href":259,"dataGaName":260,"dataGaLocation":58},"/get-started/","quick setup checklists",{"text":262,"config":263},"Learn",{"href":264,"dataGaName":265,"dataGaLocation":58},"https://university.gitlab.com/","learn",{"text":267,"config":268},"Product documentation",{"href":269,"dataGaName":270,"dataGaLocation":58},"https://docs.gitlab.com/","docs",{"text":272,"config":273},"Blog",{"href":274,"dataGaName":275,"dataGaLocation":58},"/blog/","blog",{"text":277,"config":278},"Customer success stories",{"href":279,"dataGaName":280,"dataGaLocation":58},"/customers/","customer success stories",{"text":282,"config":283},"Remote",{"href":284,"dataGaName":285,"dataGaLocation":58},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"text":287,"config":288},"GitLab Services",{"href":289,"dataGaName":290,"dataGaLocation":58},"/services/","services",{"text":292,"config":293},"Community",{"href":294,"dataGaName":295,"dataGaLocation":58},"/community/","community",{"text":297,"config":298},"Forum",{"href":299,"dataGaName":300,"dataGaLocation":58},"https://forum.gitlab.com/","forum",{"text":302,"config":303},"Events",{"href":304,"dataGaName":305,"dataGaLocation":58},"/events/","events",{"text":307,"config":308},"Partners",{"href":309,"dataGaName":310,"dataGaLocation":58},"/partners/","partners",{"title":312,"links":313},"Company",[314,319,324,329,334,339,344,348,353,358,363,368],{"text":315,"config":316},"About",{"href":317,"dataGaName":318,"dataGaLocation":58},"/company/","company",{"text":320,"config":321},"Jobs",{"href":322,"dataGaName":323,"dataGaLocation":58},"/jobs/","jobs",{"text":325,"config":326},"Leadership",{"href":327,"dataGaName":328,"dataGaLocation":58},"/company/team/e-group/","leadership",{"text":330,"config":331},"Team",{"href":332,"dataGaName":333,"dataGaLocation":58},"/company/team/","team",{"text":335,"config":336},"Handbook",{"href":337,"dataGaName":338,"dataGaLocation":58},"https://handbook.gitlab.com/","handbook",{"text":340,"config":341},"Investor relations",{"href":342,"dataGaName":343,"dataGaLocation":58},"https://ir.gitlab.com/","investor relations",{"text":345,"config":346},"Sustainability",{"href":347,"dataGaName":345,"dataGaLocation":58},"/sustainability/",{"text":349,"config":350},"Diversity, inclusion and belonging (DIB)",{"href":351,"dataGaName":352,"dataGaLocation":58},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":354,"config":355},"Trust Center",{"href":356,"dataGaName":357,"dataGaLocation":58},"/security/","trust center",{"text":359,"config":360},"Newsletter",{"href":361,"dataGaName":362,"dataGaLocation":58},"/company/contact/#contact-forms","newsletter",{"text":364,"config":365},"Press",{"href":366,"dataGaName":367,"dataGaLocation":58},"/press/","press",{"text":369,"config":370},"Modern Slavery Transparency Statement",{"href":371,"dataGaName":372,"dataGaLocation":58},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":374},[375,378,381],{"text":376,"config":377},"Terms",{"href":120,"dataGaName":121,"dataGaLocation":58},{"text":379,"config":380},"Cookies",{"dataGaName":130,"dataGaLocation":58,"id":131,"isOneTrustButton":43},{"text":382,"config":383},"Privacy",{"href":125,"dataGaName":126,"dataGaLocation":58},{"visibility":43,"title":385,"button":386},"The Intelligent Software Development Era: How AI is reshaping DevSecOps teams",{"config":387,"text":389},{"href":388},"/developer-survey/","Get the research report",{"logo":391,"subscribeLink":396,"navItems":400},{"altText":392,"config":393},"the source logo",{"src":394,"href":395},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750191004/t7wz1klfb2kxkezksv9t.svg","/the-source/",{"text":397,"config":398},"Subscribe",{"href":399},"#subscribe",[401,405,409],{"text":402,"config":403},"Artificial Intelligence",{"href":404},"/the-source/ai/",{"text":406,"config":407},"Security & Compliance",{"href":408},"/the-source/security/",{"text":410,"config":411},"Platform & Infrastructure",{"href":412},"/the-source/platform/",{"categoryNames":414},{"ai":402,"platform":410,"security":406},{"title":416,"description":417,"submitMessage":418,"formData":419},"The Source Newsletter","Stay updated with insights for the future of software development.","You have successfully signed up for The Source’s newsletter.",{"config":420},{"formId":421,"formName":362,"hideRequiredLabel":43},1077,{"id":423,"title":424,"body":6,"category":6,"config":425,"content":426,"description":6,"extension":41,"meta":442,"navigation":43,"path":443,"seo":444,"slug":7,"stem":445,"testContent":6,"type":446,"__hash__":447},"pages/en-us/the-source/platform/index.yml","",{"layout":9},[427,434],{"componentName":428,"type":428,"componentContent":429},"TheSourceCategoryHero",{"title":410,"description":430,"image":431},"Learn how to build a DevSecOps framework that sets your team up for success, from planning to delivery.",{"config":432},{"src":433},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463263/bdz7hmhpbmgwvoybcaud.png",{"componentName":435,"type":435,"componentContent":436},"TheSourceCategoryMainSection",{"config":437},{"sourceCTAs":438},[439,440,441],"source-lp-the-ultimate-playbook-for-high-performing-devsecops-teams","source-lp-measuring-success-in-software-development-a-guide-for-leaders","source-lp-building-a-resilient-software-development-practice",{},"/en-us/the-source/platform",{"title":410,"description":430,"ogImage":433},"en-us/the-source/platform/index","category","u9v0Yrf14Lhx-hAKL_t8ViZ-OxgRjEc5QiV6CvI6bJc",{"config":449,"title":450,"description":451,"link":452},{"slug":13},"Transform your software development","Read the 2024 commissioned Forrester Consulting Total Economic Impact™ study for a complete picture of how GitLab Ultimate minimized costs, maximized performance, and supported organizations’ growth objectives.",{"text":453,"config":454},"Download the full study now",{"href":455,"dataGaName":450,"dataGaLocation":456},"/resources/study-forrester-tei-gitlab-ultimate/","thesource",{"id":458,"title":459,"body":6,"category":6,"config":460,"content":461,"description":6,"extension":41,"meta":474,"navigation":43,"path":475,"seo":476,"slug":11,"stem":477,"testContent":6,"type":478,"__hash__":479},"theSourceAuthors/en-us/the-source/authors/lee-faus.yml","Lee Faus",{"layout":9},[462,472],{"componentName":463,"type":463,"componentContent":464},"TheSourceAuthorHero",{"config":465,"name":459,"role":467,"bio":468,"headshot":469},{"gitlabHandle":466},"lfaus","Global Field CTO","Lee Faus is a Global Field CTO at GitLab. Lee has been a software architect, teacher, professor, and educator for over 25 years. He leverages his experience as an educator to bring complex technology concepts into a business forum where executives gain valuable advice to positively impact their business.",{"altText":459,"config":470},{"src":471},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463398/vivhlomglvnstamj54bo.jpg",{"componentName":473,"type":473},"TheSourceArticlesList",{},"/en-us/the-source/authors/lee-faus",{"title":459},"en-us/the-source/authors/lee-faus","author","7pwNlTMVB3GVMZ6nm1tNkS4ayGeq7YqqRUwwncC7JoU",{"id":423,"title":424,"body":6,"category":6,"config":481,"content":482,"description":6,"extension":41,"meta":491,"navigation":43,"path":443,"seo":492,"slug":7,"stem":445,"testContent":6,"type":446,"__hash__":447},{"layout":9},[483,487],{"componentName":428,"type":428,"componentContent":484},{"title":410,"description":430,"image":485},{"config":486},{"src":433},{"componentName":435,"type":435,"componentContent":488},{"config":489},{"sourceCTAs":490},[439,440,441],{},{"title":410,"description":430,"ogImage":433},[494,503,512],{"config":495,"title":496,"description":497,"link":498},{"slug":441},"Building a resilient software development practice","Learn strategies to bolster your team's effectiveness amid shifts in the industry with a standardized approach to software development.",{"text":499,"config":500},"Read the guide",{"href":501,"dataGaName":502,"dataGaLocation":456},"/the-source/platform/building-a-resilient-software-development-practice/","Building a Resilient Software Development Practice",{"config":504,"title":505,"description":506,"link":507},{"slug":440},"Measuring success in software development: A guide for leaders","Discover how to measure software delivery performance with key metrics that optimize workflows, enhance team productivity, and drive better decisions.",{"text":508,"config":509},"Download the guide",{"href":510,"dataGaName":511,"dataGaLocation":456},"/the-source/platform/measuring-success-in-software-development-a-guide-for-leaders/","Measuring success in software development",{"config":513,"title":514,"description":515,"link":516},{"slug":439},"The ultimate playbook for high-performing DevSecOps teams ","Learn how to tackle issues like deployment slowdowns, lack of collaboration, and developer burnout.",{"text":517,"config":518},"Read the ebook",{"href":519,"dataGaName":514,"dataGaLocation":456},"/the-source/platform/the-ultimate-playbook-for-high-performing-devsecops-teams/",1772652101084]