Software Craftsmanship in an Agile Environment
In the past two decades agile has become the popular development methodology. Businesses have been rushing to adopt agile processes because it promises to save money and deliver working software more quickly. However, for many businesses, software quality has not improved—and often has gotten worse. In response, some software engineering leaders found it necessary to create the software craftsmanship movement. Why has agile failed to deliver on its promise of higher quality software? What can be done about it? What solutions do these craftsmen offer? Chris McKenzie explains that the core problem is the failure of engineers to properly communicate the value of technical excellence in business terms. Businesses have abandoned cumbersome processes in favor of agile processes including Scrum and kanban. However, the expectation of increased velocity coupled with a failure to understand the technical requirements of supporting increased change mean that agile processes are set against quality. Gain a deeper understanding of the communication failure among business, project management, and technical roles. Learn to address the issue of quality head-on and reap the promised rewards of agile.