PDCA is a model for structured problem-solving

Plan Do Check Act
  • Plan: Expressing our model of reality that leads us to believe a particular action, or set of actions, will have a desired effect. NOTE: this is not just blindly proposing a change;
  • Do: Taking, or attempting to take, action;
  • Check: Reflecting upon the effect of action(s), including on any problems with implementation. NOTE: this is not just measuring results with no reflection;
  • Act: Take appropriate action in response to our reflection, whether validation of our model of reality and capturing this in standards, or adjustment of our model of reality.

PDCA is a false, but useful model to avoid common errors

What would Extreme Programming (aka dials to 11) look like if it was invented today?

Summary of the answers

Harder to rely on role modeled behaviour for unwritten rules when remote

Distribute decision-making with context and decision rules


Replacing accidental with intentional.

Communication capability = communication habits + what you get for free by being co-located

Replace implicit, non-verbal cues with explicit communication and intent

  • Collaboration: “two teams work together on a shared goal, particularly during discovery of new technology or approaches”;
  • X-as-a-Service: “one team consumes something provided by another team (such as an API, a tool, or a full software product)”;
  • Facilitating: “one team (usually an enabling team) facilitates another team in learning or adopting a new approach.”
  • Consult to Not Own: Asynchronous support and review for another team that will eventually own the results of an effort;
  • Consult to Own: Asynchronous support and…

Guilds solve two problems

Guilds have three kinds of activities

Logical structure

  1. Create a collection template, that is, predefine the categories you’ll use to organise;
  2. Dump your thoughts out first without categorising;
  3. Sort the thoughts into your collection template;
  4. Organise the thoughts in each category to create a better narrative flow;
  5. Refine to create your first overall draft.

Some individual productivity practices translate well to team productivity

  • Increasing focus, by reducing multi-tasking and interruption;
  • Frequent customer feedback, via regular demos, user testing, releasing to early adopters, etc.;
  • Reducing friction. For teams, this is typically around lack of clarity of direction, lack of agreement on how to work together, clunky tooling and/or technology, etc.
  • Watching the work product, not the workers;
  • Frequent integration

Watch the work product, not the workers

  1. Increasing focus (reducing multitasking, reducing interruption);
  2. Frequent customer feedback;
  3. Reducing friction.

Multitasking feels more responsive and is guaranteed to slow completion times

4 new requests… how should you respond?

Jason Yip

Senior Agile Coach at Spotify, ex-ThoughtWorks, ex-CruiseControl

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store