SagXD@lemm.ee to Comic Strips@lemmy.world · 10 months ago"Feature Prioritisation" by Work Chroniclesworkchronicles.comimagemessage-square26fedilinkarrow-up1688arrow-down115file-text
arrow-up1673arrow-down1image"Feature Prioritisation" by Work Chroniclesworkchronicles.comSagXD@lemm.ee to Comic Strips@lemmy.world · 10 months agomessage-square26fedilinkfile-text
minus-squarefunkless_eck@sh.itjust.workslinkfedilinkarrow-up2arrow-down3·10 months 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·10 months 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-up2arrow-down4·10 months agoThat doesn’t sound like a very helpful or useful definition in day to day operations.
minus-squareThenThreeMore@startrek.websitelinkfedilinkEnglisharrow-up1·10 months 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.