Hot answers tagged

13

A good test manager has a number of key attributes. I tend to think that the best managers are like good, professional sports coaches. They have played "the game", at the highest levels, they know what is required to be successful and achieve the results you are after. Translated, they should be a great tester themselves and be able to test hands on if ...


11

There is no standard anything in testing. In very broad terms, all testers need to be observant and good communicators. Outside that, it depends. First, there are several broad fields of testing, including: security testing manual testing performance testing automated testing Expertise in one area is no guarantee of expertise in another. Second, ...


9

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 ...


9

There will always be bugs that get past a tester and land in production. I have even had bugs that where in my face, we researched it, thought it was a fluke, because we couldn't reproduce it and then released the issue into production. The best thing you can do is learn from it and prevent the same in the future. I write an automated test-case for each ...


8

I tend to prefer allowing anyone in any capacity to log defects on any team I am a part of. It helps build a sense of ownership of quality in the entire team, which is as it should be, every team member regardless of role should equally own and care about quality. It is a different story when people outside of the project team are entering defects, I would ...


7

Apart from obvious activities like test data creation, test case execution, bug reports...what other initiatives can a QA engineer , take which will help raise his value to the project/Client. You can only do what the situation and context permit you to do. In some shops testers get to review the Requirements before they are finalized. If that's ...


7

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

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 ...


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

Some thoughts here: how healthy is the situation where bugs are logged by project members other than the actual qa member who is the dedicated personnel for quality? This is normal - anyone can log a bug. The team decides which bugs are in scope for the project and which need to go into the main backlog. The team decides which bugs get fixed when ...


3

Anyone who has access to the application should be able to file bugs/defects. Defects should be filed in a bug tracker with a status new. New defects should be verified and extended (With at-least a reproduction path) Defect should be added at the top of the backlog (Keep a no defect policy when being Agile) Products Owners should monitor new incoming ...


3

Have you considered less competitive approaches to achieve your goals? Your teams may learn practical skills using deliberate techniques. I'm not sure how that increases morale (or team spirit), though. Note that for a deliberate technique to be effective, it must be: demanding targeted at improving specific areas of performance (so you must exactly know ...


3

Are you recommending the best/most appropriate way to test a problem? Are you thinking of scenarios or perspectives others arn't? Are you making sure you are seen as a valued asset within the team and not just a rubber stamp? What I must stress though, is that there is no "quick fix". The main thing is to build up trust and respect within the team. ...


3

Take care as it can lead to whatever metrics you are using being gamed and people concentrate on winning rather than the desired outcome...


3

I envy those organizations! First, I'd think a testing manager would need to have experience working with a testing group - not necessarily as a manager, but certainly with some level of administrative experience. I'd look for familiarity with a range of software development methodologies, particularly how the methodologies impact testers. Willingness ...


3

Suggestions: Work on your writing and communication. You've asked two questions in your post, but haven't used question marks. Ellipses have three periods. Learn the difference between its and it's. Use an active voice in your writing. Speak to people more than you email or message. Conversely, don't socialize too much or waste other people's time. Find ...


2

My personal experience is that a manager as you describe it is often not a good person to actually take the lead of a test team. They do not know enough and are (certainly less experienced ones) to easily convinced by nice powerpoints and smooth talkers instead of sound technical statements. This becomes very important at the point where you have to decide ...


2

One option is to have a Hackathon day between the different test teams. Hackathons come in many flavours and have different meanings to different people, so your test teams will need to figure out what does it mean to them? Ideally at the end of the Hackathon day, the different test teams should present (and share) their hackathon idea(s) to the other test ...


2

I would look for a leader rather than a manager. A leader who can inspire me and others on my team by sheer weight of his knowledge and work. I agree with whatever has been said by Bruce and probably some of points below might look like rephrased sentences (still I would give it a shot) One who enables the team to realize its potential by providing the ...


2

As there are many responses that present the perspective on the role of a lead vs. a manager, I am editing my answer to, hopefully, better answer your question Pros and cons of direct reporting: Direct report to manager is beneficial when .. a manager is considerably involved in the project, is aware of requirements, due dates and can be a part of team ...


2

I agree with the others, anyone should be able to enter bugs. One comment on: Especially if they are not well described with steps to reproduce? If the bugs being entered are not productive, I would invest some time those people to train them in the art of great bug writing. You just might make a great tester in the end.


2

qa_test235, I noticed that your are an unregistered user of this forum and I am not sure how this affects your ability to participate. Become a registered member of Stack Exchange and participate as you can in helping others learn about SW testing and quality engineering. This activity may seem unnecessary or maybe a burden. Over time this will add some ...


2

First and foremost, analyse how the bug got past you. Find a way of preventing this, and things like it from happening ever again. Second and maybe even more important, talk. Talk with everyone involved with getting new functionality out. As soon as requirements materialize, get your test approach on paper and scrutinize it AS A TEAM. That a harmful bug got ...


2

If you was under the threat to lose your job as a result of letting a single bug to slip to PROD, you should consider looking for a job in saner company. It is just a matter of time when another bug will slip to PROD. Quality is a team sport. Bugs will always slip, and pointing fingers and assigning blame does NOT improve quality. Firing you for a bug is ...


1

Test automation and push toward continuous delivery is slowly but surely reducing the need for manual testing. Learn BDD and other means of how to ensure developers' are writing good automated test and satisfying business needs. To go even further, learn how to write test code yourself; QA experience and knowing how to code will make you stand out from those ...


1

This is going to be a bit unpopular, but I am going to have to buck the tide on the answers so far. I agree that it is important to allow everyone to submit potential defects and that system should be as clear, helpful, and accessible as possible. However, I have found that it is important to separate the "official" bug list that the team is working from the ...


1

Organisations & events You can earn it for your organization in different levels. Recognition you can get having the business partnership with testing tool companies. ISO 9001 good one. Affiliation with university. Affiliation with testing organisations & participate in events.


1

I'm not sure where you are based out of, but you could look into the ISO90001 in Europe. It is a quality management certification that applies to companies: http://www.iso9001.com/


1

I worked recently on a matrix for my team and found it to be a great exercise to refine my thoughts on testing. Here is an example topic, Defect Management. Here are a couple of images of the Skill Matrix I developed and mentioned above: My matrix covers the following areas. You may want to add or remove to suit. A great test matrix covers all the ...



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