I do believe there is a better way. Why not take the best ideas from Lean and Kanban and use them to build a better, lighter, simpler and more powerful Agile 2.0 method? Take a look at this article, and tell me what you think: http://bit.ly/Agile2-UltraLight
How to fix Agile? Agile 2.0, Kanban and the rise of Ultra Light Methods.
1–5 of 5 posts
Re: How to fix Agile? Agile 2.0, Kanban and the rise of Ultra Light Methods.
#2Focus on the product, your people and the market. Defining the next process will be a waste of time.
Re: How to fix Agile? Agile 2.0, Kanban and the rise of Ultra Light Methods.
#3[edit, additional thought] It seems like if you're having a problem with Agile development being too process-heavy, you're doing it wrong.
Re: How to fix Agile? Agile 2.0, Kanban and the rise of Ultra Light Methods.
#4Why not just follow the Agile manifesto to the letter and not buy into product-management buzzwords and methodologies? [edit, additional thought] It seems like if you're having a problem with Agile development being too process-heavy, you're doing it wrong.
Having Agile that is process heavy, is precisely what we have. But there seems to be already answers to improve the state of things. Those new methods are part of Agile 2.0.
Early Agile methods, like Scrum or XP are indeed process heavy. =)
Re: How to fix Agile? Agile 2.0, Kanban and the rise of Ultra Light Methods.
#5Sounds like you are searching for a magical process. There is simply not a (light or fat) method that will fix your problems. Focus on the product, your people and the market. Defining the next process will be a waste of time.
But what Agile Development should also provide is a framework, a tool kit to deliver value with minimum overhead. That is precisely what Agile 2.0 should be all about. Please take a look at the article and you will get my point: http://bit.ly/Agile2-UltraLight