TLDR: Does anyone know a way to organize requirements (User Stories & Acceptance Criteria) to tasks in a way to make sure we’re on track, what work remains, and any holes (For example: If there is work being done that doesn’t directly correlate with a User Story). Dependencies help, but they really hard to keep track of if you’re just looking to see remaining work for tasks and the whole project.
I have recently setup weekly syncs among developers and stakeholders to make sure we’re on track and all work being done by my team directly correlates to specific requirements (User Stories and/or Acceptance Criteria).
I am having a hard time figuring out the best way to connect User Stories/Acceptance Criteria to tasked work in a way that is easy to see (1) estimated work to be done (2) what remains on for not only US/AC, but the overall project.
I’ve tried Portfolios, Sections, Subtasks, and dependencies, but still can’t find a way to easily paint my story. I am currently navigating between 3-4 projects:
Project Name - Development. Sectioned off by Iteration, with tasks that need to be done. (These tasks are then put into Sprints)
Project Name - User Stories. Sectioned off by Iteration, with User Stories as tasks, Acceptance Criteria as subtasks, and tasks from the project above added as dependencies.
Project Name - Dev & Product. Sectioned off by PM work and timelines.
Sprint Sectioned off by team, with tasks being worked within the Sprint!