Evolution of Agile Framework

You must have heard about Agile Scrum Master Certification, but do you really know what it really is? Agile and Scrum are a segment of the Lean Six Sigma Green belt certification. To become a master in your profession and take your career higher, this training is only the first step to it all.

This blog further explains the evolution of the agile framework in a brief:

The first notable thing to mention is that Agile didn’t start with… well Agile. Many of the frameworks that sit under the Agile umbrella are more than two decades old, and the term “agile” to define a new way of developing software emerged from existingframeworks (some as experiments, some long-lived already) that needed a new definition, or a new category for them to fit together.

In the ’30s, Walter Shewhart (physicist and statistician with Bell Labs), looked into the process and products improvement with the PDSA Cycles (Plan-Do-Study-Act)

In the 1950s, the X-15 hypersonic jet was built using iterative and incremental development, and the practice was considered a key for the success of the jet.

In 1986, Hirotaka Takeuchi & Ikujiro Nonaka wrote an article in HBR – The New Product Development Game – which presented a “rugby approach” to product development: “where a team tries to go the whole distance as a unit, passing the ball back and forth.”, with an emphasis on speed and flexibility.

Agile Scrum Master

1990 to 2001

In 1992, Allistair Cockburn created the Crystal Framework. Cockburn probably set the stage for the agile movement, with this set of frameworks that are characterized by simplicity, teamwork, communication, and continuous improvement.

In 1993, used rapid application development, object-oriented design, PDSA cycles, and skunk work to create a new product for Easel Corporation, and dived into learning and research on how to make a team reach maximum productivity. Scrum was born, and presented to the public in 1995, by Sutherland and Ken Schwaber.

In 1995, Scrum was made public and software development in pairs was written about independently – but at the same time – by two engineers: Jim Coplien wrote  “Pattern Languages in Program Design” one of the organizational patterns being “developing in pairs“; in “Constantine on Peopleware”, Larry Constantine reports about seeing “Dynamic duos” writing code faster in one of his projects. Both authors state that programmers working together to write the same piece of code is the sure path to more efficiency, faster learning, and higher code quality.

2001: The Agile Manifesto

“On February 11-13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and try to find common ground—and of course, to eat. What emerged was the Agile ‘Software Development’ Manifesto. Representatives from Extreme Programming, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming, and others sympathetic to the need for an alternative to documentation-driven, heavyweight software development processes convened.“, from the history of the Agile Manifesto.

All the above practices, frameworks, and learning set the stage for the creation of the Agile Manifesto. The manifesto signatories came up with the word “Agile” to encompass the traits exhibited by the above frameworks and practices after much discussion but in full agreement.

Now that you have learned about the history of agile, it is important for you to understand the relationship between agile and scum altogether. MindCypress is here to help you out, complete your Agile Scrum Master certification, and watch your career touch the skies. Contact us today!