Team Edition

Team Edition is a lightweight ALM Octane version which enables DevOps teams to plan, track, build, and release applications using Agile and DevOps practices.

Team Edition overview

Team Edition provides you with the following basic ALM Octane capabilities:

My Work

Quickly view the work assigned or related to you. For details, see Access your assigned work.

Dashboard

Use ALM Octane charts and graphs to analyze quality in context. For details, see Use the ALM Octane Dashboard.

Team Backlog

Manage the team backlog by assigning items to teams, designating specific team members to perform the work, and tracking progress of the team. For details, see Manage the team backlog.

Note: Team Edition does not include a separate Tests module.

Pipelines with basic analysis

Track the status of builds and test runs included in pipeline runs, and analyze the results. For details, see CI Pipelines.

Note: Team Edition provides limited Pipelines module capabilities.

Before you begin with Team Edition, note the following:

  • Team Edition cannot be mixed with other editions, and must be installed on a separate server. On this server only Team Edition functionality is available.

  • Team Edition supports the Named license model only.

  • Team Edition has no restriction on the number of workspaces you can create. The number of users is defined by your license capacity.

  • Team Edition does not support customized roles.

For a comparison of the different ALM Octane editions, see ALM Octane editions.

Back to top

Working with Team Edition: Example of an end-to-end flow

The following flow illustrates how different personas can take advantage of Team Edition capabilities.

Note: Roles can be customized. Roles and their permissions might be different for your organization.

  1. In ALM Octane settings, the Release Manager defines releases, milestones, sprints, and teams.

  2. In the Team Backlog module, the Product Owner defines features and priorities, and plans the release content.

  3. The Dev Team Leader now breaks the features into user stories, and assigns user stories to team members, pushes, and sprints.

  4. Each Team Member tracks their work using the My Work module. They break user stories down to tasks, and use IDE plugins to integrate their development workflow with ALM Octane.

  5. Team Leaders track progress using the board views and typical scrum workflows.

  6. Testers track acceptance testing on each user story or feature, using manual tests and Gherkin tests.

  7. The DevOps Admin and Developers use the Pipeline module to track pipeline runs and analyze pipeline failures.

  8. At the end of a release, the Team Backlog module is used to conduct a comprehensive retrospective.

Back to top

See also: