Adopting Agile Practices

Agile software development is in a rut. Agile is consistently misapplied, misunderstood, misused, and then, all-too-often abandoned. Worse than that, many popular agile methods are not actually agile. They've remained largely unchanged for more than a decade. And despite preaching inspect and adapt, users adopt and forget, following practices by-the-book and suffering when a practice conflicts with their local context. Join Andy Hunt as he describes the GROWS™ Method—a new approach to software development. The GROWS™ Method is based on four key ideas—the Dreyfus Model of skill acquisition, evidence-based practice, inclusivity, and local customization. The Dreyfus Model speaks to limitations in human cognition and problem solving. Evidence-based practice is a framework for first-class experiments that encourage us to make decisions and answer questions with actual outcomes—not wishful thinking or popular folklore. Inclusivity includes more of the organization than just the developers, and local customization makes adaptation to individual environments a first-class part of the method. It’s now time to grow software development beyond the limitations of agile.

Software processes are commonly portrayed using machine metaphors in which consistency is highly prized. Frequently, organizations set up Centers of Excellence in a well-intentioned effort to create enterprise consistency. Steve Adolph reminds us that, in reality, software development takes place in a diverse ecosystem of corporate policies, competing interests, personal agendas, personality types, and a variety of formal and informal relationships. An aggressive top down imposition of practices is like sending a bulldozer through an ecosystem. This can create a prized consistency, but it also can destroy the environment’s productive vibrancy. It does not matter if the bulldozer says waterfall or agile on the side—it’s still a bulldozer. How do we live in harmony with our ecosystem? We can start by replacing machine metaphors with biological ones about leveraging and embracing diversity. Then use these metaphors to interpret two case studies of how organizations either bulldozed their ecosystem or learned to boost their productivity by living in harmony with it.

Agile practices can be the easy part of agile, but getting people into the agile mindset can be a real challenge. Do you have a team member who doesn’t quite support agile or someone who’s playing along but not really committed? One step toward obtaining real commitment is a better understanding of why agile works, why it’s different, and when it is the right approach. In this fast moving session, Perry Reinert provides a fun look at some of the theory that gets to the core of why agile works. Yes, we really can use the words fun and theory in the same sentence! Combining parts of the Agile Manifesto, Empirical Process Control, and Cynefin, Perry leaves you wondering how anybody can choose not to use these methods! After explaining the why, Perry connects the dots from that theory to some of the agile practices. Finally, he wraps up with a discussion of common ways to screw it all up—and how not to.

This is the story about the Microsoft Developer Division and their two-year journey to agile—from shipping every three years to shipping every three weeks. In the old days, long stabilization phases were part of its DNA. Managers were rewarded for micromanagement. Commitments were made months in advance. Maintaining the appearance of meeting commitments was valued over transparency. Gregg Boer shares how this organization within Microsoft transitioned to one that values agile principles—controlling technical debt, enabling teams, eliminating bogus commitments, and rewarding transparency. When applying agile to such a large, traditional organization, the key to success is allowing autonomy at the team level, while ensuring alignment with the organization. Gregg shares successes as well as colossal failures. Learn how management sets direction while teams own their own backlog, how communication up and down can be transparent and healthy, and other lessons on their journey to agile.