Multiple roles: Developer = Technical Writer = Analyst = Project Manager..? - TechRepublic
General discussion
June 23, 2004 at 09:02 PM
jnghh

Multiple roles: Developer = Technical Writer = Analyst = Project Manager..?

by jnghh . Updated 21 years, 8 months ago

I think we can all agree that a software development project involves many different tasks: gathering user requirements, requirement analysis, design, coding, documentation, etc. And that it’s quite normal for one person in a project team to handle a few roles.

But to what extent can we merge these roles on one person? Is it even something we should do? Is it really that beneficial? Or is it actually detrimental to the company?

For me, I don’t really have a problem accepting a few multiple roles at one time. Often, it’s just due to lack of a budget to hire separate developers, analysts and technical writers. But I do have a problem with being given nearly ALL roles at one single time.

The constant juggling of technical details such as programming; debugging; designing; and documenting COUPLED with the constant juggling of less-technical details such as conducting follow-ups with users, clients, and vendors; thinking of business ideas; writing proposals to other projects —

Am I the only one who sees something wrong with the scenario above? It just FEELS wrong.

Agree? Disagree?

This discussion is locked

All Comments