5 Steps to Creating an Agile Community of Practice to Make Your Teams Awesome!

The definition of an Agile Community of Practice (CoP) is a group of people who share a passion for agile such as Agile Coaches who formally hold an agile title or agile champions, who are affiliated with agile due to their interest or knowledge.  

The volunteer members of the Community of Practice regularly come together to share domain knowledge about their agile expertise. This is an excellent way to enhance learning of individuals and teams, create opportunities for coaching and mentorship, and to help identify knowledge gaps across teams. 

Most importantly, it’s great for establishing a sense of fellowship which can help to promote morale and productivity!

Unfortunately, while many organizations see the value of embedding Agile Coaches in their organization to help with transformation efforts, most organizations don’t feel the need to sponsor a formal Agile Community of Practice which means they typically don’t exist. This shouldn’t prevent a group of people from establishing one through a grassroots effort. 

If you find yourself in an organization where the “mothership” (as one member of the TacTec team describes a Community of Practice) doesn’t exist and you want to get one started, here are 5 easy steps. 

1. Prepare your Pitch by Writing a Purpose

Having an Agile Community of Practice is a grand idea but you will need to build a membership so start by “preparing your pitch”. 

Write a draft purpose statement. It doesn’t have to be perfect, because it will be updated once you build your core membership. However, having a general idea of a purpose can help you to create some buzz about joining. 

Using a “Team Purpose Canvas” is a great way to get inspiration.

2. Recruit the People!

Once there is a draft purpose created, you need to identify people who will be the Community’s first members! 

Speaking with your immediate peer group is an easy recruitment effort. Start by speaking with those who you already know but be sure to reach far and wide to find those that could benefit from being part of the “mothership”. 

Agile Coaches are usually not part of a centralized office so you may need to do some investigative work to find them and be prepared for a plot twist as you may find that an Agile Community of Practice already exists! 

TacTec Insider Tip: We would recommend starting with people who are formally in an Agile Coaching role then open up membership to Agile Champions (those who advocate for agile but are not formally responsible for transformation efforts) at a later date. 

Gather your names and invite them for an informal gathering so the draft purpose can be shared for CoP. 

Hopefully, through this conversation you are creating some interest and are getting positive vibes. At the end of this step, do you have at least 5 people who are committed to helping to launch the Community of Practice?

3. Conduct a Working Session

It’s important to create a set of working agreements and redraft the purpose for the newly forming CoP. Don’t skip these two steps!

Working agreements should cover topics such as:

  • How often will the Community meet and at what time? Don’t forget to retrospect!
  • Location?
  • Who will own the meeting invites?
  • What type of behaviors are to be expected?
  • How does the Community define success?
  • What is the optimal team size for the Community?
  • Where to store a backlog of ideas or topics?
  • How much time do members have to contribute to the CoP?

Next, review the initial draft purpose and revise as a team. 

This exercise gives all members the opportunity to contribute to the team purpose which will generate some ideas about what to cover in the first and future sessions. 

4. GO! Have your first official Community of Practice session!

Now that you have some formalities established for the newly established Agile Community of Practice, have your first “official” session!

Usually in these first sessions, the members are getting to know each other and it’s important to be mindful of the stages a team goes through such as forming, storming, norming and performing. Yes, even a team of Agile Coaches are not immune to Bruce Tuckman’s stages of development! 

After getting to know one another, the members may want to discuss practices across teams or share their own barriers to agility to see if other members have found ways to resolve. 

If the CoP still struggles with what to discuss at this first session, use a 

Lean Coffee format and allow the members to come up with topics to discuss or even actions the CoP would like to take. 

For example, does the CoP want to offer “services” to non-members? Will it build a public portal as a way to help share knowledge? There are many things a CoP can accomplish, just be sure to keep it fun, yet effective!

5. Spread the word!

If you have the ability to write a blog, write a blurb in a company newsletter or even place posters up anywhere there is space, spread the word about the new Agile Community of Practice, its purpose and some success experienced by the Community of Practice. Spread the word whenever there is an opportunity!

Drop us a comment below if you have been part of an Agile CoP! We’d love to hear about your experience!

Share this post

Notify of
Inline Feedbacks
View all comments

Ready to level up your career?

Recent Posts

Add to Waitlist

If a course has an ‘add to waitlist’ button then it is likely booked up. Spots often become available so please fill out the form below. We will be in touch within 24hrs


Born 1965, San Antonio, Texas and lives in Dallas, Tx.
Mr. James, Ronald, Maverick holds a Bachelor of Science in Psychology at The University of Texas, San Antonio.

Mr. Maverick or JR as many call him is a “slick” but warm and friendly character in our upcoming book on the DevOps Mindset. Mr. Maverick cares about his IT team very much and could charm the socks off a Texas Longhorn. JR is liked by many in his organization; however, he is not as well trusted by the Overlords as he used to be. Mr. Maverick has a group of loyal staff, including Mr. Barker a bit of an opposite to JR. Of course, Mr. Barker would never call him JR; he would only call him Mr. Maverick because well, Mr. Maverick is his boss. Mr. Maverick has held many IT positions in the past, including starting as a Sales Professional for HP and IBM mini and mainframe computers. Over the years he has risen through the ranks to hold this senior position by delivering using high-paid consultants and Big name firms. He also received his promotion from outsourcing to a foreign country where he was able to reduce his IT spend significantly. Recently he has discovered (actually this was made painfully aware to him by the Overlords) that both the Offshore roadmap and use of external consultants was not giving him the value and velocity for his IT department, and he was probably paying more than he bargained for

So, after hearing a talk at a DevOps event by the Agents of Chaos, JR decided to enlist them to help with their digital transformation roadmap and help improve the value, focus and velocity of his department. However, MR. Maverick has a few ideas about agile and DevOps, something he has heard about for a while and read in various CIO magazines; he thinks of these as Marketing terms and something that can be bought. While Mr. Maverick has held on for many years to traditional IT ways of working he has come to the end of his tenure if he doesn’t do something fast and get DevOps working quickly as he has promised to the Overlords providing him with a little more rope to get the transformation completed more quickly as they view his IT department ageing, procrastinators who are not able to keep up with business demands. JR says in his mind, “I will get it done, they don’t call me Maverick for nothing!“