Timeline for Almost every reported bug is a high-priority bug
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2015 at 12:58 | comment | added | Cronax | It's a normal process insofar as the client will always feel that the bug they are experiencing is more important than it probably is. At the same times, devs are notorious for underestimating the importance of bugs. This is why Scrum has a product owner who sits in between the two with knowledge of the business domain combined with the high-level view of where the application is going. They are uniquely suited to correctly assess the priority of any story or bug. | |
| Nov 17, 2015 at 11:16 | comment | added | Pieter B | @DavorŽdralo maybe process is not the right word used here. I meant it's the normal thing that happens. | |
| Nov 17, 2015 at 11:12 | comment | added | Davor Ždralo | That is not a normal process. Clients have no business interacting with developers on that level, if that is happening, management has completely and utterly failed to do its job. | |
| Nov 17, 2015 at 10:45 | history | answered | Pieter B | CC BY-SA 3.0 |