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 ...

An agile company is able to move forward despite a roadblock or pivot when an idea isn't working. Having adaptable employees helps make these transitions smoother and increases the likelihood of ...

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, ...

This content is contributed or sourced from third parties but has been subject to Finextra editorial review. When we talk 'agile' there are a few big issues that I notice, especially from management ...

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 ...

This is the seventh and final installment of the “A” Word, Emily Truax’s series of articles on Agile. The rest can be found here, here, here, here, here and here. Since we started our Agile rebranding ...

One of agile development’s core principles is to deliver working software at the end of every sprint. Teams accomplish this by defining robust user story acceptance criteria, committing to the sprint ...