↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Overcome Agile hangovers with a 'software craftsman' approach

The article argues that some companies end up with an “Agile hangover” after expecting fast results from Agile without seeing better software quality or better developer skills. It says the problem is often that organizations focus on Agile rituals and still deliver software in the same old way.

It presents software craftsmanship as a way to make Agile stick. Mancuso’s view is that developers should work with care, professionalism, and technical discipline, with attention to customer needs and to the quality of what is actually delivered.

Reading notes
#

  • Many companies adopt Agile with high expectations, but do not see overnight success or better alignment with business needs.
  • The article says some organizations focus on the Agile process itself and neglect software development practices.
  • Mancuso argues that this leaves software late, buggy, and keeps the gap between business and IT.
  • He proposes a craftsman approach that rejects a production-line mentality and returns to the basics of software development.
  • Software craftsmanship is described as a two-way street that can also raise business respect for IT professionals.
  • The approach emphasizes deep attention to customer needs and customer satisfaction.
  • The text links software craftsmanship to the Software Craftsmanship Manifesto, which values well-crafted software, steady value, professional community, and productive partnerships.
  • It says software craftsmanship is not a methodology, but it recommends technical practices and disciplines, especially those associated with Extreme Programming.
  • The article presents craftsmanship as aligned with Agile and Lean principles, while pushing for professionalism, technical excellence, and customer satisfaction.