4 ms·
What’s worked best for me is basically ‘agile’ but without a lot of what I consider to be the bullshit. Project manager and/or team lead prioritize new cards as
by jrs95 9y ago
What’s worked best for me is basically ‘agile’ but without a lot of what I consider to be the bullshit. Project manager and/or team lead prioritize new cards as they come in, and developers just keep working on them. No sprints, just keep pulling work out of the backlog as needed. Stand ups and most meetings can be replaced with quick updates via Slack, otherwise they can be organized as needed (they usually aren’t). We had agreed that estimation was mostly a pointless waste of time, so we stopped doing it.
- mmcnl 9y agoThis could work, but it relies on highly competent autonomous team members who trust eachother. Often not the case.
- jrs95 9y agoIt should be the case though. Competent, autonomous, and trustworthy is a pretty low bar.
- maxxxxx 9y agoI think that's called "Kanban".
- goostavos 9y agoI have never been happier or more productive under any other system than the one you described. We paired the agile stuff down to _just_ stuff we needed. Planning was bucketing things into a super coarse High/Medium/Low priority, and then off we'd go. We'd still give a quick estimation, but that was primarily used as a tool to gauge if anyone had "Thar be dragons" level hesitations about the feature. The opposite end of the spectrum is where I'm at now. Where planning meetings last _hours_ and are mostly an exercise in squabbling over how we're going to get the points to agree with the TPMs completely arbitrary projected view of how things should go which was somehow divined before actually talking to any of the developers.