I manage a team of 6 software engineers, and while I like most of this list, I think #3 will only work for a small team and small-medium projects.
If I took most of the burden on to myself to do the work my engineers don't like I would be a major bottleneck.
Alternatively, what I like to do, is couch and encourage my engineers through these less savory tasks so they can get to the development as quickly as possible.
Edit: You could also argue that it might be worthwhile hiring a business analyst, but I haven't had much good experience with BAs.
I don't quite understand what BA does, but where I live, companies are looking for BA like crazy... so I assume BA is quite useful in a bigger organization (possibly in a medium to large org).
The definition of a BA will vary by organization. I think ideally a BA would be a person that is familiar with the business as well as the software being developed. They are the people that can understand and extract all of the wants of the business and fit them in to a new or existing piece of software by writing detailed specifications and documentation.
My experience has been that BAs are often unfamiliar with both the business and the software, which is far from ideal.
If I took most of the burden on to myself to do the work my engineers don't like I would be a major bottleneck.
Alternatively, what I like to do, is couch and encourage my engineers through these less savory tasks so they can get to the development as quickly as possible.
Edit: You could also argue that it might be worthwhile hiring a business analyst, but I haven't had much good experience with BAs.