While working with an organization in their Agile transition, Julie and colleagues recommended that they start with Kanban. Kanban would bring minimal disruption to the teams, and enable them to learn what Agile would mean in their context. However, there was a lot more to do before the teams were able to run a Kanban flow and start learning what Agile meant for them. In this episode, we explore not only how to introduce Kanban, but also what to consider when bringing Agile to a group of teams that are new to Agile.
About Julie Wyman
Julie Wyman has been working with Agile teams for over a decade and is continuously learning with and from them. She’s based just outside Washington, D.C., but has had the pleasure of supporting teams distributed across the globe and even experienced her own Agile takeaways all the way in Antarctica.
I’ve been working on a collection of great blog posts about the Scrum Master role. If you have a favorite article on the Scrum Master role, or it’s goals and responsibilities, let me know by submitting it here: https://bit.ly/TheBestScrumMasterBlogPosts2020
What’s a “working agreement”, Vasco? Good question! As a Scrum Master, one of the things I worry about is if the team members are aware of the (often implicit) agreements they have with each other.
Not having a clear picture of what we have agreed to, may lead to conflict as an outcome of missed expectations. Most commonly, it leads to bugs in the software, and delays in delivery.
So, how can working agreements help reduce bugs and eliminate delays? A simple example of this might be a working agreement like: “share bad news early, even before there are any indications of delays or other consequences”
This agreement, will help the team keep in mind the need to discuss and solve problems early, before they escalate. But, as a single agreement, this would not be enough for a team to work with.
Take It To The Team: The WorkingAgreements Workshop
As a Scrum Master, I also know that the team itself will have a more complete view of the agreements they need to work well together.
I have a few ideas, and will bring those up in our “working agreements workshop”, but it’s up to the team to define and ultimately put into practice those agreements!
Jimmy defines the working agreement as capturing “the expectations we have on each other within the team when we collaborate and communicate. I’ve seen teams call it “Code of Conduct” or “Ways of Working”. I call it Working Agreement. You call it whatever makes sense for you.”