Software Delivery Notebook

Tag: Methods

  • Mapping your deployment pipeline: A guide to Continuous Delivery

    Mapping Your Deployment Pipeline: A Guide to Continuous Delivery
    The Software Delivery Notebook
    Mapping your deployment pipeline: A guide to Continuous Delivery
    Loading
    /

    This white paper from Octopus Deploy provides a comprehensive guide to mapping and improving deployment pipelines for achieving Continuous Delivery. It explains Continuous Delivery’s core principles and benefits, emphasizing its role in increasing deployment frequency and reducing risk.

    Establish a basic deployment pipeline with stages like commit, build, acceptance, and production while highlighting the importance of automation and monitoring. Discover the cultural factors influencing DevOps’ success and find strategies for identifying and overcoming constraints to optimize the software delivery process.

    Research has shown that these external approvals actually slow down deployments, increase lead times, and don’t even improve quality or reduce failure rates. In fact, they often have the opposite effect.

  • AI code quality trends

    AI code quality trends
    The Software Delivery Notebook
    AI code quality trends
    Loading
    /

    Digging into the 2025 AI Copilot Code Quality report from GitClear and Alloy, which looked at 211,000,000 lines of code and made projections for 2025.

    Find out how AI is increasing the speed of change, and the knock on effects of optimizing for short-term speed. Or, more poetically: “Oh, what a tangled web we weave when AI agents we use for speed.”

    Good developers focus on building systems that are not just functional, but also elegant and efficient. They refactor their code, meaning they constantly look for ways to improve the structure and make it more reusable.

  • Lincoln Labs: Decades ahead of its time

    Lincoln Labs: Ahead of its time
    The Software Delivery Notebook
    Lincoln Labs: Decades ahead of its time
    Loading
    /

    It’s time for a history lesson! We start by looking at early software delivery models by looking at MIT’s Lincoln Labs and the SAGE project.

    The process used for SAGE was documented by Herbert Benington in 1956. How did they tackle building the first large computer programming when none of the tools we use existed?

    Find out why Lincoln Labs were telling us how to start with a small working system before evolving it to meet more needs decades before the Agile revolution.

    Get ready for a blast from the past, as today we’re going deep on the SAGE air defence system […] It’s like they were laying the foundation for Agile development, but like, decades before it was even a thing.

  • Developer productivity at Google

    Google Developer Productivity: Code Quality and Beyond
    The Software Delivery Notebook
    Developer productivity at Google
    Loading
    /

    A peek inside Google’s research on developer productivity, which looks at causal relationships to find what helps developers get stuff done (and what gets in the way).

    Looks at factors like shifting priorities, documentation, time spent in meetings, distributed and remote working, and technical debt.

    “Maybe it’s not just the presence or absence of documentation that matters, but the quality and purpose of that documentation.”

  • Measuring software delivery

    Measuring software delivery
    The Software Delivery Notebook
    Measuring software delivery
    Loading
    /

    Tackles the subject of measuring software delivery in organizations based on the white paper Measuring Continuous Delivery and DevOps. Relevant to teams using Agile, Lean, Continuous Delivery, and DevOps.

    Delves into leading and lagging indicators, qualitative and quantitative metrics and more. Takles some common dead ends and things to keep in mind when choosing metrics.

    “Data! We love it. In software it’s the key to making smart moves. Sometimes it feels like we’re measuring everything except the stuff that makes a difference.”

  • Why use Continuous Delivery?

    Continuous Delivery
    The Software Delivery Notebook
    Why use Continuous Delivery?
    Loading
    /

    We dive into the white paper, The Importance of Continuous Delivery by Steve Fenton, published by Octopus.

    Find out why Continuous Delivery (CD) is the best way to deliver software that we know of right now.

    “Implementing Continuous Delivery isn’t just a flip of a switch, it’s a journey. The key is to start small, focus on those quick wins, and build momentum from there.”