- Case studies
Cycle Control is a solution designed to scale Agile practices and enable coordination and visibility across multiple teams and sprints. Cycle Control gives managers the ability to accurately forecast the completion date of their releases based on the execution progress, thus enabling teams to take corrective actions in advance.
Create and manage repeatable and reliable processes for different teams and departments using stages, quality gates, milestones, checklists and others. The release scope (content) can be any combination of Projects and versions or components, Agile Boards, sprints or Epics without disturbing how individual teams manage their work.
Release Calendars are the central place where releases are visualized. Users can analyze metrics and progress to determine the release status and risk indicator. Users can define multiple calendars, for example one can include all releases for a department, while another can contain all emergency releases. A Master Enterprise Calendar can be used to drive and coordinate all company initiatives.
Who it is for
Do you want to have visibility beyond the current iteration, for the whole release, across multiple teams? For Scrum Masters, Cycle Control enables creation of metrics and goals across multiple Agile boards, Epics, and sprints.
Program and Project Managers
Do you want to drive your programs and projects using the process you choose? Do you want to collect the data you need automatically? For Program and Project Managers, Cycle Control allows creation of custom processes using staple PM building blocks. Automatically evaluating all deliverables, quality conditions and metrics, the process engine provides you with precise information regarding progress and status.
Are all releases conforming to the company quality standards?
What are the pending activities before moving one step closer to production?
Cycle Control allows you to implement and automatically monitor the desired quality standards. Features like trends and progress give you full control over the deliverables and release status.
IT and Engineering Managers
What and when do your teams need to deliver?
What is the next goal for your team?
Cycle Control gives you quick view across deliverables for multiple releases, metrics and trends to enables efficient execution.
In Cycle Control, the scope is defined as the aggregation of issues that represent the work to be done by the teams involved. Cycle Control rolls-up the deliverables of any team that manages their work in JIRA, regardless of their type (Agile or traditional). Cycle Control gives you the ability to define the scope by using Jira Projects, Boards, Epics, Sprints, and Filters.
Use Metrics to continually tune the release management process, help monitor the development schedule and provide both managers and developers with the data needed to improve quality.
Cycle Control provides you with the ability to measure multiple metrics for a release, creating a history that can be mined and audited to provide a reliable way to assess risk.
Release type and release management
A Release Type represents a common definition of a release process including the stages of development and maturity of a product ranging from its initial development to its eventual release to the customer.
In order to create releases you first must have a Release Type describing the common process to be used by a release.