Better ROI from Software Development

Better ROI from Software Development

By Red Folder Consultancy LtdTechnology
Download on the App Store

Better ROI from Software Development episodes

  • #135: Infrastructure-as-Code

    In this episode I introduce Infrastructure-as-Code - a way of defining your Operation's infrastructure as code - an example of DevOps in practice with our Ops teams learning from our Dev teams.

    Why you may be interested in this episode:

    • For an explanation of Infrastructure-as-Code
    • The advantages of using it
    • And some of the common excuses for not using it - and how to address them

      • -----

      Find this episodes show notes at: https://red-folder.com/podcasts/135

      Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

      12 min
    • #134: DevOps Topologies - Working types

      In this episode I want to continue the talk about the team structures discussed on https://web.devopstopologies.com/ - with a focus this week on the topologies are shown to work.

      The devopstopologies.com website is based on the work by Matthew Skelton & Manuel Pais. I introduced Matthew and Manual as authors of the Team Topologies book in the last episode.  The work is a pre-cursor to the Team Topologies book - and work that I feel stands on its own two feet - with a specific look into how teams should work together to gain benefits from DevOps.

      -----

      Find this episodes show notes at: https://red-folder.com/podcasts/134

      Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

      15 min
    • #133: DevOps Topologies - Anti-Types

      In this episode I want to talk about the team structures discussed on https://web.devopstopologies.com/ - with a focus this week on the anti-types.

      The devopstopologies.com website is based on the work by Matthew Skelton & Manuel Pais. I introduced Matthew and Manual as authors of the Team Topologies book in the last episode.  The work is a pre-cursor to the Team Topologies book - and work that I feel stands on its own two feet - with a specific look into how teams should work together to gain benefits from DevOps.

      -----

      Find this episodes show notes at: https://red-folder.com/podcasts/133

      Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

      12 min
    • #132: Inverse Conway Maneuver

      In the last episode, I introduced "Conway's Law" - an observation of how our organisational structures influence our software structures.

      In this episode, I want to talk about how we can utilise this law when we want to improve problems in our software structures - commonly referred to as the "Inverse Conway Maneuver".

      Why you might be interested in this episode:

      • A recap of Conway's Law and the negatives you may be observing
      • How the same law can be used to re-organise our teams to improve on those negatives
      • Ideas from the "Team Topologies" book which build on this to define 4 team types and 3 team interaction modes for improving the flow of our software change

        • -----

        Find this episodes show notes at: https://red-folder.com/podcasts/132

        Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

        11 min
      • #131: Conway's Law

        In this episode, I introduce Conway's Law, which talks about how our software structures will reflect the structures of the organisations that create them.

        Why you might be Interested in this episode:

        • Why our organisational structures affect software structure
        • The history of "Conway's Law"
        • The negatives that the Law can help us highlight
        • And why the adoption of Microservices and small Cross Functional Teams helps to alleviate those negatives

          • -----

          Find this episodes show notes at: https://red-folder.com/podcasts/131

          Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

          8 min
        • #130: To Checklist or not to Checklist

          This episode, I want to take a look at Checklists - when to use and when not to.

          Much of this episode is inspired by the Sight Reliability Engineering practices that come out of Google.

          Why you might be interested in this episode

          • The value of a checklist
          • Situations where it is appropriate
          • And situations where it isn't

            • CORRECTION: During the episode I refer to "The Manifest Checklist" - this should have been "The Checklist Manifesto: How To Get Things Right" by Atul Gawande

            -----

            Find this episodes show notes at: https://red-folder.com/podcasts/130

            Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

            9 min
          • #129: Handling Failure

            Failure in our software systems is inevitable - be it a failing hard drive, broken network cable, power outage, virus, or simply a bug in the code.

            "Hope is not a strategy" - thus we need to think about how we handle that failure.

            Why you might be interesting in this episode:

            • The differences between how failures impact our traditional monolith applications and the more modern distributed application
            • To gain an understanding of the terms like Graceful Degredation, Cascading Failure, The Retry software pattern, The Circuit Breaker software pattern, and Deadline Propagation
            • And advice on how to find opportunities to use them

              • -----

              Find this episodes show notes at: https://red-folder.com/podcasts/129

              Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

              15 min
            • #128: Error Budgets

              In this episode, I take a look at "Error Budgets"

              Much of this episode is inspired by the Sight Reliability Engineering practices that come out of Google

              Why you might be interested in this episode:

              • You want to understand what "Error Budgets" means?
              • You're struggling to prioritise effectively between feature development, defects, risk and debt
              • You want to see how "Error Budgets" can help you with that prioritisation

                • -----

                Find this episodes show notes at: https://red-folder.com/podcasts/128

                Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

                10 min
              • #127: System Availability - Service Level Indicators, Objectives and Agreements

                In this episode, I take a look at how to measure the availability of our systems.

                Much of this episode is inspired by the Sight Reliability Engineering practices that come out of Google

                Why you might be interested in this episode

                • How Google uses Service Level Indicators, Objectives and Agreements
                • Why 100% uptime might not be the correct target
                • And why "uptime" might not be the best indicator in the first place

                  • -----

                  Find this episodes show notes at: https://red-folder.com/podcasts/127

                  Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

                  11 min
                • #126: State of DevOps 2021 - What it says about Site Reliability Engineering

                  The State of DevOps report provides excellent insight through rigorous analysis of its wide reaching survey.

                  The research provides evidence-based guidance to help focus on the capabilities that drive performance.

                  One of those are Site Reliability Engineering practices that came out Google's efforts to handle massive scale.

                  Why you might be interesting in this episode:

                  • What is Site Reliability Engineering
                  • How does it relate to DevOps
                  • What correlation the report found in Site Reliability Engineering use

                    • -----

                    Find this episodes show notes at: https://red-folder.com/podcasts/126

                    Have an idea for an episode topic, or want to see what is coming up: https://red-folder.com/podcasts/roadmap

                    12 min

                  About Better ROI from Software Development

                  From the publisher's feed

                  Providing advice on how to get the best Return On Investment from your Software Development.