Skip to main content

Agile Software Development Timeline

A Timeline by definition is an iterative document - it is incrementally built minute by minute with no known completion point. However the historical entries on the time line might be elaborate also. This is a rough draft... please comment with new (better - more important, more accurate) events. Or point me to better resources - other historical time lines etc.  Thanks!

Watch Earth's history on a 100yd football field timeline.

Agile Software Development Timeline

1202 Fibonacci introduces Arabic numerals (0-9 and place value) to the West via book “Liber Abaci” (Book of Abacus or Calculation).  The Zero is born!

1950s Demining teaches in Japan

1960s NASA’s Project mercury uses test-first development and micro-increments

1971 The Psychology of Computer Publishing by Gerald Weinberg - largely ignored

1976 EVO Methodology by Tom Gilb

1980s Japanese car companies expand into Europe & Americas

1986 New New Product Development by Takeuchi & Nonaka

1986 No Silver Bullet by Fred Brooks - advantages of Incremental & Iterative Development

1987 Peopleware by deMarco & Lister

1988 Iterative delivery described by Tom Gilb in Principles of Software Engineering Management

Software Patterns

Pair Programming - organizational patterns described by James Coplien

1990 The Machine that Changed the World by Womack & Jones

1990s Object-oriented Programming

1990s Schwaber uses early Scrum at Advanced Development Methods
1990s Sutherland uses early Scrum at Easel Corporation
1990s Internet
1990s Dot-Com Boom

1994 Book:  Agile Competitors and Virtual Organization: Strategies for Enriching the Customer

1995 DSDM consortium publishes version 1.

1995 Scrum Methodology paper by Sutherland & Schwaber

1996 Lean Thinking  by Womack & Jones

1996 Journey of the Software Professional: The Sociology of Software Development
By Hohmann

1996 Beck creates XP at Chrysler Comprehensive Compensation System (C3)

1997 Feature-Driven Development (FDD) by Jeff De Luca

1998 Extreme Programming by Kent Beck on wiki

1998 Crystal family of methodologies by Alistair Cockburn

1999 Java Modeling in Color with UML by Peter Coad  - Ch 6 describes FDD.

1999, Extreme Programming Explained by Beck

1990s Crystal Clear by Alistair Cockburn

1999 The Pragmatic Programmer: From Journeyman to Master by Hunt & Thomas

2000 Adaptive Software Development: A Collaborative Approach to Managing Complex Systems by Highsmith

2001 Agile Manifesto Signed - Feb in Snowbird Utah

2001 Agile-Testing Yahoo! Group started

2001 Agile Software Development with Scrum by Schwaber & Beedle

2003 Lean Software Development by Poppendieck

2004  Watir released

2004 Agile Project management with Scrum by Schwaber

2005 Fit for Developing Software  by Mugridge & Cunningham

2006 BDD article by Dan North in Better Software Magazine

2006 RSpec released

2006 Selenium released

2007 Kanban introduced

2007 Scaled Agile Framework by Dean Leffingwell

2008 Cucumber released

2008 Robot Framework open sourced

2008 Slim update to Fitnesse

2009 The RSpec Book by Chelimsky & Astels

2009 Software Craftsmanship Conference

2009 DevOps :: Dev and Ops Cooperation at Flickr 10+ Deploys Per Day! (Talk at Velocity 2009)

2011 PMI introduces Agile Certified Practitioner

2011 Mob Programming begins at Hunter - Woody Zuill

2014 Schism in community of Scrum over techniques of scaling to enterprise

2016 Manifesto for Agile Company Development by Matt the Agile Coach

See Also:
The timeline in the Evolution of Scrum - 3Back

Timeline of Long Distance Communication

A Perspective on Time by
51 Most Popular Tech Gadgets through the Years - Popular Mechanics

Cartographies of Time: A Visual History of the Timeline
A chronology of one of our most inescapable metaphors, or what Macbeth has to do with Galileo.

4 Billion years of Technology


Elisabeth Hendrickson, Quality Tree Software, Inc.
Agile, Testing, and Quality: Looking Back, Moving Forward.  Oct 28, 2009
History of Agile S/W Development
Timeline of Computer Science  150 major events (via MIT) from 300BC to now

Here's the Timeline of the Universe... it may be a bit long...
Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.


Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.  

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?

Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.

Metrics for a Scrum Team (examples)

What metrics do you collect to analyze your scrum team?

We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignoring the intangible obvious signals (read Honest Signals by Sandy Pentland of MIT).
What if …