10 Top Programming Methodologies

In 2001, seventeen software developers made history by signing the Agile Manifesto. Since then, agile software development has taken off; in fact, in a 2015 Forrester report, 54 percent of enterprises surveyed said that more than half the development teams at their organizations were using agile methodologies. The Agile philosophy is based on twelve core principles that emphasize short iterations, continuous delivery, simplicity, retrospection and collaboration between end users and developers.

Image source: Agilemanifesto.org

Agile software development comes in many flavors, and Scrum is one of the most popular with 70 percent of respondents to the 2015 State of Agile report saying that they practice Scrum or a Scrum hybrid. It's a framework for collaboration that was first invented by Jeff Sutherland in 1993. It divides complex projects into short two- to four-week sprints, and it emphasizes the values of courage, focus, commitment, respect and openness.

Image source: SCRUM.org

Although lean development is commonly associated with agile, the principles of lean actually arose from Toyota's lean manufacturing processes. This development methodology relies on seven key principles: eliminate waste, increase feedback, delay commitment, deliver fast, build integrity in, empower the team and see the whole. Lean first came to the attention of the software development community in 2003 with the publication of Mary and Tom Poppendieck's book "Lean Software Development: An Agile Toolkit."

Image source: Guy Nirpaz, GigaSpaces Technologies, Introduction to Lean Software Development, http://www.slideshare.net/nirpaz/introduction-to-lean-software-development

Another variation of agile software development that was inspired by Toyota, Kanban gives developers a visual way to see what work needs to be done and allows them to "pull" in work as they have capacity rather than "pushing" them to complete certain tasks. It relies on three core principles: visualize what you do today, limit the amount of work in progress and enhance flow.

Image source: https://en.wikipedia.org/wiki/File:Simple-kanban-board-.jpg

Over the years, several different approaches to software development have used the RAD name. The best-known is probably James Martin's methodology, which was created at IBM in the 1980s. It can be considered a form of agile, as it emphasizes the ability to adapt to changing requirements and de-emphasizes upfront planning.

Test-Driven Development is related to both agile software development and extreme programming. Developed by Kent Beck and others, this process requires developers to write a test for any new feature before starting the coding process. It encourages developers to write a minimal amount of code.

Image Source: https://github.com/mjhea0/flaskr-tdd

This form of agile software development relies heavily on pair programming. Like other agile methodologies, it emphasizes rapid iterations and frequent requirement changes. It was created by Kent Beck, who was one of the signatories of the Agile Manifesto and published a book called "Extreme Programming Explained: Embrace Change" in 1999.

Image Source: JD Meier's Blog, Microsoft Developer Network, https://blogs.msdn.microsoft.com/jmeier/2014/06/06/extreme-programming-xp-at-a-glance-visual/

This software development methodology is named for the company that invented it—Rational Software, which IBM purchased in 2003. While some programming methodologies are very rigid, the Rational Unified Process aims to be easily tailored to unique situations. It's an iterative framework that relies heavily on visual models.

Unlike the other software development methodologies in this slideshows, the waterfall model is sequential rather than iterative. It was the most common method of software development from the early days of computing until very recently. It is best suited to small-scale projects where all of the design requirements can be known upfront.

Image Source: Paulsmith99 at en.wikipedia