Agile Scrum Evolution Timeline Overview

Agile and Scrum have evolved from specific product development theories into a global standard for project management. While Scrum predates the Agile Manifesto by several years, it has become the most widely adopted framework within the Agile umbrella. 

Agile Scrum Burn down and Burn up charts – can be downloaded from website banner

Evolution Timeline

  • 1986: The Inspiration. Hirotaka Takeuchi and Ikujiro Nonaka publish “The New New Product Development Game” in Harvard Business Review, introducing the “rugby” approach to product development.
  • 1993: The First Scrum. Jeff Sutherland and his team at Easel Corporation implement the first official Scrum.
  • 1995: Public Presentation. Ken Schwaber and Jeff Sutherland formally present Scrum at the OOPSLA ’95 conference, introducing the concept of Sprints.
  • 2001: The Agile Manifesto. 17 software developers meet in Utah to sign the Manifesto for Agile Software Development, codifying the 4 values and 12 principles that define Agile.
  • 2002: Scrum Alliance Founded. The Scrum Alliance is established by Ken Schwaber, Mike Cohn, and Esther Derby to provide training and certifications like the Certified ScrumMaster (CSM).
  • 2009: Founding of Scrum.org. Ken Schwaber founds Scrum.org to provide a more consistent approach to Scrum training and assessments.
  • 2010: The First Scrum Guide. Sutherland and Schwaber publish the first Official Scrum Guide, providing a definitive, minimal definition of the framework.
  • 2011–2017: Iterative Refinements. Updates to the Scrum Guide clarify the Daily Scrum purpose (2013) and emphasize Scrum Values (2016).
  • 2020: The “Simplified” Guide. The latest 2020 Scrum Guide is released, focusing on making the framework less prescriptive and more applicable to non-software industries by removing technical jargon. 

Key Shifts in Scrum Maturity

  • Prescriptive to Descriptive: Early Scrum was highly prescriptive about meetings and roles; modern Scrum focuses on Empiricism (Transparency, Inspection, Adaptation).
  • Team Autonomy: The 2013 update pivoted from “selecting tasks” to focusing on the Sprint Goal, empowering teams to decide how to achieve the objective.
  • Scaling Frameworks: As organizations grew, frameworks like SAFe (2011) and LeSS (2013) emerged to apply Scrum across hundreds of teams.
Plan On a Page POaP for an Agile Scrum project, available for download above
Unknown's avatar

Author: Mark Whitfield

Welcome to my site! After graduating in Computing in 1990, I accepted a position as a programmer at a Runcorn based software house specialising in electronic banking software, namely sp/ARCHITECT-BANK on Tandem Computers (now HPE NonStop). This was before the internet became more prevalent and so the notion of enabling desktop access to company accounts for inter-account transfers and book keeping was still quite a cutting edge idea (and smartphones only ever hinted at in Space 1999). The company was called The Software Partnership (which was taken over by Deluxe Data in 1994). I spent 5 years in Runcorn developing code for SP/ARCHITECT for various banks like TSB, Bank of Scotland, Rabobank and Girofon (Denmark) to name but a few. I then moved onto a software house in Salford Quays for further bank facing projects. After a further 23 years in the IT industry and now a Senior IT Project Manager (both Agile and Waterfall delivery), I thought I would echo out my Career Profile in this corner of the internet for quick and easy access.

Leave a comment