Re: OT: Agile programming; velocity during testing?

Once a bug is brought to light (i.e. the customer is told about it), they make the determination whether or not the bug is important enough to bump a feature for a given iteration. If it is, then they put it on the plate for that iteration and you estimate it just like anything else. Am I missing something?

thor

Feel the white light, the light within Be your own disciple, fan the sparks of will For all of us waiting, your kingdom will come

Comment on Re: OT: Agile programming; velocity during testing?

Replies are listed 'Best First'.
Re^2: OT: Agile programming; velocity during testing? by Whitehawke (Pilgrim) on Mar 13, 2005 at 15:20 UTC
Hi thor, Well, you and I may have different understandings of how AD works...I added an update to explictly state mine. In my understanding, once acceptance testing starts, you are no longer implementing features.	[reply]
Re^3: OT: Agile programming; velocity during testing? by thor (Priest) on Mar 13, 2005 at 17:20 UTC
Acceptance testing should be happening after each iteration. After all, how can you know if you can collect the points associated with a story if the customer doesn't say it's done? And, how can the customer say that it's done without acceptance tests to back up their claim? thor `Feel the white light, the light within Be your own disciple, fan the sparks of will For all of us waiting, your kingdom will come`	[reply]