1Software Architecture in the Agile Life Cycle, by Diego Fontdevila and Martín Salías; published in The Architecture Journal, Issue 23, 2010.↩

2“Software Architecture in Practice”, 3rd edition, Len Bass, Paul Clements, Rick Kazman, SEI Series, Pearson, 2013.↩

3The Definition of Done is a set of criteria that an Agile Team agrees upon to consider a Backlog Item completely “Done”. This typically include things like committed to source code, all unit, integration and regression test passed (probably executed by the Build Server), and some other important validation or tasks the Team consider important for the product they are building.↩

4Weirdly enough, the latter was agreed to be the most important issue in that project, as this was the third attempt at solving the same problem, and the pressure had burned the teams on the previous attempts.↩

5http://agileforall.com/patterns-for-splitting-user-stories/↩

6Explained at Martin Fowler’s bliki: https://martinfowler.com/bliki/TechnicalDebt.html↩