My Product team does not want SIT or E2E user stories under the Feature. They want us to use sub-tasks.
Can you share how your team handle SIT (System Integration Testing) or E2E work?
In this example Finance has work to do on their backlog and will not be ready for SIT until 12.2 Sprint 3
System D's work:
Feature: New Policy Benefit A
User Story: Configure Policy (Sprint 1)
User Story: Benefit API (Sprint 2)
User Story: Benefit Webservice (Sprint 2)
User Story: SIT Send Policy Benefit A data to Finance (Sprint 3)
User Story: SIT Receive Policy Benefit A data from System D (Finance story in the Finance backlog parented to System D's Feature
My understanding is subtasks:
Are used as the how of a user story; for the dev team
All subtasks must be done to close the user story
Points will not be captured if the user story is not done
