Is Scrum or Kanban Better for Continuous Deployment?

Originally published at www.scalablepath.com by Veronica on February 5, 2020.

Over the years, software teams have had to learn how to evolve with their changing industry, not only with emerging architectures, technologies, and frameworks, but with newer approaches to development altogether, like Continuous Deployment. In this agile movement that we find ourselves in, the ultimate goal is to minimize the time between the moment we take on a task and the time we release it into the production environment.

Continuous Deployment allows teams to release each feature when ready as opposed to grouping them together for a final release, creating a more efficient development process. However, for teams that use Scrum — like Scalable Path — continuous deployment throws some fundamental Scrum concepts (like sprints and retrospectives) into question. It also puts into question whether there are other — more suitable — project management frameworks to use in this context. In this article, we’ll look at whether Continuous Deployment impacts the Scrum process and consider how an alternative project management tool like Kanban may offer solutions to Scrum’s shortcomings.

Continuous Deployment is becoming a popular development approach. Today, it represents an important competitive advantage for companies and there are…