Best Scott L Bain Podcasts (2025)

1
#75-Lean Principle: Eliminate Waste 3:11

Play Pause

4h ago3:11

3:11

In part one of my series on Lean, I examine the concept of eliminating Muda, or waste. I will show this in the context of manufacturing and software development, to compare and contrast the two.By Scott L. Bain

1
#74: Introduction to Lean 3:19

20h ago3:19

3:19

This will be the first in a series on Lean Manufacturing and Lean Software Development, which is a major enabled of agile processes.By Scott L. Bain

1
#73-AI: The Future Of Systems Development 3:12

12d ago3:12

3:12

I conclude this series my summarizing my current views on AI and it's increasing role in the development of business automation.By Scott L. Bain

1
#72-AI: The Business Context 4:14

25d ago4:14

4:14

In the episode I will reflect on what I have learned by interacting with the management of the corporations I teach for, regarding the thoughts, concerns, and plans around AI.By Scott L. Bain

1
#71-AI: Scaling Our Effort 4:02

23d ago4:02

4:02

People fear being replaced by AI. Should they? This episode will examine why this concern may not be as founded as people think, at least when it comes to industries I am familiar with.By Scott L. Bain

1
#70-AI: A Tool For Product Development 5:02

1M ago5:02

5:02

This episode will use software development as an example of how AI can be used to make the product development process more efficient, and less wasteful. This is an example which I believe could apply to any kind of product.By Scott L. Bain

1
#69-Artifical Intelligence - Introduction 3:33

2M ago3:33

3:33

This podcast will kick off a series of episodes on AI, and my personal view of it.By Scott L. Bain

1
#68-Shift left - Conclusions 4:04

2M ago4:04

4:04

This week I will wrap up the notion of Shift Left, and introduce the next topic for this podcast.By Scott L. Bain

1
#67-Shift left - Detecting Defects During Analysis 3:47

2M ago3:47

3:47

The final "shift left" I will examine is the detection of defects during the planning process, specifically requirements analysis. It represents one of the most important and also most difficult challenges that face us when developing products.By Scott L. Bain

1
#66-Shift left - Detecting Defects During Design 3:28

2M ago3:28

3:28

In our continuing effort to shift the detection of defects and other mistakes to earlier and earlier phases in our development process, this week I'll discuss the role that design can play.By Scott L. Bain

1
#65-Shift left - Detecting Defects During Implementation 3:57

2M ago3:57

3:57

This week we will examine how defects can be detected and sometimes even prevented during the implementation of the product as analyzed and designed in the previous phases.By Scott L. Bain

1
#64-Shift left - Detecting Defects During Integration 3:30

3M ago3:30

3:30

We're shifting left again, to the integration phase that precedes traditional testing. What defects can and should ideally be detected at this point, and how can we accomplish this? That's what this episode with examine.By Scott L. Bain

1
#63-Shift left - Detecting Defects During Testing 3:51

3M ago3:51

3:51

We're shifting left, and the next shift involves uncovering bad or missing behavior during the traditional testing phase. Such testing is important and necessary, but is it enough? We'll see.By Scott L. Bain

1
#62-Shift Left – Detecting Defects During Deployment 3:27

3M ago3:27

3:27

In this episode, I will investigate the first step in shifting left, which is to detect product defects at the time they are sold and deployed but before they are in use by the customer, and therefore cannot impact them.By Scott L. Bain

1
#61-Shift Left – Detecting Defects During Product Usage 3:23

3M ago3:23

3:23

The next series of podcasts will examine the concept of shift left, which deals with the way we determine and remediate defects in our product. This week I will start with the notions of detecting these defects when the product is being used.By Scott L. Bain

1
#60-Shift Left - Introduction 3:25

4M ago3:25

3:25

This episode will introduce the concept of the "Shift Left" initiative in product development, and will set the stage for a series of podcasts that examine key aspects and implications of it.By Scott L. Bain

1
#59-The Structure of an Acceptance Test 4:05

4M ago4:05

4:05

This episode is about the creation of acceptance tests, who should write them and how they should be structured, to get the maximum value from them.By Scott L. Bain

1
#58-The Risk of The Missing Stakeholder 3:16

4M ago3:16

3:16

This episode will tell you a story about a time when missing a critical stakeholder caused a company to make a potentially disastrous mistake in their business automation.By Scott L. Bain

1
#57-Requirements vs. Expectations 3:41

4M ago3:41

3:41

This episode will examine the difference between Requirements and the Expectations that drive them, and suggest ways that we can better serve our organization by focusing on the latter.By Scott L. Bain

1
#56-Utilize the Power of Information Radiators 4:05

5M ago4:05

4:05

Information radiators are extremely useful to an agile organization. But often there are such radiators that have been missed. This episode will investigate this problem.By Scott L. Bain

1
#55 - Measureing Agile Progress Effectively 4:36

5M ago4:36

4:36

How you measure the progress of an agile team will fundamentally effect how much value that team will produce, since that measurement will reflect that value. What should that measurement consist of? That's the topic for this week.By Scott L. Bain

1
#54-Changing Change, Part 4 4:46

5M ago4:46

4:46

This week I will relate the notion of "changing change" to the test-driven development process, in two different senses.By Scott L. Bain

1
#53-Changing Change, Part 3 3:47

5M ago3:47

3:47

Part three of this series on changing our relationship to change deals with the concept of encapsulating variation in business automation. This is expressed in non-technical language and should be useful to those that lead product development initiatives.By Scott L. Bain

1
#53-Changing Change, Part 2 3:02

6M ago3:02

3:02

This episode will explore another aspect of the agile design process, from a non-technical point of view.By Scott L. Bain

1
#52-Changing Change, Part 1 4:46

6M ago4:46

4:46

If we are to be successfully agile, we must embrace unpredictable change. But to do that, we have to fundamentally alter our relationship to change itself. This is part one of a series about how I recommend teams accomplish this.By Scott L. Bain

1
#51-Responding to Change 4:51

6M ago4:51

4:51

The fourth point of the Agile Manifesto, that we value responding to change over following a plan, has massive implications for the way agile teams are managed. This podcast will introduce the issues that result, and will lead to the next series.By Scott L. Bain

1
#50-Implications of the Agile Manifesto, Conclusions 5:22

6M ago5:22

5:22

This week I will answer the questions raised over the last four Agile Tips, each a different aspect of the Agile Manifesto. I'll also set the stage for what to expect next from this series.By Scott L. Bain

1
#49-Implications of the Agile Manifesto, Part 4 3:05

6M ago3:05

3:05

This week I will tackle the four point of the Agile Manifesto, with an eye toward my conclusion podcast next week.By Scott L. Bain

1
#48-Implications of the Agile Manifesto, Part 3 3:07

7M ago3:07

3:07

This week I will cover part three of four in the Agile Manifesto, as preparation for my final entry in this series that will suggest how to address these implications in your organization.By Scott L. Bain

1
#47-Implications of the Agile Manifesto, Part 2 3:31

7M ago3:31

3:31

This week I will investigate part 2 of the Agile Manifesto, as part of my series of four podcasts on the subject.By Scott L. Bain

1
#46-Implications of the Agile Manifesto, Part 1 3:09

7M ago3:09

3:09

This week I'll examine the first point in the Agile Manifesto, as part of a series of four podcasts.By Scott L. Bain

1
#45-Implications of the Agile Manifesto 3:00

7M ago3:00

3:00

In this episode we will examine the roots of the Agile Movement, and delineate the Agile Manifesto that came from those roots. This will begin a series of five podcasts that point out the implications of each item in this manifesto.By Scott L. Bain

1
#44-Maintain an Organizational Glossary 2:51

8M ago2:51

2:51

No matter what kinds of products and services an organization offers, there are terms that are specific to them. These terms must be carefully defined and consistently updated as things change. This podcast is all about creating such a set of definitions.By Scott L. Bain

1
#43-The Four Quadrants of Requirements 4:41

8M ago4:41

4:41

This episode will introduce a useful framework for organizing requirements as the are identified. Such organization can be very helpful in collaboration and validation throughout an agile process.By Scott L. Bain

1
#42-The Agile Use of Inheritance 3:45

8M ago3:45

3:45

Various technologies provide us with the concept of "inheritance". What should this used for, ideally, in an agile development environment? This episode addresses this question in a way that should be interesting to non-technical people as well as developers and testers.By Scott L. Bain

1
#41-Agile Architecture-SOA AND SAAS 2:55

8M ago2:55

2:55

The way we create business automation in the modern environment has been influenced by the strength of various innovations that have preceded us. This week I'll introduce this idea, and then over the next few episodes will examine some of the implications and opportunities.By Scott L. Bain

1
#40-Writing Specifications as Tests 3:35

9M ago3:35

3:35

Last week I pointed out that Test-Driven Development, even though it is named as it is, is not a testing activity but rather the creation of an executable specification. So how does this change how they are written? That's the subject of this episode.By Scott L. Bain

1
#39-Do I Really Have to Test Everything? Third (and Final) Answer 4:55

10M ago4:55

4:55

This week I wrap up my answer to the question of three weeks ago and is so going point out, perhaps, the most important aspect of TDD, and how to make sure it delivers all the value it is capable of.By Scott L. Bain

1
#38-Do I Really Have to Test Everything? Second Answer 3:25

10M ago3:25

3:25

Part two of my answer to the question posted two weeks ago. There is one more to come, next week. It may be the most crucial of these answers.By Scott L. Bain

1
#37-Do I Really Have to Test Everything? First Answer 3:24

10M ago3:24

3:24

This is my first answer to the question posed last week. There will be two more in future weeks.By Scott L. Bain

1
#36-Do I Really Have to Test Everything? Introduction 3:27

10M ago3:27

3:27

Teaching Test-Driven Development, either in the unit testing form for developers or the acceptance testing that anyone can learn and do, this questions almost always arises at some point. It's actually an excellent question and can yield a lot of value in answering it. This episode will explain why.By Scott L. Bain

1
#35-The Principle of the Useful Illusion Part 2 3:19

10M ago3:19

3:19

How does this principle apply to the notion of an agile process? I think it fundamentally changes the way we create automation, and the value that automation ultimately provides. This week I explain why.By Scott L. Bain

1
#34-The Principle of the Useful Illusion Part 1 4:37

11M ago4:37

4:37

This is kind of a fun one. I start by pointing out that, regardless of appearances, computers are not really doing any of the things we think they are doing. Examining this fact, and it is a fact, leads to some interesting and I think useful insights. Next week, I'll drive this idea into practicality.…

1
#33-Product Confusion Reveals Coupling 3:17

11M ago3:17

3:17

Products that are difficult to use or illogical in their design can seriously impede their value. This episode will examine an example of such a problem, from the author's own personal experience with a new car.By Scott L. Bain

1
#32-Legacy Code and Magic Buttons Part 2 3:02

11M ago3:02

3:02

Last week I teased the notion that it's possible to bring your legacy code under better control by using a magic button. While such buttons obviously do not exist, this week I'll outline how to get the value of such a resource anyway, at a manageable cost.By Scott L. Bain

1
#31-Legacy Code and Magic Buttons Part 1 3:22

11M ago3:22

3:22

What is the best way to deal with the fact that most organizations have a high degree of vulnerability to the quality (or lack thereof) of the legacy systems they depend upon? This week I'll discuss a thought experiment that helps us to understand this conundrum, and next week I'll show you what to do about it.…

1
#30-Follow The Open-Closed Principle 3:50

12M ago3:50

3:50

In order to embrace change, as agile says we must, we must make sure that changes to the system going forward do not create excessive waste and/or delays. Part of how we can do this is to follow good principles, such as the Open-Closed Principle. This episode will explain this principle, and what it means.…

1
#29-Refactoring is Lean Pt. 2 3:44

12M ago3:44

3:44

Last week I discussed the notion of refactoring, and why business people often fail to see the value in it. This week I explore what that value is, and how best to express it honestly.By Scott L. Bain

1
#28-Refactoring is Lean Pt. 1 2:47

12M ago2:47

2:47

Should a Project Manager allow a development team to spend time and resources on Refactoring? What is refactoring, and why do they want to do it? It seems to have no business value whatsoever. This episode, and the next, will explore this question and offer a way to resolve it.By Scott L. Bain

1
#27-Why Design Patterns are Agile 3:04

1y ago3:04

3:04

If you are familiar with the concept of a "Design Pattern" you may well feel that they reflect an older view of development. Indeed, the patterns were first identified before the popularity of agile approaches. That said, they are entirely agile, and this episode is about why that is.By Scott L. Bain