How do you plan your sprints for the program

In Jira, sprint planning is per-project. One board, one project. If your team works across 6 platforms — Salesforce, Dynamics, MuleSoft, HubSpot, Power Apps, and a React app — you have 6 separate backlogs, 6 separate boards, and 6 separate sprint planning sessions. Nobody sees the full picture. The scrum master flips between browser tabs, manually counting story points across projects, trying to build a coherent sprint from scattered puzzle pieces. Azure DevOps has the same limitation — one board, one project. Cross-project planning means spreadsheets. Always spreadsheets.