From the course: Agile Software Development: Kanban for Developers

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Handling process policies

Handling process policies - Trello Tutorial

From the course: Agile Software Development: Kanban for Developers

Start my 1-month free trial

Handling process policies

- [Instructor] We've been talking about establishing your team's policies and having everyone be crystal clear on what they are, but not on how to keep track of that information. Work-in-progress limits are already implicit policies existing on the Kanban board for everyone to see. But what about unwritten things we all do every day when building our software? Well, the idea in Kanban is that there shouldn't be unwritten policies. Anything important enough to affect development should be explicitly stated and easily accessible to your team. I can hear you about to scream, if we wanted to generate piles of documentation, we would've just stuck with Waterfall. Lean and Kanban are always focused on doing what's necessary not adding extra work. The same goes for explicit policies. More often than not, a team employing Kanban and Lean is going to evolve a process with a few important policies rather than a lot of superfluous documentation. Now that's not to say that more documentation…

Contents