Questions for an Enterprise Architect
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Ryan Slobojan on Jan 06, 2010
Scrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. So how do they relate to each other? The new InfoQ minibook by Henrik Kniberg and Mattias Skarin, Kanban and Scrum - making the most of both, clears up the fog so you can figure out how Kanban and Scrum might be useful in your environment.
The book is broken into two main parts. The first part explores the similarities and differences between Kanban and Scrum with a focus on understanding the capabilities of each rather than judging those capabilities - the concept behind this is that a tool itself is not good or bad, but the decisions made on how to use it can definitely be good or bad. The second part is a case study which illustrates how a Scrum-based development organization implemented Kanban in their operations and support teams. Consistent with the style of Scrum and XP from the Trenches, this book strikes a conversational tone and is bursting with practical examples and pictures.
As Mary Poppendieck, one of the authors of Lean Software Development: An Agile Toolkit says in the foreword:
Henrik Kniberg is one of those rare people who can extract the essence of a complicated situation, sort out the core ideas from the incidental distractions, and provide a crystal clear explanation that is incredibly easy to understand. In this book, Henrik does a brilliant job of explaining the difference between Scrum and Kanban. He makes it clear that these are just tools, and what you really want to do is have a full toolkit, understand the strengths and limitations of each tool and how to use them all.
In this book you will learn what Kanban is all about, its strengths and limitations, and when to use it. You will also get a good lesson on how and when to improve upon Scrum, or any other tool you may happen to be using. Henrik makes it clear that the important thing is not the tool you start with, but the way you constantly improve your use of that tool and expand your toolset over time.
The second part of this book by Mattias Skarin makes the book even more effective by walking you through the application of Scrum and Kanban in a real life situation. Here you will see an example of how the tools were used both separately and in combination to improve a software development process. You will notice that there isn't a single "best" way to do things; you have to think for yourself and figure out - based on your situation - your next step toward better software development.
In his foreword, David Anderson, founder of the Agile Project Leadership Network, also adds:
We've learned a lot about Kanban in the past 5 years and we all continue to learn more every day. I've focused my own work on doing Kanban, writing about Kanban, speaking about Kanban and thinking about Kanban in order to better understand it and explain it to others. I've deliberately stepped back from comparing Kanban to existing Agile methods, though some effort was spent in 2008 explaining why Kanban deserved to be considered an Agile compatible approach.
I've left it to others with a wider experience to answer questions like "How does Kanban compare to Scrum?" I am so glad that Henrik Kniberg and Mattias Skarin have emerged as leaders in this regard. You, the knowledge worker in the field, need information in order to make informed decisions and move forward with your work. Henrik and Mattias are serving your needs in a way that I never could. I am particularly impressed with Henrik's thoughtful approach to comparison and his factual and un-opinionated, balanced delivery. His cartoons and illustrations are particularly insightful and often save you reading many pages of text. Mattias' field case study is important because it demonstrates that Kanban is much more than theory and it shows you by example how it might be useful for you in your organization.
Discussion about this new book on Twitter have included:
As with all InfoQ minibooks, Kanban and Scrum - making the most of both is available as a free download from InfoQ.
Agile Development: A Manager's Roadmap for Success
Case Study: IBM's Agile Transformation
A practical guide to choosing the right agile tools
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
Chris Richardson shows how he ported a relational database to three NoSQL data stores: Redis, Cassandra and MongoDB.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
Andreas talks about the benefits of the Open Web and how it compares to proprietary stacks. He also talks about various projects that push the envelope like Boot to Gecko, Broadway and pdf.js.
Ron Bodkin discusses early adoption of Hadoop, NoSQL and describes MapReduce and related libraries and Frameworks. Other topics include Hive, Pig, multi tenancy, and security in a big data environment
Stephen Bohlen explains how Spring helps with interoperability between Java and .NET, demoing it with the help of a sample application.
Guilherme Silveira mentions some of the turning points in project development that may affect the quality of the code offering advice on avoiding writing crappy code.
No comments
Watch Thread Reply