Feedback on Agile Software Development
Inside the tech scene, using an agile methodology has established itself as the primary mode of organization. This takeover was not made without resistance, a good illustration is the conference by Erik Meijer One Hacker Way which begins with the punchline agile is a cancer that we have to eliminate from our industry. Another example is the talk Agile is dead by Dave Thomas or The death of Agile by Allen Holub.
According to them the business made around this method, the use of many buzzwords and a certain heaviness in the setting up are the principal concerns. Even if this judgment can sound pretty hard, these concerns are mostly true, however the benefit you get makes those minor discomforts less important.
Agility emerged as a series of best practices and can be found in the Manifesto for Agile Software Development published in 2001 by a group of programmers. This manifesto consists of 4 values and 12 principles. In order to apply these values and principles, different frameworks are available. It can be extreme programming, kanban, scrum or others. Scrum was originally a wrapper around extreme programming. But over time it has become the most popular, which is why we will focus on this framework.
In this article, we will see how to operate on a daily basis, with this agile method, now well implanted in modern businesses.
