Thread

Skip Navigation LinksForums > SpiraTeam Forums > SpiraTeam Best Practices > SpiraTeam as Scrum tool

SpiraTeam as Scrum tool RSS Feed

Wednesday, July 17, 2013
In using other Agile tools on the market, I am struggling to identify how one can essentially have 4 differing artifact types (Epic, Story, Task, Defect) that are all interrelated hierarchicaly? While the requirements area could arguably be the Epic/Story level, the disconnect I am having is that Defects are incidents and Tasks are incidents...or something else? Is there a whitepaper or documentation on how to make use of SpiraTeam in a more flexible Agile manner?
4 Replies
Adam SAdam S
re: Aaron McIver on Wednesday, July 17, 2013
Thursday, July 18, 2013

Hi Aaron

I would refer to the SpiraTeam tutorial to illustrate how the different artifacts work together: http://www.inflectra.com/Documents/SpiraTeam%20Quick%20Start%20Guide.pdf

However in answer to your specific question:

  • Requirements are the User Stories and Epics (depending on whether they are parent requirements or leaf ones)
  • Tasks are the technical tasks that are decompositions of each user story
  • Incidents are any bugs/issues that arise during testing that need to also be included in the Sprint/iteration

Regards

Adam

Aaron McIverAaron McIver
re: Adam S on Thursday, July 18, 2013
Thursday, July 18, 2013
Thanks Adam, that helped.

Is it possible to adjust the effort type at the project level? It seems tightly coupled throughout the product to hours, whereas I would like to scale that up ala story points, or something generic. The caveat as you know is that the tool is assuming that the teams availability in hours somehow equates to the estimation in hours which is notoriously off.
Aaron McIverAaron McIver
re: Aaron McIver on Thursday, July 18, 2013
Monday, July 29, 2013
Adam,

Any suggestion based on my previous reply?

Is it possible to adjust the effort type at the project level? It seems tightly coupled throughout the product to hours, whereas I would like to scale that up ala story points, or something generic. The caveat as you know is that the tool is assuming that the teams availability in hours somehow equates to the estimation in hours which is notoriously off.
Adam SAdam S
re: Aaron McIver on Monday, July 29, 2013
Wednesday, July 31, 2013

Hi Aaron

The plan for v4.1 is to have requirements estimated in story points and then allow you to manage in a more customized manner the conversion from story points to hours.

Regards

Adam

Tagged
Statistics
  • Started: 7/17/2013
  • Last Reply: 7/31/2013
  • Replies: 4
  • Views: 3492
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2016 | Licensed to Inflectra Corporation.