Community Blog

There are loads of blog posts, articles and podcasts about agile - what it should be, what it should do, how it should look? The problem is that a lot of what’s out there is hypothetical and not based on field experience.

The term organizational agility is everywhere these days, but what does it really mean? Can we even define it at all? Deepen your understanding of the manifesto and why it is essential to implementing healthy agile that delivers meaningful value.

In my 100th episode of Agile.FM,  I had the opportunity to speak with Jim Benson, the co-creator of Lean Coffee.

Many thanks to attendees at my PAL-E workshop in London on 26-27 October who reviewed & debugged my change story for "what is organizational agility?"

I'd like to share another story with you... Thank you Paul and Charlie for sharing your story. It moved me and left me with huge smile on my face. 

I have my own biases,  having seen co-located teams work very well and having struggled with “dislocated” teams, I often recommend my clients to reconsider “dislocated” teams. 

The Scrum framework thrives on empirical process control. The inspection of observable results gives us insights in what might be most valuable next, always acknowledging that the future is unwritten.

  With the holiday season in full gear, many of us start crafting one or more New Year’s resolutions:

In 1995, the first codified version of Scrum was made public.

Collaboration is the key to successful agile product development. A community of practice is a technique that helps us achieve this.