38

I'm a developer, not a project manager. Why am I doing project requirements gathering?

Comments
  • 0
    +1 cause clicking the ++ is just not enough
  • 0
    At least you'll have a chance to record the client, so when he/she tells you they didn't want that, you can laugh and pull stupid faces.
  • 0
    You are doing his job for less money I'd guess
  • 0
    Because devs are the only who can see how dumb are some clients' requirements.
  • 0
    I do shit like this in Uni all the time.
    GIVE ME A TEXT EDITOR, NOT A QUESTIONNAIRE DAMMIT
  • 1
    Because many PMs cannot be trusted with getting the correct requirements. Because at the end of the day making ideas become reality is not their problem. It's ours.
  • 2
    Look on the bright side, it's something you can put on your resume.
  • 0
    I don't mind contributing to the requirements, but ultimately I just want to code
  • 1
    get out of your coding cave and be happy that you can show, that you can do better then them even in their field.
  • 0
    @DoctorDalek, sounds almost like you're being (or about to be) promoted out of your chosen field of work.. It's unfortunately one of the worst pitfalls of IT, especially when the whole story is controlled by non-technical people.

    Maybe this is the modern day cost of career progress.. O.o
  • 0
    I've sen a lot of devs move from being an engineer to work as a product manager. That being said I've seen the role of an engineer increase over the years. We no longer just code.

    We design, architect, coordinate, communicate, test, deploy, sing & dance.
Add Comment