I would agree with a lot of the people that have already replied, it's not everything but it's not nothing either. Right now I have a MCTS in Web Applications 2.0. I did learn somethings that I used the next day at work and I've learned things I'll probably never use again. If you go into it with a positive attitude you'll get something out of it. As for the future job prospects, some replies said it doesn't matter but I disagree. While I wouldn't hire someone based on cert or no cert, seeing anything on a resume that shows you have some commitment to your field isn't a bad idea. Whether it's a certification, user group, advanced degree, etc. your willingness to be more then a clock puncher improves your standing. My recommendations: 1. Take the first test before discussing the negatives with your boss. It will help your arguments to say "I got a 95% on the test but it doesn't cover anything practical". That way he can see you know your stuff, both from the test and critical thinking about the test. Plus you might be suprised by the test, like it, and want to take more. The best argument is one you don't have. 2. Get it on the project plan now. The impact to you and your boss will be quickly apparent. Even if you still need to work 40 hours per week on the project and the study time is "overtime", getting your boss to see what you are doing will help with seeing the effort you are putting in. Saying go take a few tests sounds trivial, but seeing 10 hours per week studying for 6 months (just and example, your mileage may vary) looks like a sub-project.