Cycle Control 4.0.0: Team dependencies at scale & customisable terminology


For those of you who are not familiar with Cycle Control for Jira, it is a powerful application designed to solve one major challenge – how to take the immense success of agile practices and scale them for multiple teams? Cycle Control enables organizations to fill the gap between managing a single team and a portfolio by rolling-up the data of any initiative that’s been tracked in Jira, and effectively monitor, track, and forecast its progress and status. The tool enables managers to quickly align and coordinate multiple teams using real-time data while achieving a balance between enterprise governance and team autonomy.

For those of you who are familiar with Cycle Control, we have a couple of surprises in store for you. Last week we officially released version 4.0.0, which includes two new features – team dependencies and customizable terminology.

Identify & resolve risky dependencies between teams, or external for the initiative parties

While agile development methods and the breakdown of complex tasks were initially developed to improve small-scale development, they are increasingly adopted by large-scale development organizations with globally distributed teams. In such settings, the agile breakdown of complex tasks poses a significant challenge due to complex dependencies between teams in large initiatives. As a rule, the complexity of these dependencies only increases with the size of the company, and in large-scale software development, the challenge, therefore, becomes how to minimize technical dependencies that have a negative impact on team performance, as well as how to enable communication and management of dependencies between teams.

How do we solve this challenge? Well, we think we’ve nailed it with the Cycle Control Dependency Detection feature.

Cycle Control Dependency Detection enables you to quickly identify and resolve risky dependencies either between teams or with external for the initiative third-parties. While the individual teams identify the dependencies, managers can easily monitor them and help mitigate in details if and when conflicts and risks do arise.

The major advantages of the Cycle Control Dependency Detection feature are:

– True enterprise governance with retained team autonomy: dependencies are identified and tracked by the teams in Jira, the release manager only monitors and detects them.

– Greater visibility: easily identify all dependencies for the initiative and monitor dependencies across teams.

– Risk-based analysis & grouping of dependencies: surface the dependencies that, based on your experience, have the highest potential to cause problems. Having exposed these dependencies, you as a release, project or program manager can allocate enough time to resolve them.

– Data-driven company transformation: Cycle Control Dependencies analysis can help you drive a transformation inside your organization and make your teams more effective and productive by discovering bad practices, work patterns causing dependencies, and areas for improvement in the way your teams function and are organized.

Customize the application’s terminology to fit your company processes

One of the significant challenges that we have experienced during demonstrations of Cycle Control is lack of common dictionary – our solution uses pre-defined, out-of-the-box terminology, that until recently, wasn’t open to changes or customizations. This challenge had a more significant impact on our customers – every organization uses different terms for universal concepts, e.g., what some teams refer to as a “release” is called a “program” in other organizations.

Cycle Control has always prided itself as a tool that adapts to the needs and work processes of its users, not forcing its users to adapt to the tool. This was the primary driver behind the development of a custom terminology feature – this new capability offers an unparalleled intuitive experience by allowing users to change the terminology throughout the entire application interface. This feature will enable teams to be in full control of their environment, set the terms which are used in their everyday work, and match their specific businesses processes. The new terms will replace the default terminology throughout Cycle Control’s menus, labels, gadgets and native integration.

What are the major benefits of this new capability?

– Intuitive user experience: aligning the terminology of a product as complex as Cycle Control enables users to more efficiently and intuitively navigate through the environment.

– Adapted to your work process: users no longer have to adapt to the pre-defined terminology of the tool that might be foreign for the users. This new feature helps teams adjust the terms to their existing work processes.

– Quicker adoption: introducing any new solution to your existing stack of third-party applications requires a period of adaptation or even training for users. Cycle Control’s custom terminology ensures easier and quicker adoption by removing one of the more major obstacles.

Want to give it a try? Update, or head out to our marketplace listing.