Story usually has more than one Activity and contains value of effort,
So, to this point, it is similar to sub-project
complexity (including technical environment, experience of the team, how clear requirements are, how complex is the code to complete the story),
These points would look like requirements.
and risk.
Once again ,sub-project would fit.
Story is something that can be released when it completed. Story is the primary development artifact and the basis for defining the functions a business system must provide, and to facilitate requirements management.
This looks like product version
So Story would be an hybrid object, mid-way between sub-project, requirement and product version...
I'll have a look to agile methods to get more information
Request recorded as Ticket #1794
Support us on Capterra
