Does anyone have best practices for managing Scrum and Sprints across multiple projects and service requests? Like a master plan and master sprints.
We have capital projects, or major projects, which require TDX project management. Those projects either have waterfall or card wall plans. Projects with card wall plans are typically managed as kanban boards, where tasks (cards) are simply moved from one status to another (New, Scheduled, In Process, Completed).
We also have smaller projects that we create as service request tickets. These tickets often have ticket tasks associated with them.
We have a development team and an operations team, and sometimes both teams will work on tasks within the same project. For example, the operations team may install physical servers, implement network changes, etc., and the development team may configure software, security, etc. While that project is ongoing, they also work on smaller unrelated projects (service requests), such as updating labs.
Our sprints are every two weeks alternating between Dev and Ops. I meet with the Dev team on Monday, we set our sprint for the tasks we need to complete in the next two weeks. The next Monday, I meet with the Ops team, and we set our sprint for the tasks we need to complete in the next two weeks. This cycle repeats. There are often dependencies between the two teams where the Dev team is waiting for something to be completed by the Ops team.
I've created workspaces for each team, and tasks are associated with those workspaces. However, I don't see a way to group tasks into sprints within a workspace. I'm considering creating a workspace for each sprint and then deactivating the workspace at the end of the sprint.
Is there anyone else in a similar situation, and if so, how do you manage this in TDX?
Thank you in advance for your help.