#52-Changing Change, Part 1

Agile Tips

1:00:36

Do you have fond childhood memories of summer camp? For a chance at $250,000, campers must compete in a series of summer camp-themed challenges to prove that they are unbeatable, unhateable, and unbreakable. Host Chris Burns is joined by the multi-talented comedian Dana Moon to recap the first five episodes of season one of Battle Camp . Plus, Quori-Tyler (aka QT) joins the podcast to dish on the camp gossip, team dynamics, and the Watson to her Sherlock Holmes. Leave us a voice message at www.speakpipe.com/WeHaveTheReceipts Text us at (929) 487-3621 DM Chris @FatCarrieBradshaw on Instagram Follow We Have The Receipts wherever you listen, so you never miss an episode. Listen to more from Netflix Podcasts.…

about a year ago 4:46

MP3•Episode home

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.

58 episodes

#Tech #Scott Bain

Agile Tips

#52-Changing Change, Part 1

Agile Tips

published about a year ago

MP3•Episode home

58 episodes

#Tech #Scott Bain

All episodes

Agile Tips

1
#57-Requirements vs. Expectations 3:41

6 days 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.

Agile Tips

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

13 days 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.

Agile Tips

1
#55 - Measureing Agile Progress Effectively 4:36

20 days 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.

Agile Tips

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

27 days ago4:46

4:46

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

Agile Tips

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

5 weeks 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.

Agile Tips

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

6 weeks ago3:02

3:02

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

Agile Tips

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

7 weeks ago4:46

4:46

Agile Tips

1
#51-Responding to Change 4:51

8 weeks 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.

Agile Tips

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

9 weeks 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.

Agile Tips

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

10 weeks 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.

Agile Tips

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

11 weeks 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.

Agile Tips

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

12 weeks 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.

Agile Tips

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

13 weeks ago3:09

3:09

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

Agile Tips

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

14 weeks 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.

Agile Tips

1
#44-Maintain an Organizational Glossary 2:51

15 weeks 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.

Agile Tips

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

16 weeks 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.

Agile Tips

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

17 weeks 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.

Agile Tips

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

18 weeks 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.

Agile Tips

1
#40-Writing Specifications as Tests 3:35

19 weeks 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.

Agile Tips

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

23 weeks 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.

Agile Tips

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

24 weeks 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.

Agile Tips

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

25 weeks ago3:24

3:24

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

Agile Tips

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

26 weeks 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.

Agile Tips

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

27 weeks 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.

Agile Tips

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

28 weeks 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.…

Agile Tips

1
#33-Product Confusion Reveals Coupling 3:17

29 weeks 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.

Agile Tips

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

30 weeks 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.

Agile Tips

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

31 weeks 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.…

Agile Tips

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

32 weeks 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.…

Agile Tips

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

33 weeks ago3:44