Back again with another software delivery article! Today we’re going to talk about what a feature and feature flag is in agile software delivery. They’re two distinct things but are related especially if you want to experiment often. We’ll talk about some pros and cons + a few other topics. Regardless of process, time to market, customer feedback and being “nimble” rather than following strict process that slows everything down is an important mantra in my mind.So let’s get to it! What is a feature in agile software delivery? A “feature” refers to a distinct element of functionality that can
Scrumban is a hybrid Agile project management methodology that combines elements from both Scrum and Kanban. It was initially designed as a way to transition from Scrum to Kanban, but has since evolved into a standalone framework that takes advantage of the strengths of both systems. Here’s a brief overview of each, to provide context: What are some general benefits of scrumban? Does Scrumban use Velocity or Cycle & Lead Time? In Scrumban, key performance metrics from both Scrum and Kanban are used, with more emphasis on Kanban’s flow-based metrics like Cycle Time and Lead Time rather than Scrum’s Velocity.
For today’s article I’ll talk a little about change failure rate and what it might mean to your organization. I cover it ever so briefly in the DORA metrics article I posted a while back. I’ll go a bit more in depth here today. What is change failure rate? Change failure rate is a metric used in the software delivery process to quantify the percentage of times a change, such as a new feature, bug fix, or configuration update, results in a negative outcome, such as a degraded user experience, system outage, or rollback. This metric helps organizations understand the