|
Seanzor posted:Content: I loathe traditional Agile user story syntax; when our team switched from waterfall to Agile a few years ago, all of our tickets were titled in accordance with scripture, and it was infuriatingly difficult to parse through a sprint/backlog full of tens/hundreds of tickets that all read like "As a user I want [awkwardly-phrased description of feature]". I worked with a bunch of developers who loved this syntax. But our backlog was full of poo poo they'd written like "As a developer I want to rearchitect the history_archive_encrypt module so that it is better" or "as an operator I want to deploy version 1.6.1r16 to the QA environment". There wasn't any evil PM asking them to do it...  Actually, the PMs at that company were pretty good: any feature they requested always came with some kind of justification. Like, if they wanted a bigger button there would be a comment from the new UX person. Or if they wanted some new feature they'd have done a user study that indicated that people liked it. It was pretty cool. Then the next place I was at all the features were justified as "I think this would be good". It was not great for morale to look at the Google Analytics graphs showing that the feature we were enhancing was used by ZERO of our users.
|
#
¿
Oct 25, 2017 21:57
|
|
|
|
| # ¿ May 12, 2024 00:41 |
|