But I always test every release.
It's important as a manager to keep your hand in, to stay involved with the actual work your employees do.
There are a lot of advantages to making sure you're still a tester, just like you're also a manager:
- Timeliness. If you can still test, you can be the hands that help your team through a crisis. If you're the one who caused that crisis by overpromising or misestimating, this is particularly important - you broke it, you darn well better help fix it. Even if the crisis is externally driven, your testing can make sure that your team still comes in on time and with the level of testing you need.
- Respect. Your team will respect someone who can walk in their shoes, who understands the ins and outs of testing. This is why I'm not a big fan of having a manager come in with no test experience. They don't have to have been a tester, but they need to have worked very closely with testers.
- BS Meter. You hope this never happens, but sometimes one of your team members will try to lead you astray. Often this is saying something was tested when it wasn't thorough enough, or overestimating how long a test will take. If you still test, your skills and instincts will be fresh enough that you can call them on it.
- Keep Current. Testing, like all software engineering, changes fast. The techniques, the tools, the languages, the sensitivities of the systems under test: all that will be different in two years. The best way to keep up is to keep testing.
There are some disadvantages to being a tester manager, however:
- Longer Hours. Keep in mind that testing is on top of managing your team, not instead of. You'll find yourself doing most of your testing off hours.
- Bailouts. If your team feels like you'll bail them out to make a deadline, they may decide to let you. Make sure that you're not letting them slack off while you do their work for them.
All in all, I prefer to be a manager who still tests, not just a manager.