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? en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/best-practices/646.aspxthreadId=646Aaron McIver (amciver@scfaz.com) 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? Wed, 17 Jul 2013 23:12:28 -04002013-07-31T15:35:05-04:00/Support/Forum/spirateam/best-practices/646.aspxmessageId=1178David J (adam.sandman+support@inflectra.com) Hi Aaron I would refer to the SpiraTeam tutorial to illustrate how the different artifacts work together: https://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 Thu, 18 Jul 2013 15:59:50 -04002013-07-18T15:59:50-04:00/Support/Forum/spirateam/best-practices/646.aspx#reply1178messageId=1179Aaron McIver (amciver@scfaz.com) 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. Thu, 18 Jul 2013 16:58:51 -04002013-07-18T16:58:51-04:00/Support/Forum/spirateam/best-practices/646.aspx#reply1179messageId=1197Aaron McIver (amciver@scfaz.com) 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. Mon, 29 Jul 2013 17:41:37 -04002013-07-29T17:41:37-04:00/Support/Forum/spirateam/best-practices/646.aspx#reply1197messageId=1205David J (adam.sandman+support@inflectra.com) 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 Wed, 31 Jul 2013 15:35:05 -04002013-07-31T15:35:05-04:00/Support/Forum/spirateam/best-practices/646.aspx#reply1205