search

dwyl / process-handbook

:green_book: Contains our processes, questions and journey to creating a team
GNU General Public License v2.0
77 stars 10 forks source link

More clarity around priorities #76

Open iteles opened 6 years ago

iteles commented 6 years ago

As mentioned in https://github.com/dwyl/tudo/issues/140 and seen a few times with clients since, priority labels require more clarity.

Here's the original proposal:

screen shot 2017-11-08 at 17 51 16

Thoughts on how to add more detail to each priority level (be it as above or based on any other metric) welcome!

iteles commented 6 years ago

@naazy @Conorc1000 @roryc89 We've had quite a lot of discussion on this on your project - have you found anything that works well for a system in production?

Cleop commented 6 years ago

@iteles - should this be in the product owner repo?

As a side point, more about the content of this issue- whilst I know we reserve priority 1 for emergencies, is it not down to the client to decide what their other priorities are? Even if there was a feature/enhancement that seemed not important to us, providing we have respectfully informed the client of why an issue may not be the best use of time, is it not ultimately down to them to decide what priority things are regardless of use on the app?

iteles commented 6 years ago

@Cleop Very much agree that the actual definition of each priority will vary for each client depending on their needs but having a defined, common framework that everyone on the project understands is important and it would be good to provide a starting point.

Definitely a good one for the PO repo.