3 ms·
I used to enjoy most days. Worked in faux-agile but really a waterfall model, on useful/important products. Had a lot of freedom and gave myself enough slack to
by silveroriole 8y ago
I used to enjoy most days. Worked in faux-agile but really a waterfall model, on useful/important products. Had a lot of freedom and gave myself enough slack to improve things along the way.
Now working in “real agile” where every ticket is (supposed to be) a day’s work or less and everyone’s constantly at full capacity with stupid “implement whizzbang feature because management say so” tickets. Still doing similar work technically, but now it’s absolutely soul-draining! Hooray!
- sethammons 8y agoDoes anything actually say that agile tickets are supposed to be less than or equal to one day?
- silveroriole 8y agoYes, but only our micromanaging bosses/leads. Real agile is certainly in quotes for a reason :) Nominally it’s agile because it lets you fit things into sprints and you’re doing the smallest possible thing with frequent comms, etc. In reality, having tiny little tickets makes for effective developer surveillance, and makes development into a nice mechanical assembly line with no surprises. Well, it doesn’t, of course, but it also conveniently makes all issues look like incompetent devs - how could they POSSIBLY mess up 1 day tasks!? Enterprise agile!
- shoo 8y agoHave you tried doing the Sprint flavour of capital-A agile? As you describe with the benefit that the powers that be can change their mind about priorities as often as they like, but you only listen to them when reprioritising once every sprint cycle.