Agile development methods have gained acceptance among mainstream software development since the late 1990s, when they were first postulated in the form of Scrum, Crystal, Extreme Programming, and others . Today they have been established at various levels in the software development, professional learning and training community. While there is much to learn by examining what software developers create and measuring software failure-proneness, we can gain insights through direct interaction with software developers. We can learn about the development of their businesses, their perception of the development process and how the two interact. [1]2. Agile OverviewBefore the 1990s, waterfall is a common software development but has its own problems as it assumes that all project requirements can be gathered at the beginning of the project. It seems like an impossible mission, because during the development process there are many problematic influences external and internal to the project, for example the customer's desire to change some features of the product or the developer abandoning the project. Therefore, agile software development was born to solve problems arising from previous software development. In the late 1990s, the word "agile"[2] in the field of computer systems meant "ready ability to move with quick and easy grace" or "able to move your body quickly and easily." However, this word begins to have another meaning in February 2001. A group of seventeen software developers gathered in Snowbird, Utah, and determined that agile software development is common ground on which they can agree each participant has the own ideas on how to build high-quality software. Results of a common agreement from...... middle of the document ......methodologies are an important part of information technology There are several software development methodologies and agile development methodologies are one of them. Agile development methodologies are a good method for software development. It has the ability to develop systems with unclear user requirements and short timescales excellently. However, no specific methodology stands out as the dominant method. It also has weaknesses as it is not suitable for unknown technologies and complex systems. To survive and grow, a methodology must be able to learn from other methodologies and adapt to changing customer needs. This report is an overview of agile development methodologies and some of the common methodologies in agile development methodologies. It also provides examples of successful projects and ongoing projects based on agile development methodologies.