jon torresdal - Comments on Book Review: The Art of Agile Development

Comment by Elisabeth Hendrickson on "Book Review: The Art of Agile Development"

suppressed@unknown.org (Elisabeth Hendrickson) — Mon, 28 Jul 2008 19:01:28 GMT

Thanks for your kind words on my Exploratory Testing chapter! Glad you liked it. And I'm glad you like the book as a whole. I do to. It's an honor to be associated with it.

Posted by: Elisabeth Hendrickson

Comment by Jon Arild Tørresdal on "Book Review: The Art of Agile Development"

suppressed@unknown.org (Jon Arild Tørresdal) — Mon, 07 Jul 2008 20:07:14 GMT

Just to clearify. When I said:

I'm still waiting for the Lean book by the Poppendieck's

What I really meant was:

I'm still waiting to get the Lean book by the Poppendieck's that I ordered

Posted by: Jon Arild Tørresdal

Comment by Jon Arild Tørresdal on "Book Review: The Art of Agile Development"

suppressed@unknown.org (Jon Arild Tørresdal) — Mon, 07 Jul 2008 17:36:07 GMT

Without knowing too much about the term "Value Stream Mapping" (I'm still waiting for the Lean book by the Poppendieck's) I would suggest that the retrospective meeting after every iteration in Scrum and XP is a good candidate. In Contiki we also use release retrospective where we go through the complete release process step by step (from user story planning to actual release of the product) and evaluate what we did good and where we can improve. This might be closer to what Lean thinks of as "flow of materials"?. This let us add improvements to the process after every release, and sometimes even add complete new steps to the process that we found important. The best is of course to be able to improve by removing steps that has become redundant (eliminate waste?). One of the steps in our current "flow of materials" is bug fixing and stabilization at the end of the release. This is one of the steps we're trying to eliminate by having zero bugs in the sprints. During sprints we try to focus on our definition of Done Done. Did we manage to be Done Done on all stories in the sprint? If not why? How can we make sure this does not happen again? Did we get better at any of the improvement items we came up with in last retrospective? Where there many unplanned tasks we had to take care of? Why were there unplanned tasks? What can we do to prevent this in the next sprint? And so on... Could this be a NNUG talk? Sure. However, I would rather like to see an agile panel with different people from different companies in Bergen discussing their view. Spice this with questions from the audience and I think we could have an interesting debate. Actually we could need an agile user group in Bergen...

Posted by: Jon Arild Tørresdal

Comment by Thomas Eyde on "Book Review: The Art of Agile Development"

suppressed@unknown.org (Thomas Eyde) — Sun, 06 Jul 2008 16:07:13 GMT

I recently read an interesting piece on "Value in Value Stream Mapping": http://gotboondoggle.blogspot.com/2008/06/value-in-value-stream-mapping.html It seams like Improving the Process, Eliminate Waste and Deliver Value are interconnected. If we don't know our value stream, then our improvements boils down to cost reduction. What are your experience with value stream mapping or similar exercises? If you, or your company are willing to share these experiences, that would be something for an NNUG zip-talk, don't you think?

Posted by: Thomas Eyde