In a significant move to enhance project management capabilities, Azure DevOps is steadily advancing towards a comprehensive rollout of its New Boards Hub. This transition marks a pivotal moment for users of the platform, as it heralds the eventual retirement of the legacy Boards experience. The Azure DevOps team has set an ambitious target to complete this transformation by the conclusion of the first quarter of 2025, affecting all users of the Azure DevOps service.

The rollout strategy is two-pronged, focusing on both new and existing users. Firstly, the team is working diligently to establish the New Boards Hub as the default interface for incoming users. Simultaneously, for those customers who have already embraced the New Boards Hub as their primary workspace, efforts are underway to transition entire groups to an exclusive New Boards Hub environment, effectively removing the option to revert to the older version.

As of the latest update, significant progress has been made in this transition. A substantial 60% of the Azure DevOps customer base now has the New Boards Hub set as their default experience. Moreover, a pioneering 20% of customers have fully transitioned, operating solely within the New Boards Hub ecosystem without the fallback option to the legacy system.

The Azure DevOps Update Mechanism: A Closer Look

To fully appreciate the intricacies of the New Boards Hub rollout, it’s essential to understand the nuanced approach Azure DevOps takes in releasing updates and new features. The platform employs a sophisticated ring-based release process, which segments the vast Azure DevOps customer base into six distinct tiers or “rings”.

At the apex of this structure is Ring 0, aptly named the canary ring. This exclusive tier is reserved for the Azure DevOps engineering team, serving as the first line of defense against potential issues. Following closely is Ring 1, populated by early adopter customers who play a crucial role in shaping features through their aggressive feedback and early adoption.

The subsequent rings, from 2 through 5, encompass progressively larger customer groups. This gradual expansion ensures that by the time updates reach Ring 5, which represents the broadest audience, they have undergone rigorous testing and real-world usage across various customer segments.

This methodical, ring-based approach is a testament to Azure DevOps’ commitment to quality and stability. It allows for thorough testing at each stage, significantly reducing the likelihood of issues persisting to the later rings. As a result, customers in Rings 4 and 5 rarely encounter problems that haven’t already been identified and addressed in earlier stages.

The Deliberate Pace of Progress

The measured pace of the New Boards Hub rollout is a deliberate choice by the Azure DevOps team. As each new ring is introduced to the New Boards Hub, it invariably leads to the discovery of edge cases and generates valuable customer feedback. This information is crucial for identifying and resolving issues that may not have been apparent in earlier stages.

To capitalize on this feedback loop, the team allows the New Boards Hub to “bake” within each ring for a designated period. This approach provides ample opportunity to address customer concerns and resolve any emerging issues before progressing to the next ring. While this process may seem protracted, it’s a strategic decision aimed at minimizing disruptions and ensuring a smooth transition for all customers.

The Inevitability of Change: Farewell to the Old Boards

As Azure DevOps continues to evolve, it’s crucial for users to understand that the deprecation of the old Boards experience is an inevitability. The timeline for this transition varies depending on which ring an organization belongs to.

For customers in Rings 1 and 2, the shift is already complete, with no option to revert to the old Boards. For those still retaining the ability to switch back, the Azure DevOps team strongly encourages remaining on the New Boards Hub. This not only ensures that user feedback continues to shape and improve the experience but also facilitates a smoother transition for teams in the long run.

Charting the Course: The Road Ahead

Looking forward to early 2025, the Azure DevOps team has outlined clear next steps in the rollout process. The New Boards Hub will become the exclusive experience for the next cohort of customers residing in Ring 3. Concurrently, the remaining 40% of customers in Ring 5 will see the New Boards Hub enabled as their default experience.

As with previous stages, a brief period will be allocated for feedback collection and issue resolution, ensuring a seamless transition. However, the ultimate goal remains clear: by April 2025, all customers are expected to be fully converted to the New Boards Hub, with the option to revert completely removed.

Embracing Change: A Call for Active Participation

In the face of this significant platform evolution, the Azure DevOps team emphasizes the importance of user engagement. Should users encounter any issues with the New Boards Hub, they are strongly encouraged to report them via the official Feedback Ticket system or by directly contacting the team.

It’s crucial to note that turning off the New Boards Hub is not the recommended course of action when facing challenges. Instead, by reporting issues, users play an active role in refining and improving the platform for the entire community. The team values all feedback and sees it as an integral part of the development process.

As Azure DevOps continues its journey of innovation, the New Boards Hub stands as a testament to the platform’s commitment to enhanced project management capabilities. By embracing this change and actively contributing to its ongoing improvement, users can help shape a more efficient and effective project management experience for all.

Read more such articles from our Newsletter here.