Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Issues & Questi... > Agile projects need enhan...
We're swiftly moving towards doing agile projects all the time.This presents a number of problems with SpiraTest. There is no accomodation af the requirement-artefacts used in Agile processes - even the requirement type User Story doesn't have a field for accept criteria.
Likewise, the test case or test step should hold the accept criteria.
And the automatic creation of test cases from tab 'Test Case coverage' in Requirement should map the accept criteria from the user story to the new test case or the 'expected result' in the first test step.
What do others do?
Tryg insurance, Denmark
For Agile projects you may want to consider upgrading to SpiraTeam (vs. SpiraTest), it has support for Tasks (used in Scrum) and has lots of agile planning board views which will feel more natural (vs. the requirements hierarchy view that is the only view available in SpiraTest).
For the user stories, we recommend that the story requirement type is used for the user story definition. The acceptance criteria would be the Description field of the test case (that is linked to the requirement). That is why we have the option to create a new test case from the requirement.