673
"Feature Prioritisation" by Work Chronicles
(workchronicles.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Oct 2023
673 points (97.9% liked)
Comic Strips
18495 readers
496 users here now
Comic Strips is a community for those who love comic stories.
The rules are simple:
- The post can be a single image, an image gallery, or a link to a specific comic hosted on another site (the author's website, for instance).
- The comic must be a complete story.
- If it is an external link, it must be to a specific story, not to the root of the site.
- You may post comics from others or your own.
- If you are posting a comic of your own, a maximum of one per week is allowed (I know, your comics are great, but this rule helps avoid spam).
- The comic can be in any language, but if it's not in English, OP must include an English translation in the post's 'body' field (note: you don't need to select a specific language when posting a comic).
- Politeness.
- Adult content is not allowed. This community aims to be fun for people of all ages.
Web of links
- !linuxmemes@lemmy.world: "I use Arch btw"
- !memes@lemmy.world: memes (you don't say!)
founded 2 years ago
MODERATORS
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.