Setup the taskboard so that there are columns named "New", "Active", "Dev / Peer Testing" and "Closed"
Click on "Column Options"
Column Name "New" is based on State "New"
Column Name "Active" is based on State "Active"
Column Name "Dev / Peer Testing" is based on State "Testing", if this state does not exist, please refer to Azure DevOps - Adding or editing custom states
Column Name "Closed" is based on State "Closed"
Rename Iteration 1 to be "Initial", this can be a significant timeframe as to getting everything setup and prepared for your use of Sprints. To edit click the date field on the top right hand corner
Name the Iteration "Initial" with a start and end date
For Iteration 2 and beyond, set the date for a period of 2 weeks and name it something that is easy to recognise, eg: Month Day Year to Month Day Year
Here you can configure your development team capacity, in our example we have 5 developers that have a 7 hour capacity per day for the entire fortnight