I'm getting old, I've been doing this for going on 20 years, I've been doing this since before fad workflows were really embedded in the culture. They were around but not nearly as common.
What we did then, and what we do now is what I will term "developer driven development". The developer picks up a task, often themselves, and works on it to completion. If there's a strict deadline, a PM might get involved, usually working directly with the dev(s) on the project. Other than that, the PM's job is largely just to watch over tickets.
I don't get the draw. We've had Agile and Kanban pushed on us before, and it's never stuck. We never got anything positive out of it. It only ever had negative effects on performance.
Is it just to help very poor communicators? People who can't be bothered to talk directly, so they need to waste everyone's time?
We don't do meetings. We don't need them. If someone needs a status update, they ask the person working on it directly.
Building software just isn't as difficult as these workflows try to pretend it is.
What we did then, and what we do now is what I will term "developer driven development". The developer picks up a task, often themselves, and works on it to completion. If there's a strict deadline, a PM might get involved, usually working directly with the dev(s) on the project. Other than that, the PM's job is largely just to watch over tickets.
I don't get the draw. We've had Agile and Kanban pushed on us before, and it's never stuck. We never got anything positive out of it. It only ever had negative effects on performance.
Is it just to help very poor communicators? People who can't be bothered to talk directly, so they need to waste everyone's time?
We don't do meetings. We don't need them. If someone needs a status update, they ask the person working on it directly.
Building software just isn't as difficult as these workflows try to pretend it is.