When creating iterations in Azure DevOps (Azure Boards), should non-development phases be included in the dates for each sprint iteration?
My understanding is this: schedule sprint dates in Azure Boards around when development begins and ends (code freeze). This means that sprint planning happens ahead of a sprint iteration start date, and builds get shipped to QA after the sprint iteration end date/code freeze (assuming there is a QA testing phase after development). Planning, testing, deployment, and UAT occur outside of the dates specified in Azure DevOps sprint iterations.
Azure Boards really seems to be built around only 1 active sprint at a time. Developers need to be always working on the current sprint of development work. By limiting the iteration dates to only the development phase of Agile, there is no overlap in the development phases between the previous and next sprints, and the Azure Boards tools work well with this.
The idea is to always keep work ahead of developers, in the sprints, and continue iterating.
But is that not ideal? Should the dates of the sprint iteration in Azure Boards include planning, testing, etc?
This is very difficult to lookup online, on learn.microsoft.com, on other sites, etc, and I was unable to find any information explaining WHICH dates are supposed to be used when creating sprint iterations in Azure DevOps.
Here's a visual of what I'm talking about: