... for roughly 18 months now, and quite successful at least in the aspect that people working for me kept telling that they are quite happy with how I do things compared to what was before I took over. So far, so good. I'm still not dead. ;)
Main lessons I learned:
* Learn to delegate. Fast. Don't ever ever do things yourself (speaking about solving tech issues). If you have worked with the same people before, they will frown at you for not "working" anymore for roughly 3-6 months. Ignore it. Justify it. If you are good at keeping their backs free, they will see why you do it. Reason: if you do things yourself (meaning: tech solutions), you will have to fix them. Everybody will play the "he did that" game, and you will drown. Even if you want to support the guys, help out... don't. As much as possible.
* Be rightful, honest, truthful. Never hide your own mistakes or gains from anybody. People will see, and learn to be truthful to you - because of respect, as opposed to be afraid. You need to know what's going on in your team, so this is a key part!
In other words: be the *good* guy. In every respect. Taking blame, and hand down compliments as well as negative stuff.
That will lead to people standing behind you when things get ugly, and they WILL get ugly at some point, because you are responsible for whatever goes wrong. Things have a tendency to go wrong.
* Trust is earned, not given away. You need to earn the trust of your guys as well as the big hats!
* And while taking about it, possibly the worse part, which is dealing with bosses: basically, the same rules apply. Be rightful, truthful, and try to justify things on reasoning, not emotions. Try to think FOR your people, not against them. Never blame something on a person. It's your fault for not forseeing this could happen. Keep in mind that you will suffer when your people loose faith, because you can't deliver without them. Watch out for structural issues in the company that will keep you from delivering; say, you don't have a QA department at hand or miss critical infrastructure. There goes your capability to deliver. It's about keeping those things in mind.
* Development methods don't matter. Structure does. Wrap your team around your issues, not vise versa.
* Oh, and I always wear heavy motorcycle boots, just in case somebody needs some kicking.