Hi, thanks for all the responses. They were that I could handle, and although I read them at once as soon as they came, I wanted to read them again to understand the full context. So, thanks for all!

About «we could probably write a book»: yes! And the name is «Refactoring by Martin Fowler». For me this book was game changing, and gave a new perspective for all the things that I studied in the CS degree. And yet, more than 20 years later most of CS degrees do not talk about that...

About Agile, may be the greater thing is adaptability. In fact, was one of the names proposed for Agile before Agile had name. Lean if you want. Basically is keep being smart and question everything. If you project needs deep thinking and planning, then you change your way of work to adapt to the new situation (you have been Agile because you changed from one way to the other). And so on. And about the now long distat and long article in the background, about dividing stories, just what I said in the end, step by step, reviewing the result. Often retros are the most hated meetings, but that happens because a lot of rigid people gides them. Thanks to retros we can be Agile, test new things and think about how well are we doing (a new article topic?).

Sooo, Thanks Again!!