Agile

Agile is a group of methodologies for flexible project management within a development team. This approach breaks the workflow into short timeframes, also known as sprints (from the English word ” sprint ” meaning “short-distance running”) or iterations. During each sprint, the development team creates a portion of the product that can be tested and evaluated. This approach allows for significant changes to be made to the project, even while development is in full swing.

For example, the team has already designed the interface for a new online cinema, which includes a player, a preloaded movie catalog, selections based on user viewing history, and even facial recognition technology. When a new iteration begins, it becomes clear that users are missing the ability to recognize soundtracks directly within the player, as they don’t want to open Shazam while watching a movie. The team begins developing and implementing this feature in the next phase of development.

Agile’s principles are the complete opposite of another development approach—Waterfall. It structures product development according to a different logic:

• preparation of complete technical specifications;
• design;
• development;
• testing;
• final result.

Development processes in this methodology cannot be rolled back; the team returns to previous stages only if something is malfunctioning and not working according to the specifications. Because of this, problems with the product (app, website, software) are discovered relatively late—only during the testing phase—and the resulting product may completely fail to meet the client’s expectations or not function as intended.

Types of Agile Methodologies

Agile is a general term for several methodologies united by the idea of ​​flexible work. This group includes various methods, such as:

• Scrum. This methodology works in iterations. All tasks necessary for completing a product are compiled into a special list—the backlog—and the customer plays a key role in determining the product’s type and functionality.
• Kanban. It emphasizes visualizing tasks on boards and streamlining workflows. Kanban teams strive to reduce project time and improve efficiency.
• Extreme Programming is based on practices such as pair programming, test-driven development, and continuous integration, which is the constant addition of new elements to the main project.

Agile principles

The Agile approach to development is based on several principles:

• People and interactions are more important than processes and tools. Therefore, the methodology is suitable for both small startups and large corporations. It doesn’t matter where communication and tasks are taking place—in a Telegram chat or a task manager—the key is that all participants understand the project’s goals and are aware of what’s happening at the current stage.
• A working product is more important than comprehensive documentation. This principle allows Agile development to begin faster—from the very first stages, instead of creating extensive technical specifications, prototypes are created and tested to validate hypotheses.
• Collaboration with the client is more important than negotiating contract terms. Agile development requires active client participation, so it’s not suitable for clients who aren’t prepared to delve into the work, dedicate sufficient time to the project, and experiment.
• Being open to change is more important than sticking to the original plan. This principle is the foundation of agile development. It’s impossible to plan everything perfectly in advance, and some brilliant ideas come as you work on a product. Agile allows you to focus on the tasks that matter most now and avoid wasting resources on thinking two or three steps ahead.

How an Agile team works

• product owner;
• project managers;
• UX designers;
• technical writers;
• developers (the type of developer depends on the project profile);
• testers.

Moreover, even a person in the product owner position is not formally a manager; they simply take responsibility for formulating product requirements: they convey to the rest of the team a vision of what the product should look like and what functionality it should have.

Cross-discipline collaboration is essential in Agile teams. Experts need more than just their own expertise; productive collaboration requires an understanding of how their colleagues work together. When designers understand how to calculate the developers’ workload, and developers understand the purpose of certain elements in a mockup without explanation, the team works more effectively.

For example, at Netflix, work is organized using the Agile methodology. The streaming service’s vast workforce is divided into multiple teams, and each employee has their own area of ​​responsibility, ensuring the quality of their work. Each team focuses on solving problems in its own subject area, but collaboration is encouraged when additional tools shared by multiple development teams are needed.

How to implement an Agile approach

When transitioning to a new model, companies may make mistakes:

• fail to provide training to employees;
• fail to take into account the specifics of development;
• fail to take into account the financial aspect of the company’s restructuring;
• Use only some of the methods that will not work on their own.

To implement Agile, you can gradually test the methodology on small groups. First, launch a first wave of Agile teams, and evaluate their performance based on financial metrics, efficiency, and reorganization investment. If all indicators show positive dynamics, the experiment can continue.

It’s important to remember that the reorganization will affect several parties, so training and preparation will need to be carried out not only with the team but also with clients. Some clients may not be ready for the level of involvement required by Agile.

Briefly about the main thing

• Agile is a group of methodologies for flexible project management in a development team.
• With this approach, the work process is broken down into small time periods, also called sprints or iterations.
• Scrum is a methodology in which all tasks necessary to complete a product are formed into a special list – a backlog.
• Kanban is a methodology that emphasizes visualizing tasks on boards and optimizing the workflow.
• Extreme Programming is based on practices such as pair programming, test-driven development, and continuous integration.
• The Agile approach to development is based on the principle that “People and interactions are more important than processes and tools.”
• Cross-discipline is important in Agile teams.
• To implement Agile, you can gradually test the methodology on small groups.