Translated from Português (Brazil) • View original Agile methodology is the set of practices that provide a way to manage projects that are more adaptable to changes. They are structured in short cycles, and with each new cycle, a predetermined set of features is delivered. Because it is a truly innovative approach to project management, capable of increasing interactions, making processes more efficient, and streamlining workflow, the agile methodology has been adopted by different teams and areas of activity. Agile is not only about speed, but also about flexibility and integration. That's why agile project management adapts to sudden changes in planning, such as: changing priorities, postponing tasks, and changing project characteristics as needed. How does this type of methodology work? Agile methodologies were created by a group of software developers who were looking for a better approach to the traditional development process, as it was very complicated and bureaucratic due to the amount of documentation requirements. Agile methods have emerged in the Information Technology industry to solve problems common to almost every organization or company that needs to manage projects. Some agile methodologies are: Scrum; Feature Driven-Development (FDD) and Scaled Agile Framework (SAFe). Steps within an agile methodology The first step involves the Concept. Prioritizing projects so that you can work together with your team and stakeholders to brainstorm, identify business opportunities, and calculate deadlines and costs to complete each project. Right after comes the Conception part. In this step, after being able to determine what your project will be, the next step is to figure out how you will complete it. Who are the people you need on your team? What are the initial customer requirements? Create a table with all these points and organize them well. Now comes the Iteration part. You already have your initial project defined and approved, so your employees can start the necessary activities in the way they want. Arriving at this stage is the Launch. After several iterations, the time comes when you can launch a final product. During the launch phase, it is recommended that you perform final tests and quality assurances to identify errors and defects. Here you are practically at the end of the methodology, Production. Your product is now in the market in question. Your team will provide continuous monitoring and support to keep everything running smoothly and ensure that users know how to use the system. Differences between agile and traditional methodology The traditional methodology is a good option in more specific cases within the company, for example in something that needs planning and that is decided from the beginning. If the project has little chance of having changes and with low risk, the ideal is to have a more detailed project plan before starting. In agile methods, they are indicated for situations where the focus is to anticipate as much work as possible.