Iteration

Iteration is considered from two perspectives: a time interval and a specific target date for the planned completion of a set of business and/or business technology goals.

An iteration may or may not produce a product-related outcome. Different stages of the goal lifecycle can occur across various iterations. For example, business requirements might be defined in one iteration, but the implementation hasn’t started yet; development might be completed, but acceptance criteria haven’t been finalized. These stages can be spread across multiple iterations: one iteration for requirements definition and approval, another for development, a third for acceptance testing, and a fourth for release.

Thus, an iteration is a specific amount of work carried out by a specific group of people.

During an iteration, business tasks are assigned, and the following calculations are made:

• Will all the planned tasks be completed by the specified date?
• Are there enough resources—specialists assigned to complete these tasks?
• Will all the goals be achieved?
• Will all lifecycle stages of the business tasks be finalized?

An iteration is both an organizational tool and a reporting method—it reflects the actions performed within that iteration.

Iterations can vary in length and exist within a stream. Different streams may have iterations aligned to the same target date or operate asynchronously.

Iterations are an essential part of planning—short-term, medium-term, or long-term. Planning iterations ahead allows the creation of a roadmap.

Iteration includes:

• A set of business goals for the Stream (Objectives) that are combined by a common result
• Planned completion date for all work

Status of Iteration - is defined/not defined

• Switching "Is defined" is a signal to the system that tasks are ready for planning and automatic assignment of an executor.

By default, the Iteration is "not defined."

Mandatory conditions for transitioning to the "Is defined" state:

• Planned date is set.
• At least 1 task with specified competencies and efforts exists.

There are no restrictions for transitioning to the "not defined" state.

When transitioning to the "not defined" state, all tasks (except those in the "Done" state) are removed from planning, and any assignment of an executor at any stage of the workflow is canceled.

User actions:

• Editing (name, description, plan date) at any time