33 Quotes by David J. Anderson

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.

Kanban is not a software development lifecycle methodology or an approach to project management. It requires that some process is already in place so that Kanban can be applied to incrementally change the underlying process.

Predictability builds and holds trust, a core Agile value, better than does delivering more with less reliability.

Donald Wheeler and Donald Reinertsen on variability and queuing;.

Kanban, while Japanese, is less metaphorical than Drum-Buffer-Rope.

Prioritization is rightly the job of the business sector, not the technology organization, and so should not be within a technical manager’s remit. Unfortunately, it is commonplace for business management to abdicate that responsibility and leave a technical manager to prioritize the work – and.

First, how could I protect my team from the incessant demands of the business and achieve what the Agile community now refers to as a “sustainable pace”? And second, how could I successfully scale adoption of an Agile approach across an enterprise and overcome the inevitable resistance to change?

The two pillars of the Toyota production system are just-in-time and automation with a human touch, or autonomation.

You need slack to enable continuous improvement. You need to balance demand against throughput and limit the quantity of work-in-progress to enable slack.