Working in Itera

The planning phase

The planning phase produces the implementation plan: a graph of pull requests that, taken together, deliver the iteration.

Itera generates the plan automatically. Each PR in the graph:

  • Affects only one deployment target
  • Is small enough to review in a reasonable amount of time
  • Is independently reviewable
  • Implements one self-contained slice of the feature

PRs can have dependencies on other PRs. If PR B depends on PR A, B can't start until A is merged. PRs without unmet dependencies can be worked on in parallel.

You'll see this as a visual graph in the iteration. Review it, request changes via free-text input if you want a different breakdown, and approve when it's right.

Was this page helpful?