Most organizations today have tried Agile approaches and the majority are finding them helpful. There are a significant number of people for whom Agile has not been helpful or it hasn’t worked. Or, they tried it but they did not get the benefits that they had hoped they would get. When I peel back the onion, I hear some of the same reasons for Agile not working.
Being a Scrum Master or Agile Coach is a challenging job! We've created this page to help you to grow so that you can improve the productivity and effectiveness of your team. Whether it is deepening your understanding of the rules of Scrum, improving your ability to lead scrum events skillfully, or simply hearing stories about coaching that didn't work, we hope you will find the resources on this page useful.
I always thought that crew looked like a cool sport and I've admired crew teams. In crew, team members in lightweight boats race to go as fast as possible. It is hard work! I think the crew team is a useful metaphor for Scrum teams.
Crew teams strive for speed so they keep everything as light as possible by eliminating anything heavy or unecessary. The more strong people that are rowing, relative to the weight of the boat and everything on it, the faster the boat will go.
Looking for resources to help you succeed with Agile or make the transition to Scrum? You’ve come to the right place. Bookmark this guide and leverage it for all questions you have related to Agile Pilots, Training, and Transformation.
Whether you are just beginning to learn about Agile and Scrum and need guidance on best strategies for an Agile pilot, or a seasoned Agile Leader who is looking to create high-performing teams, we have tips, plans and strategies to help you avoid pitfalls and ultimately succeed with Agile and Scrum.
I work with a lot of teams and help them to adopt Agile thinking and methods. While I am pretty passionate about Agile and many of the team members are as well, I work with many team members who are afraid of Agile. Why would people fear Agile if it is such a great thing? Perhaps it isn't viewed as such a great thing by everyone. Here are some reasons why they might fear agile and 'being Agile'.
#1 Change of Any Type is Difficult
Have you ever wondered how to undermine change and thwart progress in organizations? One of my agile coaching colleagues recently shared a link to the Simple Sabotage Field Manual, a document published during WWII by the Strategic Services, the precursor to the CIA. It makes for entertaining reading, in particular, section (11) General Interference with Organizations and Production.
A few years back my son was playing as the catcher for his high school baseball team. There had just been a close play at first base, and my son was picking up the bat for the opposing team and returning it to their dugout. It seemed like a nice thing to do, so I was surprised and won't soon forget when his coach yelled out "Hey Mersino, you're not their bat boy". The point the coach was making was that it was not my sons job to pick up the bat, he had more important things to do and focus on.
A key part of an Agile Transformation for an organization is forming the development teams. The starting point for most organizations is typically a functional organization such as developers, business analysts, and testers who report to their respective managers. It is common for each person to be assigned to multiple projects. So how do we go from that to having dedicated team members on cross-functional teams?
This is part two in my series of posts about improving your retrospectives. As I mentioned in my previous post, the point of the retrospective is to help the team to make their processes and practices more effective and enjoyable. This post focuses on the first part of the retrospective where we set the stage for the rest of the retrospective meeting.