The simple act of adding a request to a board can make stakeholders feel far more at ease and alleviate a lot of frustration. One of the key pieces in successful stakeholder management is firstly to communicate, but secondly to make people feel like their requests are being heard. Your business backlog can be used to keep track of inbound requests from stakeholders and ensure they have a visible overview of where their requests are in the overall product strategy. Your engineering backlog should be a place where more well-defined stories can be kept (along with the other bits that inevitably aren’t as clean as user stories like bugs and chores). This helps you to collect ideas and inbound requests from the business and keep them separate from the engineering backlog, which should ideally be in a cleaner state. One of the things I like to do as a product manager is to keep 2 sets of backlogs 1 for the business and stakeholders and one for the engineering team. Here we take a look at 6 less common ways you can use Trello as a product manager. However, the beauty of Trello is in its flexibility, which means it can be used in an infinite number of ways to build wonderful processes and workflows. And we’re all used to using Trello in fairly conventional ways typically for our daily standups and project management.
As product people it permeates our existence like coffee and pretentious notepads.
0 kommentar(er)
