16 episodes

What does it takes to deliver brilliant software solutions to your customers? Whether they be internal or external. Whether you see your product as a cost centre or a profit centre.

Every time I talk about a subject on the the ways and whys of software delivery. How it is built, tested, deployed, made available for our users and supported. The complete lifecycle not just of our software, but the systems and tools and processes and ways of working that we need in order to make it happen.

How do you improve your software product, while still supporting customers and being a reliable platform?

Software Delivery Club is about all the build, test, infrastructure, automation, tooling, observability, feedback, planning, product, organisation.

Software Delivery Club Richard Bown

    • Technologie

What does it takes to deliver brilliant software solutions to your customers? Whether they be internal or external. Whether you see your product as a cost centre or a profit centre.

Every time I talk about a subject on the the ways and whys of software delivery. How it is built, tested, deployed, made available for our users and supported. The complete lifecycle not just of our software, but the systems and tools and processes and ways of working that we need in order to make it happen.

How do you improve your software product, while still supporting customers and being a reliable platform?

Software Delivery Club is about all the build, test, infrastructure, automation, tooling, observability, feedback, planning, product, organisation.

    Putting the Product back in the MVP

    Putting the Product back in the MVP

    When was the last time you did a Minimal Viable Product that was actually minimal? How often do we get it right and truly focus on delivering something of value to the customer?
    On this week's podcast, I riff on the idea of how to get a true MVP, not only past the idea stage, but into production no matter what type of company you are. By looking at the constraints that we have in play at any one time, we can determine before we get started with an MVP how it might be rolled out.
    We also touch on the importance of marketing for your MVP and/or product – and ensuring that you have a customer base that wants it before you get there. How you can even use your compliance journey to road-test your idea.
    Join me for this discussion and, as always, let me know your thoughts about what’s gone wrong and what's gone right with your MVPs!
    SHOW NOTES
    This show inspired by some systems thinking, some writing and also the theory of constraints.
    https://richardwbown.com/how-the-mvp-has-lost-its-meaning/ (https://richardwbown.com/how-the-mvp-has-lost-its-meaning/)
    https://en.wikipedia.org/wiki/Theory_of_constraints (https://en.wikipedia.org/wiki/Theory_of_constraints)
    https://richardwbown.com/approvals-come-first/ (https://richardwbown.com/approvals-come-first/)
    QUOTES
    00:49: “Much is made of the MVP, the minimal viable product. But so rarely is it executed in a meaningful and valuable way.”
    02:02: “Using an MVP to road-test new tech is not always a smart move.”
    03:19: “architecture just means big decisions that you're probably not going to undo later.”
    03:59: “There is a tension here between architecture and MVP”
    06:35 - “By narrowing our proposal for our MVP. We stand a greater chance of getting it approved and rolled out in order to gather feedback”
    07:28: “The reasoning behind the processes that build up around change control are all there for sensible reasons.”
    08:15: “Whatever of path is open to you, your MVP won't deliver unless it has users”
    08:49: “Don't leave the marketing to last or as an afterthought. And this applies not just to startups or individuals, but also to the scale-up or corporate world”

    • 10 min
    Between Product and Engineering

    Between Product and Engineering

    In this episode we explore the way that technology, tools and architecture can affect the product that you are building. As engineers do we need to think more about product side? As product marketers what can we do to understand how the technology choice informs or limits our product possibilities? How do we deliver software in an open source project vs how do we deliver software in a corporate banking environment? What are the constraints that we need to be aware of in our decisions and how the customer need informs that. How we need to enjoy what we’re building - and make sure that we continue to enjoy building it as an individual, a team or as a company.
    Once again I really enjoyed recording this one and asking myself some hard questions. Perhaps you have more questions that from it? Please get in touch with me via the Software Delivery Club. I’d love to hear from you!
    https://softwaredelivery.club (https://softwaredelivery.club)
    SHOW NOTES
    Dave Farley - Modern Software Engineering (https://twitter.com/davefarley77 (https://twitter.com/davefarley77)):
    https://www.amazon.com/Modern-Software-Engineering-Discipline-Development/dp/0137314914 (https://www.amazon.com/Modern-Software-Engineering-Discipline-Development/dp/0137314914)
    April Dunford’s Obviously Awesome (https://twitter.com/aprildunford):
    https://www.aprildunford.com/obviously-awesome (https://www.aprildunford.com/obviously-awesome)
    Rosegarden Linux Audio and Midi Sequencer and Notation Editor:
    http://rosegardenmusic.com/resources/authors/ (http://rosegardenmusic.com/resources/authors/)
    You can also download a compilation of my best blog posts in PDF form. I call it:
    https://richardwbown.com/wp-content/uploads/2022/08/A-Systems-Approach-to-Software-Product-Delivery-v1.1-Richard-Bown.pdf (A Systems Approach to Software Product Delivery)

    • 14 min
    Getting your Evenings and Weekends Back

    Getting your Evenings and Weekends Back

    Making software is fun. Running software can be less fun. How do you do both and not go insane? How do you make sure you're not working all the time to keep your (virtual) baby up in the air?
    The same rules apply whether you're a startup, a scale-up, a corporate, an individual, an open source project contributor. You're part of your own support problem.
    This time I discuss what it's like to be a coder who wants to have it all - the good times and the bad times - but wants to limit the bad times to working hours only. I hope you enjoy it as much as I made recording it.
    NOTES
    XKCD 242 - The Difference:
    https://xkcd.com/242/ (https://xkcd.com/242/)
    Brian Scanlan about Intercom's approach to on call.
    https://www.intercom.com/blog/rapid-response-how-we-developed-an-on-call-team-at-intercom/ (https://www.intercom.com/blog/rapid-response-how-we-developed-an-on-call-team-at-intercom/)
    And he talked about this recently on Adventures in DevOps:
    https://topenddevs.com/podcasts/adventures-in-devops/episodes/reducing-on-call-engineer-burnout-with-a-volunteer-management-infrastructure-devops-121 (https://topenddevs.com/podcasts/adventures-in-devops/episodes/reducing-on-call-engineer-burnout-with-a-volunteer-management-infrastructure-devops-121)
    Inspiring music that helped me write this:
    https://en.wikipedia.org/wiki/Milk_%26_Kisses (https://en.wikipedia.org/wiki/Milk_%26_Kisses)
    https://en.wikipedia.org/wiki/Reading,_Writing_and_Arithmetic (https://en.wikipedia.org/wiki/Reading,_Writing_and_Arithmetic)
    QUOTES
    01:25 - How did it feel the first time you wrote something in a computer language that maybe you just learned and it worked perhaps first time
    02:50 - We're in that space where creation is flowing. But at some point reality bites. Then we need to do something with this thing that we've created.
    5:05 - What is happening tonight? Mummy, why can't we go out to the zoo this weekend? I know guilt right. The point I'm really laboring here is that one should be proud of your creations.
    05:18 - All of our creations need us. All of these things are calling for our time.
    06:48 - Some of the most successful systems on the planet have been built on a knife edge of functional validity.
    07:43 - Your job is therefore to minimize that risk and ensure that you can roll back or fix forward with the least possible effort.
    09:21 - Be aware of your legacy as a coder. Think carefully about how your persisted data will be managed.

    • 11 min
    Welcome to Software Delivery Club - The Reboot

    Welcome to Software Delivery Club - The Reboot

    Welcome to the Software Delivery Club.
    Every week, we explore different aspects of the business of delivering software into production. Talking to industry experts about how they get to keep their production software running, whether you build or buy, how they cope with new features and product changes, how they keep their customers satisfied while also keeping themselves and their engineers happy, what tools like they like and which ones they don’t as well as tales from the front line when it comes to delivering and supporting production grade software.
    NOTES
    This is the reboot of the podcast that used to be called "Automation for the Nation". The old episodes are still relevant but now we have a new name and new purpose.
    QUOTES
    00:39 "Software delivery club is the new name of this podcast." [RB]
    00:42 "It used to be called automation for the nation. While it's not a complete reboot in terms of content, I wanted to draw the line in the sand between what I was trying to do a few months ago and where this podcast is now." [RB]
    1:35 "the true magic we're looking for, I believe is at the intersection of software development practice, product and pragmatism." [RB]
    02:51 "How do you improve your product, support customers and stay reliable? Software delivery club is about that." [RB]

    • 4 min
    Thinking in Systems & Change Management

    Thinking in Systems & Change Management

    How do we manage change? Assessing urgency and what does it mean when no-one is owning a (technical) systems problem? I talk about this common problem with projects and systems and how we can resolve it, touching on Incident Management and Product Ownership.
    Secondly, I spend a few minutes talking about the book “Thinking in Systems: A Primer”. This is a classic text which describes in simple terms how interactions between systems can get so complicated. Great for those who've not thought about systems interactions before and need a basis for understanding how complexity can appear very quickly.
    NOTES
    Brief review of "Thinking In Systems: A Primer":
    https://kislayverma.com/books/book-review-thinking-in-systems-a-primer/ (https://kislayverma.com/books/book-review-thinking-in-systems-a-primer/)
    Resources for understanding Change Management (ITIL) and Product Ownership (Scrum)
    Change Management and the IT Infrastructure Library (ITIL):
    https://en.wikipedia.org/wiki/ITIL (https://en.wikipedia.org/wiki/ITIL)
    IT Service Management:
    https://en.wikipedia.org/wiki/IT_service_management (https://en.wikipedia.org/wiki/IT_service_management)
    and within that, IT Incident Managment:
    https://en.wikipedia.org/wiki/Incident_management_(ITSM) (https://en.wikipedia.org/wiki/Incident_management_(ITSM))
    What is a Product Owner?
    https://www.scrum.org/resources/what-is-a-product-owner (https://www.scrum.org/resources/what-is-a-product-owner)
    QUOTES
    "Now, when I speak to those who tell me that they have a ‘systems problem’ it’s like they’ve almost self-diagnosed. They know that they have a problem but they also seem to be able to tell me almost how I can help them fix it for them. " [RB]
    "Don't assume that a change to any system will fix a given problem without causing another problem, too. Don't assume that things work like they say they're going to work" [RB]
    "Incident Management is a process whereby you can get your systems back on track with respect to a situation with any given system" [RB]
    "the very act of fixing systems in itself requires a system and a process" [RB]

    • 11 min
    Positioning Your Business Through Better Systems

    Positioning Your Business Through Better Systems

    EPISODE SUMMARY
    This week I talk about how to position your business through better systems. How to understand how important you are at the core of the message to your customers and how you can build a system of positioning that will allow you to play with marketing messages and land on what works best for you and your ideal client.
    What systems do you need to support your positioning and marketing efforts and how they can help you understand what's working and what isn't.
    EPISODE NOTES
    Inspired by lots of reading and writing to create this podcast episode but mainly in reaction to positioning books and what I've learnt from Value Based Pricing and orienting yourself to favour the client over yourself.
    Building a Story Brand: https://buildingastorybrand.com/ (https://buildingastorybrand.com/)
    Obviously Awesome: https://www.aprildunford.com/obviously-awesome (https://www.aprildunford.com/obviously-awesome)
    Jonathan Stark Value Based Pricing bootcamp: https://jonathanstark.com/vpb (https://jonathanstark.com/vpb)
    The main message is "don't forget yourself" in the rush to build a business that you think is the right one. Client doesn't come first when you're the one that's in charge.
    Also in the recording I call the episode "Marketing Your Business Through Better Systems" but afterwards I changed my mind - this is so much more about Positioning than it is Marketing.
    QUOTES
    "How can you build it so that there is a funnel of work waiting for you every time you want to dip into it?" [RB]
    "Finding your customer is essential. Differentiation is the core of your message. And your story must make sense." [RB]
    "This is a six point list which enables you to turn your ideas into your business." [RB]
    "The systems and automations or flow from the core decisions you make these will influence your systems and processes." [RB]
    "Using analysis and tools such as MailChimp, or ConvertKit, you'll be able to see open rates of your emails, you'll be able to segment your market into locations, age ranges, demographics, perhaps, you'll be able to tag user behaviours" [RB]

    • 9 min

Top Podcasts In Technologie

Lex Fridman
RTL Nederland
Jack Rhysider
BNR Nieuwsradio
BNR Nieuwsradio
Tweakers