I am part of a company that is just establishing our process methodology for using the SAFe version of Agile, and leveraging the TFS 2015 Agile process template. Our team has several questions regarding the proper usage of the artifacts. Primarily our teams consist of BAs, QAs, and Devs. The questions we are currently dealing with are:
1) User Story - Who creates the user story? - Should the assignment of the user story change through the life of the user story? (ie: BA creates the user story, then assigns it to the developer, who then assigns it to the tester...) Or should the user story always stay assigned to the creator and tasks get created underneath it that are then assigned to people to work on?
2) Tracking what is in a "release" - Our teams have been using an additional field created on the User Story to track a "Status", which contains things like "Deploy to ", "Deployed to ", "Deploy to "... etc. This is to help inform the testers of what user stories are available to be tested. We currently do not have a firm grasp on how to properly track this information. Some are arguing that this added field should not exist on the user story at all, while other are adamant that this Status field is more valuable than the native State field of the user story. The bottom line is, what is best practice for determining what is available to be tested in what environment? Perhaps we are doing Agile wrong and are not even close to hitting the mark here, so some advice and guidance in this regard would be appreciated.
I would appreciate if you could share your own experiences of what has/hasn't worked and/or point me to additional resources that help with the practical application of the TFS artifacts as they are used to track work along with code, testing and deployments. Thank you.