Some workspaces manage their flow of work using time-boxed planning and deliver cadences.  Scrum team workspaces are a prime example, as are Solutions and Program Increments in a SAFe framework environment.  Portfolio level workspaces, however, are always of a continuous flow type, so they will never possess iterations (within the platform, however, we designate a continuous flow as the "current" iteration for purposes of internal consistency).

Regardless of whether a workspace is independent (such as a team or project workspace) or part of a portfolio of workspaces, creating increments is accomplished in the same way.

From the summary tab of your iteration-based workspace, click on the new iteration box at the start of your iterations display:

This will bring up an iteration detail screen where you can enter all of the pertinent details about your iteration:

Key things to note:

  • Iteration Name - The application will default with a system naming convention driven by your workspace characteristics.  If your workspace is part of a larger portfolio (such as depicted in the above screen shots), the iteration name will include a numbering convention driven by its parent increment values.  Users are free to modify this value via this interface.

  • Start and End Dates - If you're working within a standalone workspace or a bottom tier workspace within a Portfolio, the system will use a default start date that coincides with the end of your last iteration (a typical convention from teams practicing XP/Scrum).

    Similarly, the default iteration duration will be 2 weeks for a bottom-tier workspace level, and 10 weeks at higher levels (a typical Scaled Agile Framework convention).   

  • Mission - For delivery teams, this is an ideal container for documenting your Sprint goal.  Other workspace levels can use it for similar purposes.

Did this answer your question?