As part of my New Year’s Eve tradition, I always reach out to my friend Carlos, who was once my employer more than ten years ago. Despite no longer being colleagues, we’ve managed to maintain a tight-knit friendship, despite our jam-packed lives and chaotic timetables frequently clashing with one another.
Out of nowhere, I received a call from Carlos, which was quite unusual given his usually packed work routine. However, this time it wasn’t just a casual chat, as he was curious whether I had any knowledge about the “Agile methodology”.
As the narrator observed, Carlos seemed to be oblivious to the fact that the Agile methodology has established itself as one of the most well-known and impactful methods of software development in the past twenty years.
I agreed, fascinated by the unfolding story. It turned out that Carlos was the owner of a company that is constantly looking to enhance and grow its operations. Consequently, he took up the recommendation of a consultant to implement Agile methodology for their sales team.
To be honest, I was initially unsure about the concept of a sales team incorporating Agile methodology principles like sprints, scrums, and iterative development. At first, I had trouble fully grasping the concept.
I contemplated, “Is it achievable?” Could we apply Agile principles to our work, even if it doesn’t relate to engineering, and would it be effective?”
The Origin of Agile
I believe that it’s crucial to first comprehend the fundamental principles of Agile before we can appropriately tackle this issue. Agile is not just a set of methodologies, but rather a mindset and philosophy that governs the management of software and engineering projects.
Agile emerged as a response to the drawbacks that arose from utilising the conventional waterfall method for software development. It was created by a group of developers who identified these issues and devised alternative solutions.
They acknowledged that their occupation demanded a flexible approach, prioritising the user, maintaining an open mindset regarding methods, and an emphasis on attaining the intended results.
At the start of the new millennium, the initial attempt at Agile had two primary objectives:
- To mitigate the potential for stagnant development and maximise the speed at which customers can experience the benefits of your work.
- The objective is to obtain user feedback swiftly to allow for refinement and improvement of the product.
Eventually, these developers produced a manifesto explaining the four fundamental principles of the Agile methodology:
- People and their connections are more important than machines and their applications.
- Functional software should be prioritised over meticulous documentation.
- Collaboration with the client is favoured over legal negotiations.
- Adjusting to new situations rather than adhering to a fixed timetable.
Adopting Agile Practices
The cornerstone of project success relies on our interactions with both coworkers and end-users, with a primary emphasis on placing value on interpersonal connections rather than relying entirely on technical solutions.
Collaborate closely with your fellow software developers, engage with your clients, and prioritise outcomes over methods. Your collective knowledge will yield a more accurate evaluation of the task at hand compared to a generic, theoretical approach.
It is crucial not to discount techniques; instead, they should be used as a wellspring of inspiration rather than blindly adhering to them. Techniques are a valuable resource in the creative process, although many artists rely more on their intuition than any specific method. Both the developer and I share this viewpoint.
While it is conceivable to extend this idea to other situations, we frequently become overly dependent on established processes and neglect any changing circumstances.
Instead of solely focusing on end outcomes, managers evaluate their performance based on how well they follow a predetermined set of processes. This emphasis on sticking to a specific approach may lead salespeople to neglect the needs of their clients. In both instances, tactics have been given greater importance than interpersonal relationships.
Secondly, prioritise your attention on the product itself. Instead of producing comprehensive documentation to account for every conceivable scenario, strive to develop software that is self-explanatory. Both the developer and user will benefit from not needing to read through an excessive amount of documentation, saving valuable time.
To guarantee that our products are appropriate for our clients, we must design them according to their requirements rather than our own preferences or overlooking how they will be used.
A significant number of flight reservation systems still operate through a console, which necessitates that travel agents remember a variety of codes and inputs for the booking process. Although reference material is available, it may not be appropriate for all personnel, as the requirements may be better suited for those with a background in computer programming.
If I were to apply this idea to other situations, my main priority would be on the speed and ease of use. It is crucial to remember that customers may not have the same level of experience or understanding as we do, so it is essential to ensure that we offer appropriate guidance and support to help them acclimate to our way of thinking. Click here to learn more about making an accessible app for the visually impaired.
When aiming to make a sale, it is crucial for salespeople to communicate the product clearly using language that their clients can comprehend. Price should be the primary topic of discussion when speaking to those considering a purchase, while the long-term benefits should be discussed with the decision-maker.
When discussing the third principle, a major problem with the Waterfall approach is that the user is frequently overlooked. A set of criteria is usually defined in the initial stages, and feedback is given at the end. As a result, the user often spends a considerable amount of time waiting for the outcome.
Users must be considered not only as potential revenue streams but also as valuable contributors to the development and expansion of a product. All departments in a company should take customer and user feedback into account and act upon it.
It is no longer necessary to cling to the idea of an “expert.” Although we may possess certain information that customers may be unaware of, knowledge is exchanged between both parties. Customers and users offer us unique insights into the company, the market, and the requirements that we may not have.
The fourth principle is evident: in today’s fast-paced environment, customers demand swift service since the market is constantly dynamic, and we could be left behind if we take too long to respond. The capability to adapt swiftly is critical in this situation.
Regrettably, life is too uncertain for us to be able to anticipate what will happen and plan accordingly. Instead of worrying about whether a project will fail, my colleague suggests that we concentrate on the potential outcomes.
When met with challenges or changes in the market, it is crucial that we possess the ability to adapt quickly and efficiently. Enhanced flexibility will provide us with the best chance of successfully overcoming any obstacles that emerge.
Plans are useful for outlining a vision for the future, but they are not a strict set of instructions. The plan serves as a guide, indicating the proper direction to take. However, we ultimately determine how to move forward.
Expanding Beyond the Techniques
Initially, I had reservations about introducing agile practices to other countries since I was fixating too much on the particulars of its execution. However, in accordance with the principles of true agility, we should not merely assemble a sales team and implement Scrum without any contemplation. Instead, we can utilise these concepts as a foundation for devising new methods for each sector in accordance with its unique needs.
In brief, the principles of Agile are just as relevant outside of software development as they are within it.
