Agile Chuck Wagon

Chuck talked about kaizen, the lean concept of continuous improvement.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about why emotional impact is an important part of messagingSupport the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck talks about the financial concept of asymmetry of returns in terms of agile experiments.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about metaphor and how its use can propel effective retrospectives.Support the show (https://www.patreon.com/agilechuckwagon)

In keeping with the theme of the last episode, Chuck talks about corporate values, again using the 5 taekwondo values of courtesy, integrity, perseverance, self-control, and indomitable spirit. He talks about how these 5 values could be of use to an agilist.Support the show (https://www.patreon.com/agilechuckwagon)

On this episode, Chuck talks about doing the podcast during the COVID crisis and perseverance.Support the show (https://www.patreon.com/agilechuckwagon)

On this episode, Chuck talks about the idea generation technique of mind mapping.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about diversity, and why it's important in society and on agile teams.Support the show (https://www.patreon.com/agilechuckwagon)

On this episode, Chuck looks back on ten seasons of the revived Agile Chuck Wagon.Support the show (https://www.patreon.com/agilechuckwagon)

Saliency is a measure or quality of things standing out from their neighbors. Chuck talks about this information science term in the context of agile.Support the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck talks about lessons he learned during his time on the board of Agile Denver. The board of directors is a team, needs common answers to fundamental questions, and needs a good working agreement with the rest of the organization.Support the show (https://www.patreon.com/agilechuckwagon)

Fishbone or Ishikawa diagrams are a handy tool for performance root causes analysis. Chuck talks about them in the context of the Scaled Agile framework, but the tool comes from lean and can be applied anyway. It's particularly strong when paired with the 5 Whys technique.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about how to handle a situation where you only want to download part of a Git version control repository.Support the show (https://www.patreon.com/agilechuckwagon)

In this episode of the Agile Chuck Wagon, Chuck talks about why a person who isn't a programmer might want to use a version control system.Support the show (https://www.patreon.com/agilechuckwagon)

In Growing Great Employees, Erika Andersen talks about six core competencies to evaluate people against. Chuck talks about them in this episode: teamwork, judgement, initiative, results orientation, caring, and pragmatic.Support the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck talks about the 4x4 performance management framework. He compares its 4 questions to the scrum daily standup.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck gushes about the markup format Asciidoc, as well as markup in general.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about the coronavirus and its disruption to routineSupport the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck illustrates the use of Jonathan Raymond's Accountability Dial technique, with Manager Tools feedback examples as well.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about a concept from the new book The Advice Trap by Michael Bungay Stanier, the Advice Monster. This tendency to inject ourselves into coaching comes with three personas: Tell-It, Save-It, and Control-It. Chuck uses personal examples for each.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about the difference between coaching and feedback. This difference between staying curious and sharing your point of view is a line he often blurs himself. This concept comes from the new book The Advice Trap by Michael Bungay Stanier.Support the show (https://www.patreon.com/agilechuckwagon)

A quick audio note that there was no Season 9 retroSupport the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about the strategy pattern, a technique software engineers use to make programs behave more intelligently. Design patterns appear outside of software, and Chuck uses real-world examples to illustrate.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about how exercising control, ownership, reach, endurance (CORE) can help you deal with adversaries. He mentioned Morag Barrett's book Cultivate if you want to convert an adversary to an ally.Support the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck talks about the decorator pattern, one of many design patterns software engineers use.Support the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck talks about a study done by the New Economics Foundation on 5 practices that improve a person's happiness and feelings of well-being. They are Connect, Be active, Take notice, Keep learning, and Give. Thanks for sketchplanations for bringing it to my attention!Support the show (https://www.patreon.com/agilechuckwagon)

In this short episode, Chuck reminds us of the importance of remaining professional after giving notice.Support the show (https://www.patreon.com/agilechuckwagon)

In a continuing series on DevOps, Chuck talks about build systems: what they are and why they are important to DevOps success.NOTE: The episode doesn't mention build systems by name. Three popular options are Jenkins, Travis, and TeamCity.Support the show (https://www.patreon.com/agilechuckwagon)

The ESVP activity has application beyond just retrospectives. Learn about explorers, shoppers, vacationers, and prisoners in business meetings and other gatherings.Support the show (https://www.patreon.com/agilechuckwagon)

In today's episode, Chuck talks about version control. He uses software and non-software examples, then talks through the basics of git, a popular version control system, uses those running examples.Support the show (https://www.patreon.com/agilechuckwagon)

On this episode, Chuck talks about the differences between service level objectives (SLOs), service level indicators (SLIs), and service level agreements (SLAs).Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about Annie Duke's book Thinking in Bets, which has some nice parallels to agile philosophy.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck introduces the topic of DevOps or Site Reliability Engineering.Support the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck talks about how excuses prevent taking ownership of issues.Support the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about Pat Lencioni's book, The Ideal Team Player.Photo by Quino Al on UnsplashSupport the show (https://www.patreon.com/agilechuckwagon)

Chuck introduces Steve Litt's 10-step Universal Troubleshooting Process, found on troubleshooters.com.Photo by Owen Beard on UnsplashSupport the show (https://www.patreon.com/agilechuckwagon)

In today's episode, Chuck talks about Pat Lencioni's book Death by Meeting.Photo by Marvin Meyer on UnsplashSupport the show (https://www.patreon.com/agilechuckwagon)

Today, Chuck talks about situations where a group takes an action no individual approves of.Photo by Dino Reichmuth on UnsplashSupport the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck talks about a model for levels of conflict by Speed Leas. The model shares some strategies for keeping conflict from escalating.Photo by Frank Busch on UnsplashSupport the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about Jakob Nielson's 10 heuristics for create good user interfaces. They include rules of thumb like use of ubiquitous language and the need for error prevention.Photo by Kobu Agency on UnsplashSupport the show (https://www.patreon.com/agilechuckwagon)

For the last episode of season 8, I did not record a retrospective due to the hiatus. Instead, I talked about my personal reading workflow. It's enabled me to read over a book a week.Photo by Thought Catalog on UnsplashSupport the show (https://www.patreon.com/agilechuckwagon)

In a similar vein to last episode, Chuck talks about the challenges of having a development manager also be an engineering lead.Photo by Marius Ciocirlan on UnsplashSupport the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck answers a question from an old work colleague who recently went into management. Young wants to know if dev managers can fill the role of a scrum master. Chuck explains the challenges with this practice.Photo by Foto Sushi on UnsplashSupport the show (https://www.patreon.com/agilechuckwagon)

The Agile Chuck Wagon is on pause while I recover from a car accidentSupport the show (https://www.patreon.com/agilechuckwagon)

Chuck details an exercise to help people using source control learn good commit discipline.Interesting in trying it? See my code-kata respository for an implementation.Support the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck teaches you how a tomato timer can help you be manage your time and be more productive.Support the show (https://www.patreon.com/agilechuckwagon)

This week, Chuck talks about 4 pillars of too much: stuff, choice, information and speed. While originally in the context of overwhelm in children, adults suffer from this as well.Source: SketchplanationsSupport the show (https://www.patreon.com/agilechuckwagon)

Chuck talks about Nancy Hey's spectrum of feedback quality, from no feedback at all to judgmental, descriptive, targeted, and then self-recognized at the top.Source: SketchplanationsSupport the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck reviews Kent Beck's 4 Laws of Simple Design. They are that software code: Passes the testsReveals intention Has no duplicationUses the fewest elementsSupport the show (https://www.patreon.com/agilechuckwagon)

This episode talks about Christopher Avery's Responsibility Process that each person goes through with something goes wrong. It contains the steps of denial, lay blame, justify, shame, obligation, quit, and responsibility. Compare it with a previous episode on the Accountability Ladder.Support the show (https://www.patreon.com/agilechuckwagon)

In this episode, Chuck talks about the Trust Equation by Charles Green. In it, trust is the sum of credibility, reliability, and intimacy, divided by self-orientation.Support the show (https://www.patreon.com/agilechuckwagon)