4 ms·
I work at a large national software company who shall remain nameless. At some point, they determined that "we are now Agile" and put all work in a tracking sof
by legitster 8y ago
I work at a large national software company who shall remain nameless. At some point, they determined that "we are now Agile" and put all work in a tracking software, and everything must now be assigned to sprints.
But if you dig any amount of depth down it becomes ridiculous. An example I found, the helpdesk literally has one project every sprint ("Ticket resolution: February Sprint 1", "Ticket resolution: February Sprint 2", etc.)
Or tasks that used to take 2 or 3 days now gets split across 2 or 3 sprints, because guy 1 can't allocate it to guy 2 until he finishes it. And it just sits around until the next sprint.
Even creative departments are supposed to snap-to. The idea is a recording a video should be a dozen or so tickets in Jira (edits and revisions happen as bugs). These teams are smart and overworked enough to completely ignore the directive.
And the amount of PMs has increased by an order of magnitude, because taking things in and out of the tracker has become its own workload because managers want to see more and more detailed 'analytics', so work get broken down into finer and finer pieces.
I describe the situation as if someone tried to make their truck lighter and faster by bolting a Lotus onto it.
- sethammons 8y ago> Or tasks that used to take 2 or 3 days now gets split across 2 or 3 sprints, because guy 1 can't allocate it to guy 2 until he finishes it. And it just sits around until the next sprint. This so much. Because no PMs want to adhere to "sprint forecast," but insist on "sprint commitments," you literally cannot commit to doing a unit of work that depends on someone else getting theirs done first until they are done. A smooth flow that gets to market quicker now _must_ be lock step gated by sprint start dates. /me sighs
- iovrthoughtthis 8y agoI imagine stuff like this is why kanban was developed.
- sethammons 8y agoI think kanban was primarily for interrupt driven projects, but this works too for pipeline like stuff.