Home > Archive > Extreme Programming > June 2006 > OT: Acceptance test and engineering tasks
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
OT: Acceptance test and engineering tasks
|
|
| noisefree@gmail.com 2006-06-06, 8:01 am |
| I apology, I am new to XP and Agile Development.
I've searched through the group but found no answer to the following 2
questions.
1) Is there a place on the web where can I find a good example of an
acceptance test?
2) When should I split User Stories into Engineering Tasks?
a)During the early planning of each iteration, while evaluating User
Stories (ONLY those stories that will be in the current iteration)
b)During the early planning of each iteration, while evaluating User
Stories (all stories will be splitted in tasks to help evaluating them,
no matter if they are chosen for the current iteration or not)
c)During the development phase, only on those stories assigned to the
current iteration, as a response to a test case in the UAT?
What I don't understand is if
Eng.Tasks are generic development tasks "derived" by the understanding
of the User Story (eg: 1 user story= 1 or more Eng.Task),
or
specific development tasks "derived" by the understanding of the User
Acceptance Test (eg: 1 test case= 1 Eng.Task -or even more-)?
I hope my english is not too messy...
I would appreciate any help.
Thanks in advance.
| |
| John Roth 2006-06-17, 8:11 am |
|
noisefree@gmail.com wrote:
> I apology, I am new to XP and Agile Development.
> I've searched through the group but found no answer to the following 2
> questions.
>
> 1) Is there a place on the web where can I find a good example of an
> acceptance test?
fit.c2.com
www.fitnesse.org
The FIT Book is also an excellent reference: Fit for Developing
Software, by Rick Mugdrige and Ward Cunningham.
>
> 2) When should I split User Stories into Engineering Tasks?
> a)During the early planning of each iteration, while evaluating User
> Stories (ONLY those stories that will be in the current iteration)
> b)During the early planning of each iteration, while evaluating User
> Stories (all stories will be splitted in tasks to help evaluating them,
> no matter if they are chosen for the current iteration or not)
> c)During the development phase, only on those stories assigned to the
> current iteration, as a response to a test case in the UAT?
The latter is the usual practice, although it can be done during
estimating if there's any need to look at a story at a finer level
of detail.
>
> What I don't understand is if
> Eng.Tasks are generic development tasks "derived" by the understanding
> of the User Story (eg: 1 user story= 1 or more Eng.Task),
> or
> specific development tasks "derived" by the understanding of the User
> Acceptance Test (eg: 1 test case= 1 Eng.Task -or even more-)?
Both. An EAT (executable acceptance test) is
the detailed expansion of the sentence or three
in the story. Writing it is usually the first engineering
task in implementing the story, although a lot of
teams write the EAT in advance.
HTH
John Roth
> Thanks in advance.
| |
| noisefree@gmail.com 2006-06-17, 8:11 am |
| > Both. An EAT (executable acceptance test) is
> the detailed expansion of the sentence or three
> in the story. Writing it is usually the first engineering
> task in implementing the story, although a lot of
> teams write the EAT in advance.
>
> HTH
>
> John Roth
>
Thank you very much, I've appreciated your help, I've finally cleared
my doubts.
Long life to XP!
;)
|
|
|
|
|