Beyond the buzzword: see Agile in action! Immerse yourself in real-world scenarios and discover how this approach transforms projects and delivers results.
The Agile Manifesto was introduced in 2001 and with it came an entirely new way of thinking about the software development process. Today, agile is adopted as the mindset and methodology of choice among development teams. Even other types of businesses are adopting agile methodology as a way to put people and products first.
But while agile methodology certainly has several benefits, it can be challenging to implement in many environments. How do successful companies do this? How can these obstacles be mitigated?
What is agile?
Agile is a mindset and an approach to the software development process. Originally, it was considered a successor to the Waterfall methodology, which was commonly used before the introduction of agile. Waterfall is now considered less flexible. This is especially so because of how often requirements change and developers and team members need to rethink their processes.
Agile is based on the Agile Manifesto, which consists of 12 principles that focus on continuous software improvement and collaboration. The principles also prioritize customer satisfaction – in fact, this is the first principle – and flexibility in the development process. Even late in the process, developers should welcome changes to requirements.
The Manifesto also highlights the importance of providing high-quality, functional software, as well as keeping all stakeholders informed and involved throughout the process. The entire methodology aims to guide the team and adapt to a constantly changing scenario.
Agile in practice: a case study
Multinational banking company Barclays sought to streamline its efforts and become a more effective global services organization. On the company blog Jonathan Smart, Head of Ways of Working, discusses how the bank adopted an agile approach to promote flexibility and engage teams.
In 2015, Barclays began the process of adopting agile practices, but as Smart notes, “there is no end date: it’s about being the best at being better, and it’s a never-ending journey.” Still, he reported that the company had significant data showing work items and problems being resolved in half the time and at 50% of the cost, leading to better overall results.
The customer-centric philosophy, he notes, has many benefits, including the ability to get feedback faster.
According to Smart, agile doesn't just apply to Barclays' technology departments. The company's Internal Audit area, for example, also adopted the mentality. Before they did so, auditors worked on many audits simultaneously, which led to process inefficiencies and a lot of switching between projects. Adopting agile methodology has resulted in less work in progress, fewer concurrent projects, shorter completion times, and an overall reduction in waste.
While acknowledging that “it’s a big mindset shift,” Smart encourages leaders to work with their teams to drive buy-in, equipping them with a mission to accomplish and helping them collaborate to achieve it.
5 traps to avoid
For teams to truly follow agile effectively in the real world, they must be aware of common pitfalls associated with the mindset.
1. Failure to get buy-in from the company
Agile depends on collaboration. To achieve it, leaders must involve everyone involved in the methodology. Change isn't easy, especially when you've been doing things one way for a long time. The process takes time and it is necessary to appeal to people's interests. As you begin the agile implementation process, keep employees informed about the why and how behind the decision. Also ask for their opinion – because this depends on collaboration, team members will be essential in making change happen.
2. Ignoring the role of talent
Often, the skills of the individuals who make up an agile team are overlooked. If you want your products to be successful and your customers to be satisfied with their results, it's critical to ensure you have diverse skills on your team and fill any gaps that exist. Think beyond technical or hard skills – agile also requires soft skills like communication, problem solving and, of course, collaboration.
3. Lack of planning
It's true that agile is a highly flexible methodology that encourages developers to respond to changes in requirements and other process elements, not avoid them. It’s about “going with the flow”, so to speak. But that doesn't mean that the software development process doesn't still need planning.
Planning is crucial for integral elements of the development process, such as:
Budget
Requirements gathering
Schedule Estimates
Onboarding team members involved in the project Although you may deviate from the original plan, it is still a critical part of Agile.
4. Forgetting about scalability
Your first agile project probably won't be your last. Furthermore, this initial project could be a rudimentary or less sophisticated version of what is to come, like an MVP. Consider how your organization can grow quickly and also how your products can be improved. If you're starting out with a department or a few teams, think about how agile can be successfully incorporated into other aspects of your organization, like Barclays has done.
5. Communication problems
Strong communication is critical to agile development. If you haven't established clear channels and methods of communication with team members, customers, and other stakeholders, both the process and the end result will suffer. Initially, organizations must determine how they will communicate, in terms of methods and frequency, to prevent these problems from occurring.
This is true for co-located in-person teams, but it's even more critical for distributed teams, which don't have the benefit of sharing a workspace. Agile has revolutionized the way we deliver software. When organizations successfully adopt the mindset, it means better products, happier customers, and more efficient and productive teams.
