Luisa Sepulveda wrote:Are the agile practices really good for the quality in the development?
Agile practices can certainly help improve quality of software but it really boils down to the people who develop the software. Good quality software can be produced by teams using non-agile practices. Likewise, poor quality software can be produced by teams who claim to use agile practices.
Agile practices focus on creating tighter feedback loops between the end users and the people who develop the software. By aligning the development team's interests more closely with the people who will eventually use the software, many of the things you do in Agile methodologies are done to give the team the ability to produce higher quality code. Practices like test-driven development and Pair Programming focus on constant review of the code that's being written to make sure that bugs are found as close to the time they're injected as possible. Developing iteratively and having users involved in your feature/user story prioritization process helps to make sure that you're building what the users expect. Much of what a team does in adopting agile is about quality. It might not seem that way at first glance, but in many ways that's one of the major advances that Agile practices bring to teams that pay attention the principles behind the practices.
We talk a lot about how Agile practices bring about high quality software in Learning Agile.
Author, Learning Agile
Time flies like an arrow. Fruit flies like a banana. Steve flies like a tiny ad:
create, convert, edit or print DOC and DOCX in Java