4 ms·

I enjoyed and mostly agree with these ideas. Some points though: Re: Position In a Queue > Every team must have a single ordered queue of tasks > every sin

I enjoyed and mostly agree with these ideas. Some points though: Re: Position In a Queue > Every team must have a single ordered queue of tasks > every single one of them is prioritized relatively This may lead in Eisenhower's matrix to prioritize urgent tasks vs important tasks and end up with tech debt. I lead a soft eng team and we have a task queue but they are not prioritized (and that may be a mistake). Beyond the time wasting agonizing if X > Y for tasks, I like to keep parallel tracks of urgent (blocking) and tech debt tickets. Re: Ticket Type The most or one of the most important metric in software is user angry or happy calls (a proxy for revenue). If an unannounced planned feature doesn't make it to the next release, nothing happens. But if the customer now sees a regression bug (something that worked suddenly doesn't) that's bad. There's value in differentiating bugs from features, at least in some industries. Re: Software Version See Semantic Versioning https://semver.org/ https://semver.org/ ; it's important to know if a release is backwards-compatible or not

taftster 6y ago
A bug report does not imply a user is angry or not. Software is shipped with known bugs which often go unfixed. And a lack of features can be just as critical of an impediment for a user. So neither bug nor feature can fully describe the effect that an identified issue has on its overall priority. An angry phone call doesn't universally change the order of work for all companies. Some projects might rate this event more importantly than other projects. Most angry phone calls are a result of usability problems not strictly feature defects. So there's no direct correlation here between user product sentiment and backlog priorities, unless your company culture adds that correlation.
- lazyant 6y ago
  thanks for this nuances.

taftster 6y ago

A bug report does not imply a user is angry or not. Software is shipped with known bugs which often go unfixed. And a lack of features can be just as critical of an impediment for a user. So neither bug nor feature can fully describe the effect that an identified issue has on its overall priority. An angry phone call doesn't universally change the order of work for all companies. Some projects might rate this event more importantly than other projects. Most angry phone calls are a result of usability problems not strictly feature defects. So there's no direct correlation here between user product sentiment and backlog priorities, unless your company culture adds that correlation.

lazyant 6y ago
thanks for this nuances.