What role does coaching play in the agile transformation of organisations? How do ScrumMasters and Agile Coaches use coaching? How do they differ from Coaches?
The retrospectives we ran with the tech teams became quite popular in my former company. The rest of the company got interested in running their own retrospective events, so we started running retros with marketing, social media, product launch, content team, films teams, etc. One complexity I encountered was when I was asked to run... Continue Reading →
Some years ago our teams decided to commit to increasing their Agility (coming from a background of doing Scrum), with a focus on the Agile principles and living them every day. After workshops and discussions on the principles and how we can reflect them better in our work, I experimented with a model of retrospective... Continue Reading →
I've described in a previous post why the retrospective is the most important event you will run in an agile transformation. For the retrospective to fulfill its role, it needs to be effective: it has to happen in a safe space, the team needs to look into data and generate insights based on actual information... Continue Reading →
I believe all Agile principles are equal in importance and they work together holistically: focus on customers, iterative development, self-organised teams, technical excellence, and continuous improvement. But this last principle is "more equal than the others": Continuous improvement is the heart of Agile. Without reflection, there is no learning, without learning there is no continuous... Continue Reading →
I've written about The Agile Manifesto here (values) and here (principles), with this post I will dig even more in how Agile came to be. The first notable thing to mention is that Agile didn't start with... well Agile. Many of the frameworks that sit under the Agile umbrella are more than two decades old,... Continue Reading →
After diving into the Agile Manifesto and discussing the Agile Values here, this post is entirely dedicated to the accompanying principles. Originally, the 12 principles of Agile software development were split in three categories: customer, managers, teams (see below a copy of the original manifesto), each category having four principles. I. Slanted towards Customers: The... Continue Reading →
"We must be Agile!" From C-level to any level employee, Agile is becoming more and more popular. But what do they mean by being Agile? This is what I got from asking the people around me: we have to move fast I want to see the work before it's completed I need the team to... Continue Reading →