Skip to main content

Company QA Community Blog

I'm thinking of creating a QA Community blog in my current workspace, you may ask why? What would be the benefits of this?

I can think of a number of immediate benefits:
- People within the Community will be more aware of what others are doing by their posts on there
- People can more easily learn from one another, I feel that by writing up about something, even in a blog post you learn more about it yourself, and the people reading the blog post will also learn from it
- It will encourage people who possibly hadn't thought about having their own blog to get involved and contribute

There are also benefits for the wider community in that:
- People will read it, and hopefully contribute to it outside of asos and offer insights into what might work better etc.
- People will read it and want to be a part of it, and thus make the company a more attractive place to work

The biggest hurdle I think will be actually getting people to contribute to it, once it is up and running however I will be sure to share it on here, so everyone can look at it! There's also the problem with the content being the view of the QA member who is posting it and not of the bigger company, but that can easily be avoided.

Does anyone else have a company QA Blog? Any advice on getting it to work and be adopted?

Comments

  1. Hi Gareth

    Our company have something like this already set up. Get in touch with me via twitter (@steveo1967) and I can then provide some contact details so we can discuss this in more detail.

    ReplyDelete
  2. We did internal setup a OSQA server (http://www.osqa.net/) as our knowledge 'database', To make people contribute to it, all our internal releases of the software is announced with a mail. In that mail we also mention each time the link to the OSQA server, so that our collegues are aware of it. Of course we also had some kind of presentation of the usage after rolling out that server a few years ago.

    ReplyDelete
  3. . I just wrote an incredibly long comment but after I clicked submit my comment didn't show up. Grrrr... well I'm not writing all that over again top digital marketing agencies

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...

QA is Awesome!

No real point to this post other than I have had the song stuck in my head and figured I could change it slightly and quite easily make QA is Awesome! Oh and I haven't even seen the movie all the way through! But for some reason that song is incredibly catchy! Not much point to this post in fact, just thought I'd put it out there :)

What we (Asos Testers) are working towards this year...

At Asos we have a large testing team (30+ testers), they all work within their development teams, and the way development teams work can vary and understandably so. Helping the 30+ testers we have a number of Test Leads, of which I am one, recently we (the leads) all got together to come up with a plan of things that we feel we need to work on/define/have an idea of how to approach them for the next year to help improve our testing standards across the boards and improve the skillset of testers within the teams. To help with this we got together and came up with a mindmap, the plan going forward is for us to take ownership of one of the areas and come up with a strategy/approach/implement actions to help improve the areas and define whatever is needed. There's a lot there, and I'll probably write seperately about each one, and what we're doing, as it's always good to share ideas and get feedback... so watch this space!