AB Testing – Episode 84: Stories about Changes and Nets

On to Principle number 3 (full list at moderntesting.org).

We are a force for continuous improvement, helping the team adapt and optimize in order to succeed, rather than providing a safety net to catch failures.

As promised in the show, there will be an AMA on Modern Testing hosted by Ministry of Test on July 10. Register Here.

AB Testing – Episode 83: Accelerating the Team

We’re back to the MT Principle Deep-Dives (which may just be medium dives).

Principle #2 says:
We accelerate the team, and use models like Lean Thinking and the Theory of Constraints to help identify, prioritize and mitigate bottlenecks from the system.

We talk about that – but of course, there are a few tangents we hope you enjoy.

Finally – apologies to everyone who had their AB Testing RSS feed reset over the weekend. We moved the web host for angryweasel.com (notice that the site now has a valid RSS cert), and the RSS reset was an unexpected casualty of the move.

AB Testing – Episode 82: Brent Talks to Alan About Data

We are already taking an interlude from principle deep-dives to reflect a bit on the episode 81 feedback, and for Brent and Alan to have short (but in depth) discussion on how to get started creating actionable metrics.

We’ll be back to Modern Testing principles in episode 83.

AB Testing – Episode 78: Digging in on Modern Testing Principles

We don’t reiterate the Principles directly (see the Episode 77 show notes for that), we talk a lot about how we are adapting the principles slightly based on feedback and discussions with the three – and how much better the principles are for the effort.

We also discover that both Brent and Alan love to cook. Or at least they both finally realize that each other likes to cook.

AB Testing – Episode 77: The Conception of the Modern Testing Principles

We discuss, vet, and rewrite (and not for the last time), the Modern Testing Principles. These are a work in progress, but we’re happy to share the current final form.

Listen to the podcast to hear these developed in real time.

  1. The customer is the only one suitable to judge and evaluate the quality of our software
  2. We apply the theory of constraints to identify, prioritize and mitigate bottlenecks from the system (and accelerate the team).
  3. We are not the safety net for software correctness – we focus on improving the business, and not the code.
  4. We are responsible for the quality culture of our team, and are accountable for helping and coaching the team in this regard.
  5. We use data to deeply understand customer usage and customer pain.
  6. Embrace continuous improvement, and help the team adapt and optimize in order to solve customer pain
  7. We strive to reduce or eliminate the need for a dedicated testing specialist on our teams by increasing testing abilities and knowhow across the team.