Day 3 wrap-up

You may have noticed that I’m blogging less and less on each day. Some of this is because the planning and procedural stuff is becoming less emphasized as we work more on getting a story done. While I could say “we wrote code” it doesn’t seem the same to me in terms of what I […]

Day 2 Group Retrospective

We split up into 3 sets of pairs (actually 2 pairs and a triple) to focus on three tasks: An acceptance testing framework (using the DOM) Conversion of data from word doc into usable stuff Developing an initial page that displays the case information After spending the time to do the development, here’s where we […]

Test Ideas (Day 2 Iteration)

Beginning day 2, we decided to go with the cgi approach because it already handles POST requests. Since we’ll have 140 tests, the GET method of form submittal will quickly be unwieldy. We then delayed acceptance testing strategies until noon. Then, we began brainstorming test ideas (the next story we’ll be implementing): Click a test […]

Iteration #1

This afternoon was spent doing iteration 1. Our initial task list was: Get people up to speed on RubyFIT Determine how to run FIT from within Eclipse Perform a spike to determine feasibility of using the cgi library (through Apache) Perform a spike to determine feasibility of using a basic built-in Ruby server Determine how […]


We talked about how we were going to estimate the various stories. We decided to do estimates in stream half-days (one or two people (since there’s 7 of us – Bill, Brian, Lisa, Chris, Mike H., BC, and myself). Working down the stories in the last post, we came up with the following estimates. One […]

Stories for the Veterinary project

I’m working on the veterinary project. Brian has talked to a person he knows who is involved in giving this test, and talked about what they’re looking for in this application. We then talked about the user stories we could pull out of the description Brian gave us. Here’s the stories we’ve come up with […]