Baza znanja:
KANBAN
… Pronađite mnoštvo korisnih KANBAN, LEAN i AGILE resursa ( posteri, infografike, primjeri ispita, vodiči, webinari…).
“Kanban must not be thought of as a software development lifecycle process or a project-management process. Kanban is a change-management technique that requires making alterations to an existing process: changes such as adding work-in-progress limits to it. Work”
— David J. Anderson (Kanban)
Baza znanja:
KANBAN
Kanban (看板) (natpis ili reklamni pano na japanskom) je sustav rasporeda za Lean proizvodnju i proizvodnju na vrijeme (JIT – Just in Time). Taiichi Ohno, industrijski inženjer u Toyoti, razvio je kanban kako bi poboljšao učinkovitost proizvodnje. Kanban je jedna od metoda za postizanje JIT-a. Sustav je ime dobio po karticama koje prate proizvodnju u tvornici.
“Summary of Scrum vs Kanban
Similarities:
– Both are Lean and Agile
– Both use pull scheduling
– Both limit WIP
– Both use transperency to drive process improvement
– Both focus on delivering releasable software and often
– Both are based on self-organizing teams
– Both require breaking the work into pieces.
– In both, the release plan is continuously optimized based on empirical data (velocity/lead time)”
— Henrik Kniberg
“SCRUM & Kanban – Differences:
Scrum:
– Timeboxed iterations prescribed.
Kanban:
– Timeboxed iterations optional. Can have separate cadences for planning, release, and process improvement. Can be event – driven instead of timeboxed.”
— Henrik Kniberg (Kanban and Scrum – Making the Most of Both)
“The physical board had a huge psychological effect compared to anything we got from the electronic tracking tool we used at Microsoft. By attending the standup each day, team members were exposed to a sort of time-lapse photography of the flow of work across the board. Blocked work items were marked with pink tickets, and the team became much more focused on issue resolution and maintaining flow. Productivity jumped dramatically.”
— David J. Anderson (Kanban)