It's interesting how one of the first things they mention is that you won't be expected to code. That may be true in some orgs but not others.<p>In my org team leads are the managers as well as the technical leads and wear the Scrum Master hat too.<p>Most of the other advice is still sane if you ask me but personally I do like oue mix of coding and other challenges. Keeps things interesting and you don't get too bored of one side of things. Also, it's much easier to see if one of your 'stars' is actually one or is just the loudest. If you don't really know the code base yourself that can be a little harder to figure out and message. And you don't have to work on the large, important critical path user stories either. Just fixing bugs from time to time is enough to learn their tools, their conventions, keep current, be seen as competent by them (helps tremendously with being listened to in my experience) and still have time to actually do your other jobs properly, because coding comes last but not least.