Sun, 15 Jun 2003
Agile Fusion: mid-course correction
We've decided to drop the veterinary exam project. It didn't seem
likely to meet the learning goals for the group. But it led me to
some tentative ideas:
Maybe I should pay more attention to "the natural starting size" of a
project. I bet that one pair of people
could have laid down infrastructure faster than seven people did,
and it would probably have been a better one to build upon.
-
In this early phase, I believe that defining acceptance tests
first helped clarify things. So did seeing the early version of
the app. Seeing the early version was more
valuable. To the extent that automating the acceptance test
delayed deployment of the first version, automation was a bad
thing.
We would have been better off deferring the
automation. We should have just used the acceptance test
manually. I suppose we might have locked in on an implementation
infrastructure that made automation hard, but I doubt it.
-
I'm also inclined to think that choosing to test against the
GUI (by using COM to drive IE) didn't help. I'm disappointed by
that, because my bias has long been to write acceptance tests against the
"domain model", not the GUI. It's boring to have your biases
confirmed.
## Posted at 05:59 in category /agile
[permalink]
[top]
|
|