Picture this scene from three years ago: Employing the corporately mandated processes, a software engineering team is delivering system updates about once every nine months. When their senior user suddenly demands the next delivery in twenty-two weeks-half the current cycle duration-the team realize that they must quickly change development practices. Mathew Bissett describes how Her Majesty's Government did precisely that-and much, much more. First, they reduced delivery cycles from unpredictable dates every nine months to predictable releases every six weeks. Then, they cut releases cycle time to once every week. By identifying and mitigating risks early in the work intake process, enforcing quality gates, executing multiple test levels concurrently-and more-they dramatically increased throughput with the same or better quality. Today, these new processes provide their teams the best balance of structure versus agility.

One principle architects employ when designing buildings is "form follows function." That is, the layout of a building should be based upon its intended function. In software, the same principle helps us create an integrated design that focuses on fulfilling the intent of the system. Ken Pugh explores congruency-the state in which all actions work toward a common goal. For example, as Ken sees it, if you form and promote integrated teams of developers, testers, and business analysts, then personnel evaluations should be focused on team results rather than on each individual’s performance. If you embrace the principle of delivering business value as quickly as possible, the entire organization should focus on that goal and not the more typical 100% resource utilization objective. If you choose to have agile teams, then they should be co-located for easy communication, rather than scattered across buildings or the world.

Agile practices have proven to help software teams develop better software products while shortening delivery cycles to weeks and even days. To respond to the new challenges of cloud computing, mobility, big data, social media, and more, organizations need to extend these agile practices and principles beyond software engineering departments and into the broader organization. Adaptive leadership principles offer managers and development professionals the tools they need to accelerate the move toward agility throughout IT and the enterprise. Jim Highsmith presents the three dimensions of adaptive leadership and offers an integrated approach for helping you spread agile practices across your wider organization. Jim introduces the “riding paradox” and explores the elements of an exploring, engaging, and adaptive leadership style.

In many development organizations today, quality is the responsibility of everyone on the project-both developers and testers. However, getting devs fully engaged in this testing continues to be a challenge. Andrew Prentice describes two approaches-blitz testing and mentored testing-that help Atlassian’s developers gain the skills they need to improve code quality before the testers get their hands on the application. He shares how they structure and organize blitz tests-group test sessions, the various roles participants play in them, and how to foster their viral adoption. Andrew also describes mentored testing, including its potential risks and mitigation options. He examines the skills and tools testing teams need to implement these techniques with their devs.