Notes on Agile Software Development

From:
"andrew cooke" <andrew@...>

Date:
Thu, 24 May 2007 07:54:58 -0400 (CLT)

I have to write a review of this book and I'm worried that by the time I
get to the end I'll have forgotten what I wanted to say at the start, so I
thought I'd make notes here.
At end of chapter 1.0
- Structure of book. Grey tabs are new.
- Very touchy-feely (poetry on site).
- Stating the obvious (so I agree with it).
- Reminds me of adolescence. People reading "How to Make Friends..."
- Can you teach people who don't know that?
-- They end up using the words but not understanding the process?
-- "What should..." sections are aimed at solving this?
-- What's the equivalent of "nice girls want sex"?
- Complex real-life problems - how will these be addressed?
-- Buy-in throughout the hierarchy
-- Clueless architect
-- Cultural differences
- Poor examples
-- Steak tasting is texture
-- Climbers don't care about long term
- Three levels - obvious? useful? how?
Best thing so far: three levels.
Worst thing so far: you shouldn't need to be told this.
Andrew

More Thoughts on Chapter 1

From:
"andrew cooke" <andrew@...>

Date:
Thu, 24 May 2007 08:25:48 -0400 (CLT)

- Mule can be seen as changing from infinite to finite game?
-- Careful with proprietary info... JBoss too?
- Is "you shouldn't need to be told this" a level issue?
- Levels are subjective
-- Depend on generalisation/abstraction/extension
- If you're caught in a low level situation, what do you do?
-- Is faking levels useful?
- I wouldn't have thought of these points if I'd not read the book
-- So are obvious things useful anyway?
-- Or are these pointless?
-- How do you measure usefulness?
-- What is sufficient? (satisficing was also raised in this chapter).
Andrew