• FooBarrington@lemmy.world
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I’ve worked in a couple corporations, thank you.

    Let’s think of a simple example: you’re starting a new project, the current infrastructure is technology A, but one engineer proposes technology B, since it’s better in categories X,Y,Z. You can plug in anything you want here. Now, the engineers can give their opinions and estimates, but they can’t decide it. The PM can. It’s his job to weigh the risks and uncertainties and decide on the path forward.

    This has absolutely not been the case in any corporation I’ve worked, the PM is not allowed to make these kinds of decisions. They are made by technical or solution architects. It’s also in no way a PMs job to weigh risks and uncertainties when making technical choices, since they literally can’t.

    Again, as the guy above, you’re thinking way too narrowly focused on your small slice of the world. IT departments aren’t magical omnipotent collections of super smart people, revolving mainly around themselves and their superior technology. They’re just cogs, we are cogs, and our job is, to keep a machine running.

    You’ve obviously never worked in a corporation if you think a PM is allowed to make this kind of choice.

    • AggressivelyPassive@feddit.de
      link
      fedilink
      arrow-up
      1
      arrow-down
      3
      ·
      edit-2
      1 year ago

      Then ask yourself: who is taking the risk? Who will get blamed, if the project fails? The architect? Or the guy who let the architect do his thing?

      • FooBarrington@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Obviously the architect, and consequently the project owner. The project manager has no say in these decisions, why would they get blamed? I’ve never seen that happen, while I’ve seen the PO get blamed multiple times.

        I really think you’ve never worked in a corporation, because what you’re saying just doesn’t happen. The PM gets blamed if the project falls behind, but not if the technical decisions of the architect make problems. A “project manager” is not a manager in the classical sense…