Getting your team to work like a team can often be helped by setting up some initial “rules” that everyone on the team agrees to follow. By laying the groundwork early in the formation of the team, you can avoid misunderstanding and even deliberate “misconduct” by always going back to the rules. Instead of, “No, this is how we’re supposed to do it,” you’ll be able to say, “No, we all agreed to work this way.”
Every team should create their own ground rules. If they are imposed from outside the team, they become a lot harder to enforce — the developer can just say, “Hey, I didn’t agree to do that.” So, in your very first gathering of your team, we recommend setting up some ground rules to help govern future behavior and decisions. While you want your team to come up with these rules, here are some good ideas to include on the list:
- We all agree to follow Scrum as defined in the Scrum Guide.
- If I don’t want to be on the team, I will take steps with management to get removed from the team (the “escape clause”).
- We will, to the best of our abilities, be on time for, and participate in, all team events (e.g., Sprint Planning, Daily Scrums).
- We agree to support team decisions, even if we disagree with those decisions.
- Make sure everyone gets heard.
- Stay focused on the Sprint Goal.
- Don’t say, “no,” say “Sure, add it to the Product Backlog and let the Product Owner prioritize.”
This short list can get you started, but make sure it’s the team that creates the list — don’t impose it on them.
More About #TransitioningToScrum
Agile Transformations – Is It All-Or-Nothing?
Wondering where to start with agile transformation? Do you pick a single project? Or a specific team? Train everyone and run with it? Here's some guidance.
Leading the Way to Organizational Change
As a ScrumMaster and organizational change advocate, here's 7 things you can do to help your organization embrace change as a normal way of life.
What Causes Conflict on a Team?
Change usually creates conflict, but a good ScrumMaster knows what types of conflict to expect and is prepared to handle it with correct conflict responses.
It’s All About Value
One small change can make a BIG difference to your Product Owner success. Before worrying about putting value on backlog items, here's some simple tips.
What Does it Mean to BE Agile?
With the Agility mindset, it's critical to understand the concept of "being" Agile. Some people want "to do Agile", but you don't DO Agile, you must BE Agile.
Should Scrum Teams be Dedicated to a Single Product?
Should Scrum teams be dedicated to a single product? The truth is, there's times when you want a dedicated team and times when you don't. Let me explain!
Creating the Skills You Need for Agility
When beginning the transformation to Agile Development, it's hard to know exactly what skills the organization needs to adapt to the new way of working.
What is the Role of the ScrumMaster?
Although the Scrum Guide defines the ScrumMaster at length, here we're going to dissect that description and take a much closer look at what a ScrumMaster is.
What Do Testers REALLY Do On a Scrum Team?
Analysis, design, coding, and testing are done constantly rather than in phases, meaning testing ISN'T just a phase but an ongoing part of Agile Development.
Leave A Comment