Agile Methodology: from concept to practice

Have you ever heard of “agile methodologies” or “agile management”?

These terms are already quite common in the technology field, but they are becoming more and more present in the daily routine of other areas of activity, such as business and marketing.

Before we understand more about this set of practices, it is important to know its origin. Back to the 80s, agile management was already being discussed, as the market was in demand for innovation, greater productivity, and better quality in the delivery of software projects. But it was only in 2001 that the expression “agile methodologies” gained notoriety, when a group of 17 individuals came together in Utah, USA, and created the “agile manifesto”.

This manifest has its construction based on four values:

1. People and their interactions over processes and tools;
2. The operation of the software above the documentation;
3. Collaboration with the client above negotiation and contract;
4. The ability to respond to changes above a pre-established plan.

But anyway, what is agile methodology?

Agile methodology is a set of practices that seek to offer more agility, flexibility, and efficiency when doing tasks and projects.

Because it is structured in short cycles, and with each new cycle new pre-determined functionalities are delivered, it is possible to rapidly identify uncertainties related to the project, prioritize demands and respond quickly to changes.

We can say that these practices are characterized by making frequent and fast deliveries, providing greater satisfaction to customers, since they monitor and participate closely in the development cicle.

How to apply this methodology?

There are several methods already recognized in the market and that can be used by you and your team. In this text, we will present the Scrum method.

Scrum is a framework that can be used for simple and complex projects. Created by Ken Schwaber and Jeff Sutherland, this method of work comes from short cycles of activities within a project. Each cycle is planned and is called Sprint, which includes a list of tasks to be performed in a predetermined period.

In this methodology, there is the participation of some important roles, such as the Scrum Master and Product Owner, who seek to enhance teamwork and follow the evolution of the product or solution constructed. Below, we can check how to implement this method in practice:

1. Define the team

The first step should be focused on building a multidisciplinary team (and defining their roles) that is capable of meeting all stages of the solution’s development.

2. Organize the Product Backlog

This step aims to define the deliverables and features of this particular product or solution, with priorities being listed.This step is the Product Owner responsability, and the items must be prioritezed. 

3. Plan the Sprints

Understanding what must be delivered, it is time to plan the Sprint.s for work. Define which activities will be carried out in the Sprint, what will be its duration, and who will be responsible for each activity. At this step we have a cerimony called  “Sprint Planning” and all team members are required to participate. Is recomended that all Sprints have the same duration period.

4. Make the process visual

Organize the process in a way that facilitates its monitoring and development. Visual aid can be a great ally.

Tip: Try management tools as Rally, Azure DevOps, Confluence and others

5. Do Daily Meetings

Hold daily meetings, as they are essential for planning the day and identifying what deserves more attention. Daily meetings are important to make sure the team is on track.

6. Be clear

It is important to build a clear relationship with the team about all the processes involved and the status of the activities, assuring that the best advantage of the Scrum method is taken and that continuous improvements can be made and the best way to do it is by doing what it’s called “Retrospective”.

Retrospective is a cerimony from Scrum that enforces Scrum pillar’s, Inspection, Adaption and Transparency. In this cerimony the team talks about what went well, what went wrong in the previous sprint and create action plans to improve the upcoming Sprint. 

When reading texts about the subject, it is clear that the Scrum method was built for technology projects, but from my own experience, I can say that this methodology can also be implemented in other areas. In marketing, for example, it can be used in the development of a campaign or content planning for your brand.

Anyway, as with any change, the implementation of agile methods does not happen overnight, but this can potentially be one of the best ways to stand out in the market.

How about implementing it in your company? We hope you enjoyed the reading.

Featured Image from Freepik.