So we have a disagreement between our customer and the development team, these are some facts:
- We are a software development company (I have a team of 3 devs and 1 QA)
- Our customer is a startup, that is growing fast, and already making some money
- We haven't successfully adapted to a workflow, yet
When we began the CTO choose pivotal tracker as our scrum board software, which works fine, however they are constantly adding labels to prioritize the items which I think doesn't make sense under the SCRUM approach where you have a sorting or order in the backlog (and in the current, per pivotal's feature) where, if you need certain story to be addressed or worked on then you need to make sure that is estimated, well defined and you just move it in the backlog to the top, developers then pick up these stories on a LIFO basis.
My motivation to tell the customer that they should not prioritize stories is simple: it is useless. These priorities change all the time, sometimes on every sprint, so the only sane way to keep up would be for them to be re-prioritizing all other stories, not only the new ones which they want to be worked on first, maybe some of the older stories that last week were priority 1 are now priority 2, or even less, plus the constant and ever-changing requirements make this harder, so why bother?
On my opinion this goes against the idea of the backlog and planning of the sprint, but I'm still a rookie on SCRUM so I'm wondering is this kind of prioritization a common practice in the real world?