As someone who runs a software agency, kanban sounds like nonsense.
If you don’t know exactly what you’re doing, for whom, by when, you fail to meet expectations by delivering the wrong thing by the wrong time.
There is design & estimation, planning, development, and evaluation phases. End of story. It doesn’t matter what you call those phases. If you don’t do design and estimation, you have no idea what you’re building or any metric for success. If you don’t do planning you have no schedule for delivering it.
“I’ll do this feature as defined by a two sentence ticket whenever I complete it” is incompetent and reckless. It’s idiotic. I’ve seen many companies operate this way, and they are constantly delivering the wrong thing by the wrong time (particularly VC-backed startups).
If you don’t know exactly what you’re doing, for whom, by when, you fail to meet expectations by delivering the wrong thing by the wrong time.
There is design & estimation, planning, development, and evaluation phases. End of story. It doesn’t matter what you call those phases. If you don’t do design and estimation, you have no idea what you’re building or any metric for success. If you don’t do planning you have no schedule for delivering it.
“I’ll do this feature as defined by a two sentence ticket whenever I complete it” is incompetent and reckless. It’s idiotic. I’ve seen many companies operate this way, and they are constantly delivering the wrong thing by the wrong time (particularly VC-backed startups).