We love a good debate about the individual merits of each development method as much as the next product development team. Whether you’re a die-hard Agilist or you’re more into Scragile, Scrummerfall or Wagile what matters in this age of continuous delivery is that you have a means to foster collaboration and keep teams aligned and iterating–fast. Our Director of Business Intelligence, Eric Nguyen, weighed in on this article in TechTarget.
Continuous delivery is not a software development methodology per se. It is a practice — or rather, a series of practices — of developing and testing software in a way that lets organizations quickly issue updates anytime.
Many software developers and testers see it as a natural outgrowth of Agile development. They are not wrong, but a broader definition is more accurate. What really prepares a software team to take on continuous delivery is solid experience with any form of iterative development. “There is a tendency to pigeonhole methodologies,” said Eric Nguyen, director of business intelligence at Jama Software, a company that sells requirements and test management software. But how a software team defines itself — Scrum, Agile, KanBan — doesn’t matter, said Stephen Forte, chief strategy officer at tool maker Telerik. “They are all adapting toward continuous delivery.”
What does matter is a mind-set that says, “Be more iterative,” Nguyen said. Whether you’re scripting tests, writing and testing code, or defining a business problem, “you are breaking things down into smaller and smaller [pieces],” he added. And that is ultimately what continuous delivery is all about.