When should an iteration backlog be created?

Creating an iteration backlog at the beginning of each sprint is aligned with the core principles of Agile methodology. The iteration backlog is a prioritized list of work items that the team commits to completing during a specific sprint. This practice is fundamental to maintain focus and ensure that the team works on the most valuable items to deliver increments of value regularly. It allows the team to set clear goals, define deliverables for the sprint, and ensures that everyone is aligned on the work to be completed.

Starting the iteration backlog at the beginning of each sprint also supports the iterative and incremental nature of Agile frameworks. It provides an opportunity to reassess priorities based on current circumstances, stakeholder feedback, and team capacity, which is essential for ensuring that the project remains responsive to changes.

In contrast, creating the iteration backlog at the beginning of each project would be premature, as you wouldn't have detailed understanding of the team's capabilities or the specific needs of the stakeholders yet. Similarly, defining the MBI or planning for a Kanban board occurs in different contexts and methodologies, not necessarily tied to the specific rhythm of sprints. The iteration backlog is specifically designed for the sprint execution phase, making it most relevant when the team is ready to commit to a defined workload and goals for that time frame.