I should not have to justify Kanban.  If you’re reading this then someone has already decided that this is the way of the future. There are plenty of images of Kanban boards on google and other search engines. It’s pretty simple to implement basic and advanced boards. The complexity comes from lack of discipline to keep doing it. It’s so easy to get lazy.Five Kanban properties: Visualize Workflow Limit Work-in-progress measure and manage flow make process policies explicit use models’ to recognize improvement opportunitiesKanban shares some elements with Lean, Scrum, Agile, and even waterfall. Artifacts include epics and stories. Work cycles or sprints have time limits. Teams might have multiple stand ups based on cross functional team makeup as well as roll ups.The Basic Kanban board (extremely oversimplified): input queue analysis development test stage prodThe Basic Kanban board with buffers (extremely oversimplified): Input queue analysis (in prog, done) dev ready (in prog, done) development (in prog, done) build ready test release ready stage prodThe Kanban board movement: input enters from the left and output exits to the right officially workers are only supposed to pull WIP they will push into queues workers pull from the queues never exceeding their WIP limits When a story is removed it’s because it was completed, implemented and verified in production or KILLEDThe Advanced Kanban Board(s): There might be an epic board which drills down to individual team or cell boards Each sub-board might be parsed or forked; by vertical function or horizontal worker role. Or a master board might have extra columns for individual contributors or even horizontal sub-columns based on role and/or vertical.Standups: meant to happen near the boards meant to happen in public/common locations as to attract external attention meant to be short and to allow commingling of cross functional conversations meant to fail fast and identify blockers fast create slack (whatever that means) cadence promotes consistency and reproduction do not really promote remote users standups in team rooms do not promote global interaction know the difference between a block and a speed bump. decide on a format that works for the team. What you did yesterday is not really that important.Metrics: generate reports measure business value (internal and external) track to revenue or savings detect failures perform root cause when necessary - do not use intuitionExceptions: set WIP limits set queue and buffer sizes limit scope to epic slack used to catch up, recharge or experiment###