Hiccupps

  What I particularly like about Lean Coffee are the timeboxes. At Agile in the Ether yesterday it was an hour for the whole event and just eight minutes per topic. At that level, the investment is low and the potential returns are high: some ideas for right-now problems and background for those that will surely come later. On top of that, the possibility that I can share something that will be a win for someone else. Here's my notes aggregated from the conversations. Ideas for agile coaching teams when you're in there on a very ad hoc basis. How to not disturb but still bring a value. Is it possible? The teams are typically overconstrained which makes change difficult. It's common for the coach to suggest an approach but not return for a couple of iterations. They don't know whether it landed. Can you build a relationship with someone in the team and have close communication with them to get the feedback? Ideally this would be with someone who cares about improvements...

After hearing good things about it for years, and failing to get one of the limited spots at its lean coffee events for almost as long, I was excited to finally be at Agile in the Ether last week . Here's a few aggregated notes from the excellent conversation.  How to encourage non-digital stakeholders to understand the value of discovery and outcomes over outputs? The business has scaled quickly and is large and stakeholders just want features They don't talk about problems and give people space to offer solutions Help them to think about how they experience the world outside work Lay out the risks/benefits of switching to incremental devlopment Get an ally who is respected (by them) to support your case Show business which haven't adapted, e.g. Blockbuster Show business which have adapted, e.g. McDonalds Let stakeholders observe interviews with users to understand their prioritie...