No good deed goes unpunished. When you step up to be a team player and do that grunt work, you open yourself up to getting more and more of it. Next thing you know you have to stand up for yourself or become a door mat.
In healthy environments (and yes, they do exists) good deeds are actually rewarded, not punished.
Furthermore, grunt work can be an excellent opportunity to shine. For example, you can figure out a way to automate it so that the next person who works on it (which may be you again) has to spend only a fraction of the time on it. Things like running reports or generating documents tend to lend themselves really well to automation, and a little programming ability can take you a long way.
So yeah... think twice before turning away grunt work, even if you believe that you may be given more of it in the future if you agree to take it on now.
http://www.daedtech.com/the-gravitational-force-of-wage-labo...
* Deal with difficult users or customers
* Write documentation
* Go back and forth between different stakeholders to make sure everybody is on the same page
* Make sure other developers have the right tools and equipment
Depending on the manager he could be doing this but if he doesn't the senior Dev has to do it or the project fails