Better ROI from Software Development

We all know that a heft bonus improves productivity. Its a management stable - dangle the carrot and good results just roll it.

But is that really true?

In this episode, I look at the negative consequences of using bonuses for motivation - once again, leaning heavily on the work of Daniel Pink and his book "Drive" to explore the idea of extrinsic and intrinsic motivators - and what works best with modern software development.

-----

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

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

Occasionally I record an episode exploring something that may commonly be considered good, or common practice, but is actually causing dysfunctional, and unexpected, results in modern software development - and thus would be bad for ROI.

This week I look at the RAG (Red Amber Green) status reporting and its impact on modern software development.

-----

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

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

Occasionally I record an episode exploring something that may commonly be considered good, or common practice, but is actually causing dysfunctional, and unexpected, results in modern software development - and thus would be bad for ROI.

This week I want to introduce you to a strange beast, found way too often in our organisations, the HiPPO. While the term might sound comical, its implications in the corporate world, and our software development, are anything but.

-----

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

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

In this episode I wanted to explore what it means to be a manager for a development team - and more importantly in the world of diverse, cross-functional, self-managing, value stream teams, does the manager still have a role to play?
Picture this: You've successfully built a software development team that's as diverse as it is dynamic. They are cross-functional, self-managing, and entirely focused on delivering continuous value. You've assembled the dream team. But here's the central question we'll be grappling with today - if you've created this ideal team, what role, if any, should you as the manager play?

Could you have possibly made yourself redundant?

-----

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

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

In this episode I wrap up this series of episodes on transaction-based costing by looking at the common themes and revisiting some of my initial reasons for starting the series.

For me the key takeaway is the common theme of constantly rethinking our best practice and adapting to the changing landscape of technology, our organisation, and our markets. -----

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

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

In this episode I continue the discussion on transaction-based costing by looking at the relationship with Small Batch Sizes.

I began by defining small batch sizes - the breaking of work down into more manageable tasks, which can improve the speed and quality of your output.

I then explore how small batch sizes play a pivotal role in transaction-based costing, promoting efficiency and cost-effectiveness by enabling more precise tracking and control of costs.

I also examine the benefits that come with this combination - enhanced agility for software changes, better predictability for improved financial forecasting, enhanced transparency for granular insights into cost allocations, and streamlined processes for reducing waste and improving value delivery.

And to wrap up, I talk about some the challenges of a transition from traditional methods and implementing small batch sizes.

-----

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

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

In this episode I continue the discussion on transaction-based costing by looking at the relationship with Value Stream Teams.

I start by defining value stream teams - cross-functional groups that work towards delivering value from customer request to service delivery. I explore how they fit into the software development landscape, leveraging principles of lean manufacturing for better efficiency.

I recap the transactional cost mindset, comparing it with the traditional CapEx/ OpEx model - highlighting the benefits of a transaction-based approach for improving visibility and accountability for better decision making.

I then discuss the importance of breaking down organizational silos - examining the significance of focusing on the end-to-end flow of value in software development, emphasizing how transaction-based costing helps optimize this flow for better financial outcomes.

Lastly, I highlight how this approach can enhance agility and speed up time to market.

-----

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

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

In episode, I discuss the relationship between transaction-based costing models, serverless computing, and cloud computing in a dynamic business environment.

I look at how this model offers flexibility, scalability, and cost-effectiveness by allowing businesses to pay only for the resources they use - and compare this model to the traditional capex/opex model and highlight how the transaction-based model, combined with serverless and cloud, can lead to higher profit margins, better financial planning, and the ability to invest in other areas of the business.

-----

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

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

Are you struggling to track the true return on investment in your software development projects?

Traditional CapEx and OpEx models may not be enough in dynamic environments. But don't worry, there's a solution!

In this episode, I introduce transaction-based costing.

By assigning a cost to each transaction within the software development process, you can achieve better transparency, tighter cost control, and a more direct linkage to outcomes. -----

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

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

In this episode, I discusses the potential benefits of organization-specific AI Coding Assistants.

While AI won't replace developers, it can provide more refined and less generic answers, leading to improved code quality and enhanced productivity within the organization. By tailoring AI Coding Assistants to an organization, it can understand and adapt to project-specific requirements, suggest appropriate design patterns and architectural improvements, integrate with existing development tools and workflows, and contribute to knowledge sharing and onboarding. -----

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

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

In this episode I discuss the potential negatives of using AI Coding Assistants in software development.

I cover topics such as:

• over-reliance and skill degradation,
• lack of creativity and innovation,
• false positives and incorrect suggestions,
• limitations with domain-specific knowledge,
• dependency on internet connectivity,
• adoption and learning curve,
• and privacy and security concerns.

-----

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

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

In this episode, I discusses the expected benefits of using AI Coding Assistants in software development.

These benefits include:

• increased productivity,
• code optimization,
• learning and knowledge enhancement,
• error detection and debugging,
• collaboration and coding consistency,
• code documentation,
• and code completion and suggestions.

-----

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

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

In this episode I discuss the growing use of AI Coding Assistants in software development, particularly large language models like ChatGPT.

I explain how AI Coding Assistants can greatly improve productivity and efficiency for developers, with examples of popular products in the market.

AI Coding Assistants will not replace developers, but rather enhance their work.

-----

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

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

In this episode, I review last weeks conversation with ChatGPT, an artificial intelligence language model developed by OpenAI. I discuss the technology behind ChatGPT, its potential risks and benefits, and the ethical and societal questions it poses. I also talks about my personal experience with ChatGPT and my intention to use it for podcast scripting.

-----

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

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

In this episode, I aim to explain what ChatGPT is and its future for a non-technical managerial audience - and I do this through conversing with ChatGPT.

I share this first chat I've had with ChatGPT - with a followup planned for next week to talk through my experience and initial thoughts.

-----

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

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

In this episode, I discusses the LastPass breach that occurred last year and how it has prompted me to improve my password hygiene.

I talk about why the breach has led me to move away from LastPass - and how it has provided an opportunity to clean up my password data and reset passwords for critical accounts.

I also re-emphasizes the importance of good password hygiene and using multi-factor authentication for added security. -----

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

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

In this episode, I discuss my personal experience with Microsoft Certifications and their value in the IT industry.

I believe that certifications provide a wider breadth of knowledge that may not be obtained through day-to-day work - but is still no subsitute for experience when it comes to recruitment.

-----

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

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

In this episode, I introduce the Actor Model as a Design Pattern that can offer faster and more efficient processing by managing state in memory.

I discuss potential use cases for the Actor Model, such as in online gaming and IoT sensors, but acknowledge that it is a different development model than traditional approaches.

-----

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

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

In this podcast episode, I introduce the concept of design patterns in software development and explain their importance in improving code quality and readability.

I give examples of design patterns in everyday life and emphasize how they can speed up the development process by providing tested and proven development paradigms.

I also highlight the confusion that can arise when design patterns are not followed correctly.

-----

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

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

This is the first episode after a prolonged break - so firstly, an apology for the gap in recordings.

In this episode I wanted to talk about why I took a break, the lessons to learn and what I've been up to over the past few months.

-----

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

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

As we start the new year, its not uncommon for organisations to looks at budgets and general expenditure - and given the current financial outlook, I would have expected many organisations to be taking the time to look at how best to weather the storm.

I've found that many organisations typically react with a combination of cost cutting and putting pressure on staff for "more" in such periods.

However like many "traditional" sound managerial practices, this cause dysfunctional and negative outcomes in the Age of Software & Digital - and specifically when it comes to any form of knowledge work like Software Development.

The problem we have is that these "traditional" managerial practices have become muscle memory - so ingrained with the managerial psyche that it can be a difficult thing to re-think.

In this episode, I want to ask you to re-think about 3 things in particular:

• Training and learning
• Doing less work
• Take advantage

-----

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

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

This episode, I wanted to take a quick look at the 2022 edition of the State of DevOps Report.

I've talked a number of times about the State of DevOps report. I originally introduced it back in episode 13, and last year I devoted seven episodes, 120-126, to a deep-dive into the 2021 edition.

-----

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

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

I've long held the belief that Estimation is the source of much dysfunction within Software Development.

However, with a New Year, I'll like to take this as an opportunity to revisit my strong opinions on the subject - are they still valid? Are there better ways?

In this episode I recap the understandable desire for Software Development Estimations, why I feel that its a source of so much dysfunction and my plan for the coming year to test and challenge my opinions.

-----

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

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

I originally discussed Gantt charts back in episode 62, but I found more history behind them while researching Scientific Management and Taylorism for episode 156. I originally thought to include this additional history in that episode, but it felt out of place - thus this separate episode to revisit Gantt charts.

-----

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

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

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why of the podcast.  Over recent episodes, I've take a deeper dive into the themes of the pitch and why they made the cut.

And in this weeks episode, I want to explore the idea that there is no a one-size fits all approach to Software Development

-----

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

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

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why of the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

In this episode, I look at why Software Development cannot be deterministic - why do have so many unknowns - why can't we make it as deterministic as moving pig-iron or flipped hamburgers at McDonalds.

-----

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

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

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why of the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

In this episode, I want to take a deeper dive into the management practices of yesterday - where they came from and why they gave us success yesterday but are failing us today and certainly not fit for tomorrow

-----

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

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

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

Over the last few episodes, I've looked at the business side of the pitch and how our organisations need to embrace changes as something they do rather than something that happens to them.

In this episode, I want to move onto the Software Development half of the pitch, and look at its age and maturity.

-----

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

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

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut. 

In this episode, I follow on from last weeks introduction of change, brought on by the current Age of Software and Digital, by providing more evidence of change - along with why change shouldn't be something that happens to an organisation - change should be something that an organisation "does".

-----

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

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

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

In this episode, I wanted to talk about why I led with "Welcome to the Age of Software and Digital".

-----

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

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

In episode 150, I reintroduced this series with a new pitch. It was my way of taking what I've learnt over the last three years, the last 150 episodes, and almost 33 hours of content and updating the why the podcast.  Over the coming episodes, I'll take a deeper dive into the themes of the pitch and why they made the cut.

If you listen back to the pitch, you will notice that it is almost half way through the 5 minutes and 21 seconds before I actually mention "software development" - which might seem odd for a podcast entitles "Better ROI from Software Development".

In this episode, I explain why I devote pretty much the entire first half of the pitch to talking about the business context we find ourselves in.

-----

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

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

On the 23rd September, the UK Chancellor announces a series of change during a "mini-budget".

The mini-budget, and its contents, have been the subject of much debate ever since.

What might have been missed by many people where the changes to the IR35 off-payroll rules - which, as I discuss in this episode, could have material impact on both the contractor AND permanent recruitment markets

Note: Since the original recording and release of this episode, the proposed reversal of the "Off-Payroll" rules has been dropped.  This episode does still however provide some value with a description of IR35 and the Off-Payroll rules.

-----

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

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

Welcome to the 150th episode of the podcast.

In this episode, I take a moment of introspection to revisit the "pitch" for this series.

-----

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

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

Over the last few episodes, I've focused on legacy software - what it is, how it occurs, and various strategies to deal with it.

Alongside that legacy software is the legacy data - which is arguably more important than the data.

In last week's episode, I talked about why thinking about that legacy data is so important.

In this week's, I will provide advice for dealing with it.

-----

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

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

Over the last few episodes, I've focused on legacy software - what it is, how it occurs, and various strategies to deal with it.

Alongside that legacy software is the legacy data - which is arguably more important than the data.

In this episode, I want to talk about why thinking about that legacy data is so important

-----

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

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

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

A few weeks ago, I introduced three methods to address legacy software:

• Evolution - continual improvement to the existing system to bring it out of its "legacy" state
• Revolution - the wholesale replacement of system with something new
• And Outsourcing - using a third party to either maintain or replace the legacy system

In this episode, I take a deeper dive into Outsourcing

-----

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

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

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software. 

Two weeks ago, I introduced three methods to address legacy software: 

• Evolution - continual improvement to the existing system to bring it out of its "legacy" state 
• Revolution - the wholesale replacement of system with something new 
• And Outsourcing - using a third party to either maintain or replace the legacy system In this episode, I take a deeper dive into Revolution 

-----

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

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

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In last week's episode, I introduced three methods to address legacy software:

• Evolution - continual improvement to the existing system to bring it out of its "legacy" state
• Revolution - the wholesale replacement of system with something new
• And Outsourcing - using a third party to either maintain or replace the legacy system

In this episode, I take a deeper dive into Evolution

-----

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

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

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen as a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll introduce three methods to address legacy software:

• Evolution - continual improvement to the existing system to bring it out of its "legacy" state
• Revolution - the wholesale replacement of system with something new
• And Outsourcing - using a third party to either maintain or replace the legacy system

I briefly compare the three options and will dig further into each in future episodes.

-----

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

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

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll describe a simply risk matrix that can be used to monitor and highlight how legacy your software products are.

-----

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

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

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll talk about some of the causes behind how our software can become "legacy".

-----

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

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

This is part of a new mini-series looking at Legacy software - the term "legacy" is often seen a positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll talk about the impact of Legacy software and why the software industry invests so much effort into addressing.

-----

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

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

This is the start of a new mini-series looking at Legacy software.

The term "legacy" is often seen as positive - yet within computing it is a negative term generally uses to indicate the need to replace hardware or software.

In this episode, I'll give you an introduction to Legacy software.

-----

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

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

I've talked many times about the productivity benefits from automation.

In this episode, I talk about the higher value benefits we get from automation - something you could describe as a side-effect.

Automation gives us productivity - but not just to do more, but to do better.  Automation gives us the opportunity to elevate the work carried out by our teams - ultimately leading to better, cheaper, more reliable, more secure software.

I look at common automation techniques and how they helps to free up our teams:

• Automated Testing
• Continuous Integration, Deployment & Delivery
• Infrastructure-as-Code  

-----

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

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

I've talked many times about the productivity benefits from automation.

In this episode, I talk about the knowledge sharing benefits we get from automation - something you could describe as a side-effect.

I discuss how, to be effective, any new software developer needs to learn not just the technical tools and practices, but also the domain - the environment in which the software will operate.

I then look at how automation practices like Continuous Integration, Deployment & Delivery, Infrastructure-as-Code and Automated Testing can help provide that knowledge.

-----

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

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

I've talked many times about the productivity benefits from automation.

In this episode, I talk about the auditability benefits we get from automation - something you could describe as a side-effect.

I discuss:

• Why having audit data is helpful to our organisations
• How automation can help to provide that audit data
• How automation can remove a whole class of questions over manual access to production environments
• How automation can improve on the overly bureaucratic, and often harmful, Change Advisory Boards found in many organisations
• And how your auditor can not only help, but will likely to be keen to do so

-----

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

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

I've talked many times about the productivity benefits from automation.

In this episode, I talk about the security benefits we get from automation - something you could describe as a side-effect.

I discuss:

• Reduced access
• Reduced manual interpretation
• Logs
• Controllable environments
• Automated security tools
• Signed software

-----

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

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

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

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

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