DEVOPSdigest

Split announced Statuses and Rollout board, two new features that build upon the platform’s management and governance capabilities allowing software development teams to oversee and control feature releases and experiments at scale.

As consumers demand more and more from applications, businesses have faced mounting pressure to expedite their digital transformation and bring innovations to market faster. However, software development teams have struggled to keep pace with customer needs, lacking the control and insight to safely reduce cycle time and deliver impactful features. Split closes this gap with its feature delivery and experimentation platform, enabling teams to rapidly deploy to production, gradually release to target audiences, and measure the impact of each feature on key metrics.

Over the last few years, as enterprises have accelerated their release cadence and experimented with new ideas, feature flags, and the difficulty of managing them within application code, have proliferated. Split has seen its own customers increase their use of feature flags threefold over the past year within its platform. For companies with hundreds to thousands of flags being managed across multiple teams, the burden and risk associated with ensuring all flags are promptly updated and all team members are kept informed increases exponentially. Enterprises need a reliable and efficient way to control and collaborate on their releases end to end. Split’s new Statuses and Rollout board feature streamlines the release process by allowing software development teams to organize and view every flag and experiment at each stage of the feature delivery lifecycle in one place. This gives developers and product managers the visibility they need to seamlessly release new features and collaborate on delivering the best outcomes for their users.

“Our focus has always been helping our customers drive the speed of development, safety of releases, and business impact,” said Matthew Cordasco, VP of Product at Split. “However, achieving all this for large enterprises introduces numerous challenges and complexities such as security, compliance, and process management. Split is uniquely positioned to solve these challenges. We have unparalleled data privacy, we were first to market with approval flows, and now we are the first to introduce a visualized workflow designed to manage feature delivery at scale. We’re excited to see how our customers leverage Statuses and Rollout Boards as they continue to create new flags and experiments.”

Statuses indicate a feature’s stage in the release process. Split users can simply assign a status to a feature flag when configuring and updating its targeting rules. Flags can then be filtered by status to see what features reside in each stage, from pre-production to controlled rollout to fully released in production. Rollout board visualizes flags by status and displays metadata essential for determining appropriate next steps such as the number of days since the status was last updated, traffic received across environments, and outstanding alerts and change requests.

The benefits of Statuses and Rollout board include:

- Streamline feature delivery: Ensure flags are always up-to-date to avoid forgotten flags and delays, and quickly determine next steps required for any given feature.

- Enable efficiency at scale: Easily manage multiple feature releases and experiments across teams in a central location.

- Reduce technical debt: Safely and promptly retire feature flags once features are fully released and prevent unused flags from accruing in application code.

Statuses is now generally available to all Split users. Rollout board is only offered on Split’s Platform edition.