Tag Info

Hot answers tagged

27

Short answer is "everyone" - as was pointed out in other responses. For the long answer, I'll refer to an article I wrote recently on this exact subject, The One That Got Away.


20

I'm not sure what you mean by "responsible" in this context? who should get yelled at who should be fired who should get demerits on their next annual review who should take action to cure the problem something else Clearly both the developer(s) and tester(s), and almost certainly others, should be concerned whenever a defect escapes into production. ...


19

it makes the higher ups really happy to see results, and the winning QA members get lunch. Since you have set the system up so that there are "winners" and "losers" based on bug count, it's not much of a surprise that testers are trying to find a way to win. You are focusing on the wrong goal. You have basically told them that the goal is not improved ...


14

The whole team regardless of responsibilities should shoulder the blame. It is not a "test escape" but a "team escape". Testing is not only a department, it is also a discipline that everyone in the team should be involved in.


11

Bug hunts should be fun and productive for the entire team, and a little professional competition can go a long way to improve moral of the entire team and help them grow. This is a rare case that I slightly disagree with Joe. I also like the idea of a point system. But would expand to include: Everyone is involved in the bug hunt; not just testers. ...


10

There are several things that you need to remember before starting this task: You do not want to measure just for the sake of measurement; instead, you want to achieve a clearer view of what you have (or do) and how can you make it happen better. You do not want to for your team nor their performance to be only driven by improving the measured results, for ...


9

What value is "yesterday, today, blocking" to this team of testers? Presumably they have similar scrums where they present the same information to the functional team they are assigned to. So you may be asking them to repeat what they have just said, or will soon say. Perhaps you instead want to focus your meeting on "what is important for other testers ...


8

My perspective is - This question is more related to identifying charter / vision for the team based on current state of the Team You have to assess your current test process, tools, bugs, automation, product quality to arrive at areas of improvements Your proposal for roadmap would cover below aspects Roadmap for Team Team should have a roadmap to ...


8

Eduard, welcome to SQA. I will assume you are that developer. I think there are a lot of ways a developer can help a QA team. The most obvious way to help would be to write automated tests or to write tools that make testing easier, e.g. creating test data or automating a deployment. You may have skills outside of coding that would also benefit your ...


7

As said, everyone. This is why postmortems are important and valuable, as well as high-communication environments where people feel comfortable taking responsibility for problems without being afraid of blame. Get everyone who might have had a chance to eliminate this issue - management, PMs, developers, testers, business owners, and so forth into a room. ...


7

First off, everything I say here should be checked against your job description - that's going to tell you what your employer expects of you. As a lead, you probably don't have hire/fire responsibility (that usually goes with the manager title), so your employer's expectations will probably fall into these areas: resource management - making sure that ...


6

I think your question assumes the positions are mutually exclusive, but I've worked places where we had a per-project lead and a cross-project manager. I think the tradeoffs are the same as between a dev manager and a dev lead. You need leaders in a team for mentoring, more difficult work, and technical direction. Somewhere in the organization you need a ...


6

A developer can be also useful to QA team in defect isolation. Having skills to read the code, understand the architecture of the system and debug a running program, you will be able to isolate the root cause of the defect you or the rest of your QA team has found. It is often faster to reproduce and isolate the issue, when you are performing the tests and ...


6

I seldom worry about individual titles and even less about department names. My team is called Quality Assurance. Nobody in my company actually thinks we assure quality.


6

The testing team I'm on finally got everyone to start calling us "testers" and "testing" instead of "QA". We're organizationally a separate team from development, but de facto we work as a whole team together. Testers often pair with programmers, and programmers often do testing. It's true that as testers we do a huge variety of activities, and some people ...


5

My personal preference is to share resources across features and even products. While working on a single feature or product does increase specializing, that in itself has some associated cons: If the person specializing in a feature has missed something important and everyone else is not familiar enough with what they are doing to notice it, that could ...


5

Before you attempt to implement a metrics program, I strongly urge you to read "Measuring and Managing Performance in Organizations" by Robert D. Austin. You owe it to your team and to yourself to learn about the people-related aspects of measurement systems, and how "measurement dysfunction" occurs. And you may learn about the appropriate level of ...


5

I'm quite happy to be called a tester and though a lone gun would also be happy to be a test team If other people think 'testing' is demeaning or lowly then educate them into exactly what you do And depends on your definition of 'testing' - see this post from Alan Page for example - http://angryweasel.com/blog/?p=298


5

For several months I was testing for a company in the US. What helped? Having a regular Skype call to talk to the team A social network - we use Yammer - to help interactions that are not always work related so you can build up a picture of each other as individuals Occasional face-to-face meetings, I had a couple of visits to the US office and putting ...


4

I designed and developed training for MS for about 10 years. The most successful approach I found was to Perform a business needs analysis - many businesses have required compentencies or skills for people in different job functions at different stages in their careers. Even smaller companies likely have a set of expectations, and expected level of ...


4

Both can work, and as you point out, both have pros and cons. I am currently in a situation where we have insufficient people to be able to dedicate them to any project(s). The juggling between projects is constant, and starting to wear me down. Each day seems like "so which projects do I have to disappoint today?" If the projects themselves can be ...


4

Where I work, which has a very enlightened approach to QA/Dev, we actually have a report that details every bug found at customer sites, why it was missed in QA and what steps are being taken to ensure that similar bugs will not be missed. We understand that everyone is human. If we expect developers to occasionally wirte a bug into the code, we should ...


4

The deliverable is information about the system. The purpose is to help people make better decisions, based on information about the system.


4

@user246 has some good options - the first that came to mind for me as well was the creation of automation and support tools. I think that another area where many test teams that I've been on could benefit is from having a deeper understanding of the system architecture and technologies. A developer has a different perspective on the system - they have more ...


4

There are a number of systems that can handle this. I'm familiar with Test Link and TFS, both of which have APIs (although the TFS API is a little challenging - speaking as someone who's worked out how to post test results to TFS through the API) and both of which have ways to handle test cases that need to change. A lot depends on your budget - Test Link ...


3

All of the above... The developer is responsible for writing buggy code The tester is responsible for not finding the issue Depending on who asks the question, and the purpose and meaning of "responsible" you can get a better answer using root cause analysis of the test-escape. The tester missed the bug either by not testing it (coverage not good ...


3

Scott, Tester performance isn't something that you can measure easily. There are too many other dependencies. Some examples: If you go with number of bugs opened/closed/whatever that's highly dependent on the quality of the material each person is testing. Someone who's got a load of fertilizer will open a lot of bugs quickly and close them quickly ...


3

I'm with Joe on this one. When there's a reward only for the "best" - no matter how that "best" is determined, there's an immediate temptation to game the system and an incentive to undermine teamwork. I'd look towards a more group-oriented arrangement, one that doesn't necessarily reward the number of bugs found (the last thing you want is people ...


3

Given that a scrum meeting should be really quick, how much support will this actually give the testers ! Why are you calling it a scrum, can't it just be a meeting ? Also, if you are 'managing' the testers then it seems to more of a meeting than a self-organized scrum.... Not saying your idea is wrong, not sure that calling it a scrum is the best ...


3

Even though an answer was already accepted I felt to offer another perspective: You should not run a scrum for the testers only. Effective scrum teams rely on their ability to self govern and self organize. So each team will handle things in their own way. If a tester has an issue, he/she should bring it to the scrum master and work it out in the team. ...



Only top voted, non community-wiki answers of a minimum length are eligible