Agile & What is Agile Software Development?

---

Agile is the ability to create and respond to change, representing a fundamental aspect of Business Agility. It is a way of dealing with, and ultimately succeeding in, an uncertain and turbulent environment. The authors of the Agile Manifesto chose "Agile" as the label for this entire concept because it encapsulated the adaptiveness and response to change that was crucial to their methodology.  

It’s really about understanding your current environment, identifying the uncertainties you face, and figuring out how to adapt as you progress.  

Agile software development encompasses more than just frameworks like Scrum, Kanban, Extreme Programming, or Feature-Driven Development (FDD). It includes a range of Agile methodologies, practices such as pair programming, test-driven development, daily stand-ups, sprint planning, and iterations (sprints).  

Overall, Agile software development serves as an umbrella term for a set of frameworks and practices rooted in the values and principles articulated in the Agile Manifesto and its 12 Principles. By approaching software development through this lens, it’s beneficial to adhere to these values and principles to determine the most effective actions tailored to your specific context.

One thing that separates Agile methodologies from other approaches to software development is the focus on the people doing the work and how they collaborate. Solutions evolve through collaboration between self-organizing cross-functional teams utilizing the appropriate practices for their context, as emphasized in the Agile Manifesto. The Agile software development community places a significant focus on collaboration and the self-organizing team. This doesn’t mean there aren’t managers; rather, it signifies that teams have the autonomy to determine their approach independently. These teams are cross-functional, ensuring that all necessary skill sets are present when they come together. While managers still play a crucial role by ensuring team members possess the right skill sets and creating an environment conducive to success, they typically allow teams the freedom to decide how to deliver products, stepping in only when teams face unresolved issues. 

When teams and organizations begin their journey into Agile development, they often concentrate on the practices that enhance collaboration and work organization, which is beneficial. However, another vital aspect that is frequently overlooked involves specific technical practices that directly address software development under uncertainty. These technical practices are essential for achieving Business Agility and should not be underestimated.

Ultimately, Agile is a mindset informed by the values and principles of the Agile Manifesto. These values and principles provide essential guidance on how to create and respond to change, as well as how to handle uncertainty. The Agile Manifesto encapsulates the core idea with its first sentence: “We are uncovering better ways of developing software by doing it and helping others do it.”

When faced with uncertainty, try something you think might work, gather feedback, and make adjustments as needed while keeping the Agile values and principles in mind. Allow your context to guide which frameworks, practices, and techniques you implement to collaborate effectively with your team and deliver value to your customers.

If Agile is fundamentally a mindset, then what implications does that have for Agile methodologies? To explore this question, it’s helpful to have a clear definition of what a methodology entails. 

Alistair Cockburn suggested that a methodology is the set of conventions that a team agrees to adhere to. This means that each team will develop its own unique methodology, which may differ in various ways from the methodologies of others. 

Therefore, Agile methodologies are essentially the conventions that a team selects to follow, all while aligning with the Agile values and principles to enhance business agility.

When you want to understand Agile business analysis, consider asking, 'How might we perform business analysis in a way that aligns with the principles of the Agile Manifesto, enabling us to create and respond to change while managing uncertainty?' The Agile Alliance and the International Institute of Business Analysis (IIBA) have explored this question through their collaborative effort to develop the Agile Extension to the Business Analysis Body of Knowledge, which is available to Agile Alliance members. 

These concepts exemplify efforts to extend Agile methodologies beyond software development, contributing to the emerging Business Agility movement. 

If you broaden the concept of Agile as a mindset, individuals pursuing Business Agility may ask, 'How might we structure and operate our organization to foster an environment that embraces change and effectively navigates uncertainty?' 

In essence, business agility represents the understanding that for individuals within an organization to truly embody an Agile mindset, the entire organization must support and adopt that mindset. True Agile software development only emerges when an organization adjusts its structure and operations to thrive in an uncertain environment.