INDUSTRY WIRED

  Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Agile methodologies have long been praised for their ability to increase team collaboration, break down silos, empower decision-making and project management, and more. With roots in product development, the agile methodology was later adopted in the nineties by software engineers who were experimenting with different approaches to software development. Today, you can find agile ways of working in many industries outside of IT. From agile marketing to agile HR, it seems that the agile methodology has something to offer everyone.

  Every technology organization today seems to practice the agile methodology for software development, or a version of it. Or at least they believe they do. Whether you are new to agile application development or you learned software development decades ago using the waterfall software development methodology, today your work is at least influenced by the agile methodology. Agile was formally launched in 2001 when 17 technologists drafted the Agile Manifesto. They wrote four major principles for agile project management, to develop better software: