Software Craftsmanship

Throughout the career we have studied we have seen different methodologies to develop software, we even find ourselves with the dilemma of understanding the difference between a methodology and a framework (as agile is). Personally I believe that this framework of good practices to develop software more efficiently, quickly and with better teamwork, has been a total innovation in our area.

I totally agree with the author when he mentions about the craftsmanship of the software, because it is, no software is a copy of another because we are always producing new things and each programmer puts a little of his part, his essence, and the way he solves Problems when programming are part of the way you think, the way you express yourself, that makes software art.

Imagine for a moment return to the development of traditional, sequential software, with PMI. The requirements of our customers, today more than ever, constantly change. The technologies we work with are evolving day by day, the people we serve are and suddenly no longer, the business needs change day by day adjusting to the market, the ecosystem, the economy. Then what do we do? Are we still developing software unable to adapt? Do we cancel the projects at the moment they become useless? All these questions are solved with the implementation of this new way of developing software: agile. A framework that focuses on giving greater concentration to the client and that says "changes are welcome" allowing that, even at late stages of the project, changes are accepted in order to meet the needs of the client or end users who will use the system.

Personally I am very fan of this type of software development and I have even certified in Scrum methodology with ScrumStudy and IBM Agile courses because I think it is a fairly successful framework for the shortcomings of software development.