A real world example on how to build an application layer by layer, using Scrum, simple design and emergent architecture.

Software rot describes the decay at which a software project deteriorates over time. This can be experienced in various ways: reduced performance, increase in bugs and increased difficulty at pushing out new features. A multitude of project failures can be attributed to software rot. If you’ve been a professional

When implementing agile there is a lot of focus on reorganizing the teams into feature teams, implementing practices such as Continuous Integration and Continuous Delivery, incorporating automated unit tests and regression tests… There isn’t much focus on the Product Owner, we assume that he will present User Stories that

While using Git you'll probably end up using stash a lot, and if you do you'll probably end up losing a stash by mistake. Fear not, Git has ways of recovering lost stashes, or commits. For demonstration purposes, let's lose a stash. First, I'll show some work in progress so

The velocity is the cumulative value, in story points, that a team has accomplished during a sprint. In an experienced team, this velocity will be stable and can easily be used to forecast a release. Take a look at this example chart: ![Stable velocity chart](https://raw.githubusercontent.com/ippontech/

Original Author: Florence Herrou [](https://raw.githubusercontent.com/ippontech/blog-usa/master/images/2015/03/dessinEmpereur.png)Emperor Drawing ** ** The last monthly meeting of Agile Nantes  (presented by Agile Garden) was titled The  Emperor’s New Clothes