{"id":13482,"date":"2021-10-06T10:21:40","date_gmt":"2021-10-06T13:21:40","guid":{"rendered":"https:\/\/www.neomind.com.br\/?p=13482"},"modified":"2021-11-09T11:04:53","modified_gmt":"2021-11-09T14:04:53","slug":"agile-methodologies","status":"publish","type":"post","link":"https:\/\/www.neomind.com.br\/en\/blog\/agile-methodologies\/","title":{"rendered":"Agile methodologies: everything you need to know"},"content":{"rendered":"\n

First, before we understand what agile methodologies are all about, we need to realize that every task has to be, somehow, completed.<\/p>\n\n\n\n

Sometimes the assignments we have are so easy to handle that we don\u2019t even bother about organizing our time or coming up with techniques to facilitate their execution. On the other hand, there are more complex situations where we feel lost and it\u2019s hard to even tell how to start dealing with a given task.<\/p>\n\n\n\n

Now imagine that you are part of a development team and you have several items coming from a backlog, and that you need to discuss with your peers a practical, optimized solution to carry out all those assignments.<\/p>\n\n\n\n

Okay, I have this challenge of tasks that have to be done\u2026 What now?<\/strong><\/p>\n\n\n\n

Now, the agile methodologies will help you to complete your activities, no matter their complexity level, and basically enable you to make double the work in half the usual time.<\/p>\n\n\n\n

To start doing that, you\u2019ll need to gather your team and learn what are the actual tasks to be executed that are on your radar. Usually, agile methodologies are implemented in the company by the PO (Product Owner) or Product Manager \u2014 who represents the final user\u2019s needs and who, along with the development team, can list those activities. Before implementing any given methodology, tough, you must have at least a basic understanding of each of the most common ones.<\/p>\n\n\n\n

And what would be the main agile methodologies?<\/strong><\/p>\n\n\n\n

Scrum<\/a><\/em><\/strong><\/h2>\n\n\n\n

It\u2019s one of the most popular existing methods. To utilize it, you need to have a good overall understanding of your team, so you can define, in detail, the role that each member will play out during the actual, practical undertaking of the tasks.<\/p>\n\n\n\n

In this methodology, it\u2019s also important that someone takes responsibility for the customers\u2019 needs, leading meetings with enough knowledge to sort each task\u2019s priorities and understand their related features.<\/p>\n\n\n\n

These meetings, where the direction that the team will take to develop each backlog item is set, are called Planning<\/em>. From there, items that will be developed are sent to a Sprint<\/em>, which may last up to four weeks.<\/p>\n\n\n\n

At the end of each Sprint<\/em>, the team reviews everything that was done and what needs adjustment. Then, a new sprint <\/em>begins and so on until all pending backlog items are concluded.<\/p>\n\n\n\n

Kanban<\/em><\/strong><\/h1>\n\n\n\n

It\u2019s a methodology where everything that\u2019s being done is sorted visually to improve understanding.<\/p>\n\n\n\n

The simplest, most efficient divisions of this format are made up of three parts:<\/p>\n\n\n\n