The Agile Manifesto, which lays out 12 principles for agile software development, was written in 2001, a time when many people were still using dial-up internet. While these principles still influence ...

A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...

Nobody likes bureaucracies, least of all software developers. All good software starts with a spark of innovation and a notion of design, and red tape has a nasty habit of stifling that spark. That’s ...

The traditional model for software development is the waterfall approach, where development “flows” downward like a waterfall through six phases: analysis, design, implementation, validation testing, ...

Lately, the term "continuous" has popped to the top of vendors' and pundits' lists as the software architecture we all should and want to have. The problem is that many assume "continuous" means rapid ...

Any developer on a team that practices Scrum, XP, Kanban or Lean-based software development methodologies should be familiar with the Agile Manifesto and the Agile principles it espouses. But not all ...

AgileFall is an ironic term for program management where you try to be agile and lean, but you keep using waterfall development techniques. It often produces a result that’s like combining a floor wax ...