app icon indicating copy to clipboard operation
app copied to clipboard

Adding ideas to the backlog

Open iteles opened this issue 6 years ago • 1 comments

In https://github.com/dwyl/app/issues/239#issuecomment-556214589 we discussed that we didn't want to have a backlog jammed with a lot of 'possible' feature ideas or unprioritised feature ideas that we knew were a few months away.

This was because having these in the backlog and in notifications in particular is distracting and adding a low priority label to the issue (such as priority-5) doesn't help because this just puts the issue in a black hole ("priority-5 is where issues go to die").

Currently I have a note in my notes app with bullet points of features I would like but are not imminent and I therefore don't want to distract people by adding them to the backlog now.

How should we capture these from all members of the team so that they don't get lost? Would regular backlog grooming as suggested in https://github.com/dwyl/app/issues/239#issuecomment-556214589 be enough to use the lower priority labels and trust the issues won't be forgotten? Shall we have an epic of feature ideas where people can add comments (this seems like the best way to lose information)?

What are everyone's thoughts on process for this?

iteles avatar Jan 27 '20 19:01 iteles

In my opinion the best approach we can take at this time would be to create a repository for ideas that are not going to be done at this time. So it would give us space to focus on the most important projects/apps. I was also thinking about another group in Signal just to store we kept Dwyl's group but added another group to put the ideas.

Now that it's been talked about we will all be more careful about what to give a certain priority, the priority should always be around the two applications we want to do in the shortest time possible without compromising the quality of the application.

miguelmartins17 avatar Jan 27 '20 20:01 miguelmartins17