sag@lemm.ee to Comic Strips@lemmy.world · 2 years ago"Feature Prioritisation" by Work Chroniclesworkchronicles.comimagemessage-square28linkfedilinkarrow-up1681file-text
arrow-up1681image"Feature Prioritisation" by Work Chroniclesworkchronicles.comsag@lemm.ee to Comic Strips@lemmy.world · 2 years agomessage-square28linkfedilinkfile-text
minus-squarefunkless_eck@sh.itjust.workslinkfedilinkarrow-up2·2 years agonot necessarily. Your “stakeholders” on the deal/contract that interface with product and success managers could all be VPs who never use the product.
minus-squareThenThreeMore@startrek.websitelinkfedilinkEnglisharrow-up6·2 years agoNo. A stakeholder is anyone with an interest in the project. Where you consider the importance of a particular stakeholder vs another is a different question.
minus-squarefunkless_eck@sh.itjust.workslinkfedilinkarrow-up2·2 years agoThat doesn’t sound like a very helpful or useful definition in day to day operations.
minus-squareThenThreeMore@startrek.websitelinkfedilinkEnglisharrow-up1·2 years agoMeh. It is what it is though. That’s why you have stakeholder analysis.
not necessarily. Your “stakeholders” on the deal/contract that interface with product and success managers could all be VPs who never use the product.
No. A stakeholder is anyone with an interest in the project. Where you consider the importance of a particular stakeholder vs another is a different question.
That doesn’t sound like a very helpful or useful definition in day to day operations.
Meh. It is what it is though. That’s why you have stakeholder analysis.