The engineers know the project is in terrible trouble, but the executives think it's going great. This "greenshifting" anti-pattern occurs at NASA, software companies, and everywhere in between. We tell a few related stories, including a fable, and suggest methods that might work to counteract the greenshifting tendency in your organisation.

SHOW LINKS: - "The Mushroom Song" by Steve Savitsky: http://steve.savitzky.net/Songs/mushroom/

  • The SNAFU Principle (communication fable) from the Jargon File: http://skeptictank.org/files//cowtext/jargn10.htm

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

  • Scott Ambler on Greenshifting: https://www.drdobbs.com/dr-dobbs-agile-newsletter/191600661

  • Alistair Cockburn on information radiators: http://www.informit.com/articles/article.aspx?p=24486&ranMID=24808

  • Brian Marick on lava lamps as build status indicators: https://gist.github.com/marick/3ec112bc38b2af267e15


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