Be the first to like this
For any product that has users and a future, inputs for product direction come in from different quarters.
- Product marketing and sales guys
- Senior management
- Product manager's vision
- Existing customers
- Prospective customers
- End user input via support channel
- End user feedback via social media
- Industry trends
- Product development team
These inputs may be at the granularity of feature requests or more strategic. If these inputs are collected and curated carefully, it can be an invaluable basis for prioritizing the backlog. But this calls for a fair amount of effort and typically, the product owner or product manager don't have the time to do justice to this job. As a result, we end up with a uncurated backlog that is scattered in people's minds, emails, ticket management system, project management tool, presentations etc. This leads to somewhat unscientific prioritization.
There is a role of backlog curator lurking in here. Need not a full time role but something that a product analyst (BA) can do for say one-third of the time. In the talk/workshop we'll explore some techniques for effective curation and retrieval that enable a more data-informed approach to backlog prioritization.