Posted over 11 years ago. Visible to the public. Linked content.

Kanban vs. Iterative Development — Agile Web Operations

If you need big synchronization points, e.g. for big marketing campaigns, you might be better off using an iterative development approach. If you want to ensure a continuous flow of features, which are optimized for time to market (cycle time), Kanban might work better for you.

Your development team has a full backlog of feature requests, chores and refactoring coupled with deadlines? We are familiar with that. With our "DevOps as a Service" offering, we support developer teams with infrastructure and operations expertise.

Owner of this card:

Last edit:
almost 11 years ago
development, agile
About this deck:
We are makandra and do test-driven, agile Ruby on Rails software development.
License for source code
Posted by Lexy to makandra dev
This website uses short-lived cookies to improve usability.
Accept or learn more