Conference Reports

Estimation

Written by Andy Tinkham. Date of post: .

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 thing that I noticed (which Lisa was commenting on over lunch) is that it went a lot faster than I normally would expect. We weren’t summing estimates of each task, and our units of estimation were fairly loose (estimates were more against the other estimates rather than more attempts to accurately figure out our velocity (how many points we can get done during each iteration)

QA1 (estimate = 4)

Tasks:

  • Machine setup (eclipse, FIT, ruby, test::unit, CVS)
  • FIT can run test case
  • Can run unit test, automate unit tests
  • Write HTML page w/ tests
  • 2 spikes: one using available Ruby CGI library, one fully implementing Ruby http server
  • Deployment of server (for external customer viewing)
  • Write static web pages (2 pages — one with case summary and tests, one with results)
  • QA2 (estimate = )
  • QA3 (estimate = 1)
  • QA4 (estimate = 2)

    In discussing an estimate for QA5, we decided that it was really two stories. The first story becomes the new QA5. The second one became QA15

  • (QA5) Cases appear in different windows (window stays open after diagnosis) (estimate = 1)
  • (QA15) Data is retained if the case window is closed (and the window can be reopened. If window is already open, trying to reopen it will make the window rise to the top rather than reopen) (estimate = 3)
  • QA6 (estimate = 1)
  • QA7 (estimate = 1)
  • QA8 (estimate = 1)
  • QA9 (estimate = 2)
  • QA10 (estimate = 1)
  • QA11 (estimate = 1)
  • QA12 (estimate = 3)
  • QA13 (estimate = 1)
  • QA14 (estimate = 2)

    Added another story:

  • (QA16) Printing a case (estimate = 1)
  • S1 (added “(also their text is different too)” to the story description) (estimate = 2)
  • S2 (delayed estimation due to needing information from customer)
  • S3 (retitled to “Each test has a score”) (estimate = 2)
  • S4 (estimate = 2)
  • S5 (estimate = 1)
  • S6 (estimate = 3)
  • S7 (estimate = 1) (clarified to comparison to determine whether someone passed)
  • S8 (estimate = 3?)

    EA1/EA2/EA3 redone to be

  • (EA8) Enter case summary (estimate = 2)
  • (EA9) Enter case diagnoses (
  • (EA1) Enter case’s results in text
  • (EA2) Enter case’s results in tables
  • (EA3) Enter case’s results in images
    All the above are delayed for estimation pending investigation and information

  • EA4 (estimate delayed)

    Added story:

  • (EA10) Ability to look at what will appear on test and determine that it matches what the original case had (validate entry, validate the data)
  • EA5 (estimate delayed — possibly no coding)
  • EA6 (estimate delayed)
  • EA7 (estimate delayed)