I don't know. I found out the hard way that being too good a "team player" will hurt you. People would just shove work to you or to your team. Or take resources from you in the guise of good for the team.
One time in a prior company, an important database/server was under my team's responsibility. Another team needed processing power and asked to borrow some capacity before they ordered their own hardware. Being a team player I agreed since it's good for the company. But over time their processing had huge impact on my tasks and caused performance problems. When I asked them to migrate out, it's always a low priority item, for whatever reason, budget, schedule, or whatever excuses. It took a year to kick them out. I got so fed up that I've contemplated to set up firewall rule to deny access from their machines.
Did people remember I being a team player and helped the other team and the company overall? No, they remembered my server was failing SLA due to poor performance since it's under my responsibility.
>>Did people remember I being a team player and helped the other team and the company overall?
Screwed if you do, and screwed if you don't.
Generally happens in companies where people don't have what it takes to own things up. Keep shifting blame on people until they take responsibility, take credit for wins. But when there is a failure conveniently announce if wasn't your responsibility at the first place. And if they don't take responsibility name them as bad team players.
The game is set to use you and throw you. You can only lose in such a game.