Yes, I know. Everybody is recommending books, so, why I will not do the same, right? right…?
Well, yes, I will recommend some books but not new ones, very old ones. I am totally convinced that one of the today’s developers lack is knowing from where our practice come from. There are a lot of new developers arriving and stumbling with many new concepts but, sometimes, those concepts and ideas are not necessary new, or were around for a wile making everybody wondering how to solve it.
Let talk about agility and Scrum. For the new comers that could be the standard paradigm of project management and they will not know anything about waterfall or any other sort of software management attempt.
What happen when you just face these concepts but don’t know the reason behind it? Why we decided to change? What happened before and the necessity for that change? How you will know, if don’t know the past, that thing the facilitator (self-called guru, scrum master or coach) is valid and is not just trying to manipulate you if what they are telling to you sound fresh and original but, actually, is not?
The answer is: THE OLD BOOKS (No religion related)
So, here is my recommendation for three books and a paper that, if you haven’t read it yet, could change your mind drastically.