http://dannorth.net/2012/05/31/bdd-is-like-tdd-if/
Challenging comment:
Dan North · June 6, 2012
- I’ve seen teams burn insane amounts of time trying to automate UI interactions, for instance, at huge cost and with almost no benefit.
- The opportunity cost, in terms of all the other things they could have done with that time, is considerable, and they’re usually doing it on someone else’s dime.
- I think there’s a duty of care involved in these kind of decisions.
- You shouldn’t automate “because we do” but because there is an identifiable benefit in the automation that outweighs its cost in this case.
- Sometimes that investment is worth it, sometimes it isn’t, so it’s always worth asking the question.
http://lizkeogh.com/2012/05/30/showcasing-the-language-of-bdd/
J.B.Rainsberger: TDD/BDD and Queuing Theory
http://www.jbrains.ca/permalink/how-test-driven-development-works-and-more
Other Reading:
Perils of Estimation
http://dannorth.net/2009/07/01/the-perils-of-estimation/
- move beyond this cargo cult approach to inception where we slavishly trot out hundreds of stories with their associated estimates,
- remember we are engaging in a process of deliberate discovery
Real Options
http://decision-coach.com/lean-and-real-options/
Real Options:
- Options have value.
- Options expire.
- Never commit early unless you know why.
Lean:
- Defer Commitments
- The Last Responsible Moment
- Pull
