Skip to main content

The Importance of Building a Good Community of Practice

Within every organisation i think we can all agree that 'collaboration' is a major factor to the success of any project or initiative.

As organisations grow, new teams are created and existing teams fragment from each other, this is natural and i doubt that will change.

So what impact does that have to an organisation?
  • Stress in the work place? 
  • Unmet expectations? 
  • Relationship breakdown? 
  • Low Morale? 
  • Dissatisfied Clients?
Collateral damage is inevitable.

When clients are dissatisfied, they often take their business elsewhere, which costs your company money. Poor communication can lead to high employee turnover, which creates a cost of hiring and training for new positions. At the least, with lower productivity and an unclear sense of purpose, poor communication causes employers to pay for work hours that are not efficiently spent, costing money, affecting efficiency, and keeping employees from reaching their true potential.

Its sometimes difficult to work on projects where you/your team(s) are not responsible for the entire big picture, this is the situation i am currently in.

There are around 70/80 product teams across 7 delivery centres working on our super huge platform, each team responsible for a very small part of that overall picture.

Without cross team collaboration we are setting ourselves up for a huge failure, Right?

Across the centres we use Slack with great anger... many many channels all serving a different purpose. Useful yes, but this shouldn't be the only form of communication.

I am a great believer in that building a good community for testers but not exclusively for testers is not only a a good thing, but the right thing to do to close the gaps created as an organisation grows. A community of practice is a group of people (Multi-discipline) with a common interest, a common goal of improvement and sharing ideas and should be lead but the whole community not one individual.

Earlier this year in the delivery centre that i am located i kicked this off with a brainstorming session to understand what output people would like from regular sessions/workshops. 

There appeared to be a great appetite for this, we initially agreed a regular meet once a month and all agree that fortnightly would become too onerous and interest would soon dip, as you would agree we need to keep these sessions productive… This of course doesn't mean we have to wait to share useful information, additional sessions can be arranged. the regular meeting is to ensure we keep these going.

The brainstorming session we had raised exactly what i want the sessions to be about:
  • Knowledge/Ideas sharing
  • Pain sharing/Problem solving
  • Self development/Learning from each other
  • Demos/mini talks
  • Proof of Concepts
  • Encouraging/Enhancing best practices
  • Support/Coaching/Mentoring
  • Breaking silos/meeting & working with new people
Id love to hear what others are doing regarding communities, how engaged are your teams? are they productive and providing benefit?

If this is new to your organisation... give it a go! GET TALKING :-)

Emily Webber wrote a great book which is definitely worth a read:


Popular posts from this blog

My Testbash Brighton 2017 Notes

This was my second Testbash... if you ever get the chance in the future these conferences are a must!
I took copious amounts of notes from the 9 talks and tried to highlight my key takeaways here... hope they make sense but please comment if you have any questions :-)
Amy Phillips - Continuous Delivery
A survival guide to joining a fast paced environment/project…
Where does testing fit within Continuous delivery:

As highlighted, basically from start to finish…
There are lots of things we can do when joining a project that is using Continuous Delivery but one of the main points from this talk was to do your research! There should be an element of "Continuous" in every aspect of the project.
·Learning the ling, what's the difference Continuous Delivery, Continuous Deployment, Continuous Integration, Continuous design, Continuous Improvements etc.? ·Understand what your role in the project is going to be ·Understand the teams values, What's going well and maybe what the team p…

Is TestBash an Invaluable experience?

Over the last few years, I’ve attended four single track conferences at TestBash Brighton and Manchester. Most recently, September 2018 and April 2019.

One of the most common questions I get after the conference is, Was it worth it? Especially now given, I’m a contractor, and I attend at my own expense.

In short, Yes It’s definitely worth the trip!

That leads me into my question; does a single-track conference work for me, or could I get more out of TestBash?

Of course, there are pros and cons, some talks may not be as engaging, but this is no disrespect to the speakers, for me, it’s because I probably favour certain subjects and I’m pretty sure others will think the same.

Do I make the most of what’s on offer at TestBash? It pains me to say, No! I don’t make the most of the events leading up to and post the single-track conference so I could get more from the week.

TestBash offers master classes on automation. A full day of workshops. Test.bash() with talks on automation and technica…

The way we work shouldn’t be ‘Alien’ anymore, Should it!?!?

It’s been a good while since I have written anything (Mainly because I’m not that good a writer) but given my 16 months in the public sector I thought it was time… 
For a good number of years now the DevOps trend has given rise of buzzwords and methods aiming to speed delivery and it’s now an assumption of mine that most organisations are au fait with the term ‘Continuous Delivery’.
I was wrong…
Within the organisation that I am currently placed I believe I have a high-functioning collaborative team who work flexibly and in continuous cycle. We also involve the users which is a huge benefit to the development teams, but that’s not saying we get everything right 100% of the time! Teams must continue to learn and evolve to remain productive.
Our team work in one of several delivery groups and with this comes multiple challenges; Silos No single environment strategy lack of communicationsVaried ways of working.  And thats just to name a few, which is interesting when all delivery groups …