To Change or Not to Change?

by Markus Gartner

David Anderson describes Kanban as an evolutionary change method.1 In comparison to other agile methods, Kanban can be introduced with little changes. But what are the differences between different methods? And is there a way to handle changes more successfully?

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve your password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com, or you can Request Guest Access.
To Change or Not to Change?01 December 2011

Become a Member

Research and inquiry privileges, plus regular strategy meetings with Cutter's pioneers and leaders in the Agile movement, are just some of the perks! Talk to Cutter today about trial membership, including access to research, webinars, podcasts, white papers and more.

Request trial membership

Get the Agile Feed

Agile 'Beer Summit'

Israel Gat (Director of Agile Practices for the Cutter Consortium) was kind enough to invite Damon Edwards (DTO Solutions) over for beers in his backyard to discuss a wide range of topics including Agile, DevOps, and the measurement of Technical Debt.