My friends and colleagues in the #NoEstimates circles have some good ideas, as I’ve commented elsewhere. I’m left, though, with a couple of concerns.
Index of ‘Practices’ Articles
The Agile Manifesto says “Deliver working software frequently”. Learn to do that. The rest will follow.
It’s time to work a bit on the “model” for the game. I envision an array of “stories”, each able to answer how long it will take to do it, and how valuable it is. The answers to these questions …
Let’s take a look at what we have so far, and see what the code is trying to say. Does it seem like early days for that? Maybe not … why not start thinking right away? :)
-- Game Spike…
At the Agile Developer Skills course at the Raikes School, I commented that we don’t usually test accessors. But we test everything. Is this a contradiction?
Jon Bettinger has found a failing test! Excellent!
Philip Schwarz provided a nice-looking implementation. Let’s look at it and try to build on his ideas.
My critiXXXXX advisors expected a more function-oriented solution. Here’s something a bit better, perhaps …