Welcome back to another day at www.implementingscrum.com.As a Scrum Master, you may have the opportunity to work with multiple teams as time goes on.

This can be a fun and exciting time because sometimes you may work with a team long enough that coaching the same team may get boring – especially if the team is just moving along and being productive (smile).

One of the things I like to chat about with an existing ScrumMaster is the concept of being able to move from “zero to sixty” within and among Scrum Teams.

What does this mean?

Scrum is a change.

Some may consider it an organizational change (a topic for the future!).

As a ScrumMaster, you are an agent of change.

When you are working on a Scrum Team, the team goes through the normal team “stuff” that teams go through to become a cohesive unit. Things and people mesh. Inside jokes prevail. Little things become normal, and sometimes people can start finishing another team members sentences or thoughts.

Then….

The team finishes a project and those people may go on to start new teams (or join existing teams). Some team members go back to traditional waterfall projects while others may have the opportunity to go to a new Scrum Team.

This story really apples to any role, be it a ScrumMaster, Product Owner, or Team Member. I do want to point out here that as a ScrumMaster, it is your responsibility to know and understand what is happening.

So.

When you go to a new team, remember this: It is a new team.

And, when you start a new team, I remind folks that they need to “start over.”

As a ScrumMaster (possibly working on one or more teams, or even a serial Scrum Master (hmmm)), you need to realize that each team you work with are in different places of their lifecycle as a team.

You need to recognize “where” the team you are working with “is” on the team formation cycle, and be able to walk into the current situation to help them along.

Team A is not Team B is not Team C.

ScrumMaster must work with all different Scrum Teams — A,B, and C.

ScrumMaster must mold and treat each team differently.

Including when you play the role of ScrumMaster and how you perform that role on each of the various teams.

And be able to go from “0 to 60″ on a daily basis if needed.

Gotta run…

Please send comments, questions, criticisms, ideas, or whatever here.

You can also enter The Forum to discuss this entry and other Scrum topics. Thank you!