To Change or Not to Change?

Advisor

Posted November 30, 2011 | Leadership |

David Anderson describes Kanban as an evolutionary change method.¹ 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?

About The Author

Markus Gartner

Markus Gärtner studied computer sciences until 2005. He published his thesis on hand-gesture detection in 2007 as a book. In 2010, he joined it-agile GmbH, in Hamburg, Germany, after having been a testing group leader for three years at Orga Systems GmbH. Markus is the co-founder of the European chapter in Weekend Testing, a black-belt instructor in the Miagi-Do school of software testing, and contributes to the ATDD-Patterns writing community… Read More

Don’t have a login? Make one! It’s free and gives you access to all Cutter research.

	Balancing Wind-Energy Needs with Biodiversity Goals
	Actionable Steps for Corporate Nature Positive Journeys
	Assessing the Potential of Lunar Resource Utilization
	Beyond Orbiting: Toward a Sustainable Space Economy — Opening Statement
	The Tragedy of the Commons in Orbital Space: Toward a Circular Economy
	3D Printing & the Future of Space Exploration

To Change or Not to Change?

Subscribe to free newsletters

Contact us