> without those annoying team planning/documentation meetings, work will get duplicated, done hastily, done with no discussion or thought toward testing, archit

> without those annoying team planning/documentation meetings, work will get duplicated, done hastily, done with no discussion or thought toward testing, architecture, maintainability I don't see why that is necessarily the case. It certainly didn't happen on the Kanban teams I've led. Maintaining the backlog and reviewing the work in progress is just as important in Kanban as in any other process.