Tuesday, March 30, 2010

How Many Slices In A Packet Of Ryvita



recently finished reading Scrum and XP from the Trenches , Henrik Kniberg. The book is recommended and contains, among other things, good descriptions of case studies of using Scrum (has some XP but in less depth).
At this point I would like to share a paragraph from the foreword by Mike Cohn that I find very good:

"Both Scrum and Extreme Programming (XP) require that the teams have completed some form of potentially releasable product at the end of each iteration. These iterations are designed to be short-term fixed. This focus on delivering working code every so often means that Scrum and XP teams have no time for theories. Model are not intended to draw the perfect UML CASE tool, write the perfect requirements document or writing code to suit all imaginable future changes. Instead, Scrum and XP teams focus on the things done. These teams may agree that mistake by the way, but also realize that the best way to find these errors is to stop thinking in software on a theoretical level of analysis and design, and immerse yourself in it, and start getting your hands dirty to build the product. "

I think it's an excellent summary of what the "spirit Agile software development.