Situations where the members of the project team have tasks which are not directly related to their job positions happens quite often (especially in cross-functional teams).
According to my experience, this will always decrease the morale of the team.
Two examples from my practice:
1) On one project my team had a lot of translation work.
In my company we have a special translation department, but the quality of its translations are very poor, they don't have knowladge of the subject area and if we give a translation to them, we will have an external dependency that we can not control well.
That's why the development team does all translation work. Of course, no developer wants to do this and it is a great demotivation factor.
2) Another example. Unfortunately, my company eliminated the tester from my team. Developers can test well, but dont want to (and it's logical, if they wanted to test, they would go to work as testers, not as programmers).
So, how can we decrease this kind of demotivation?
Of course, the answer that we should hire a technical writer or tester on our team is very easy, but in the real world it not always possible.
So, a little bit of explanation about what kind of solution I want: for example, if a new project should be done in a well known or even legacy technologies, some companies make special days for developers, when they can work on their own project with any technologies they want. My company has no resourse for such days. But in any new project we try to implement the minor part with new technology. This decreases the dissatisfaction from monotonous work with boring well known technologies very well.
I am looking for some kind of non-trivial solution to the question that I described above.