Q&A: The Evolution of Feature Management and Experimentation
Split caught up with guest speaker Chris Condo, Principal Analyst at Forrester, to talk about what’s changed from the earlier days of feature management.

Learn Why Agile Businesses Use Split
Deliver software features that matter, fast!
renderContent(deleteTreatment) { const allowDelete = deleteTreatment.treatment === "on"; return ( <div className="todoListMain"> <div className="header"> <form onSubmit={this.addItem}> <input ref={(a) => (this._inputElement = a)} placeholder="Enter Task" ></input> <button type="submit">Add</button> </form> </div> <TodoItems entries={this.state.items} allowDelete={allowDelete} delete={this.deleteItem} /> <TodoItems entries={this.state.items} allowDelete={allowDelete} delete={this.deleteItem} /> </div> ); }
"You’re not really doing Agile" is a pretty bold claim. How do teams turn that around?
“Agile” is all about constant iteration and getting information back about whether or not what you delivered is actually working. One of the cycles that we see taking hold is this practice where a business leader or a product manager says, “I’ve got an OKR. I’ve got an objective and key result. I want to move the needle on something.”
It was interesting to get Condo’s perspective on the latest industry movements, including trends in trunk-based development, testing in production, and the introduction of causal analysis. Most notably, we agreed that measurement and learning capabilities, like experimentation and impact monitoring, are heating up.
Schedule a Split Demo Tailored to Your Needs
Speed up development cycles, reduce release risk, and focus your team on DevOps best practices that create maximum impact.
Create Impact With Everything You Build
We’re excited to accompany you on your journey as you build faster, release safer, and launch impactful products.