MIS 340 Lecture Notes - Lecture 4: Kanban Board, Taiichi Ohno, Time Management

• School: Iowa State University
• Department: Management Information Systems
• Course: MIS 340
• Professor: Townsend Anthony

Document Summary

Kanban in action: software development: the problems: Kanban in action: data survey: the problems. Kanban is a lean agile system that can be used to enhance any software development lifecycle including scrum, xp, or waterfall. To continuously and predictably deliver value: kanban promotes the lean concept of flow, the work and the workflow is made visible, kanban limits work in progress, kanban is not a software development methodology, it is a method. To make activities and issues like backups obvious. It implies there is no ongoing relationship: kanban is based on the notion that the team will stay together and engage in a relationship over a long period of time. It implies a commitment to a relationship not just to a piece of work and therefore a higher level of trust. Scrum vs. kanban: kanban has less rules than scrum, kanban is great methodology for maintenance, scrum is good for development that is heavily dependent on stakeholders".