We continue our mini-series on how to learn by considering ways to realise your learning - that is, how to convert what you've learnt (say, from a retrospective) into changed behaviour. We discuss how and why to create pre-planned actions in response to situations where you'd like to do better, for instance software outages or suspiciously optimistic delivery dates.

SHOW LINKS:

- Feynman on the Challenger disaster: https://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt

- Reg Revans, Action Learning: https://www.brookes.ac.uk/services/ocsld/resources/theories.html#action

- Helicopter pilot story: https://www.verticalmag.com/features/ejection-decision/

- Ejection Decision: https://www.youtube.com/watch?v=Aa1Ba_NEobs

***

We'd love to hear any thoughts, ideas, or feedback you have about the show.

Email us: see link on troubleshootingagile.com

Tweet us: twitter.com/TShootingAgile

Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

Ways to Learn Continued: Pre-Planned Actions

Troubleshooting Agile is a problem-solving session for agile teams. Jeffrey Fredrick and Douglas Squirrel look at common problems agile teams face and provide practical, immediately useful advice for getting back on track.