History of Agile

1. History of Agile
By Alexander Paul Gaigole

2. History of our Jobs

3. We were Hunter Gatherers

4. Then we were Farmers

5. Then …
https://en.wikipedia.org/wiki/Lists_of_people_by_occupation

6. Number of professions
28, 275 Occupation Names are registered
In the Ministry of Labor

7. We’d Improve by Specialization

8. In early 1900’s,
We decided to further in specialization:
Thinkers and Doers

9. Managers and Workers

10. Venetian Arsenal – around 1104 to 1554
The earliest example of :
• Standardized Design
• FLOW Production
• Assembly line
Galleys creation was reduced
to an Hour thru a narrow
channel

11. Interchangeable Parts – 1700s
Eli Whitney, 1798 contract to produce 10,000 stands of arms
The interchangeable parts used in the creation of the
Muskets were cited as one of eth main reasons for North
victory in the civil wars.

12. Scientific Management - 1911
Frederick Winslow Taylor
Frederick Taylor’s four principles of Scientific
Management are:
1. Develop a science for each element of work
2. Scientifically Select, Train, Teach and
Develop the worker
3. Cooperate with the Worker
4. Divide the Work and
Responsibility
Another key tenant of the book
being the removal of
wasteful activities

13. Motion Efficiency
Frank Bunker Gilbreth
• Motion Study
• Process Mapping
Lillian Moller Gilbreth
• Workplace psychology

14. FORD - Manufacturing Line - 1910
Brought together the basic unit
elements of any organization:
• People
• Machines
• Tools
• Products
Was also a promoter of Just In Time
production.
The Model T became an iconic vehicle
becoming the most widely sold car very
quickly making Ford very wealthy.
But the assembly line had one inherent
problem, it was unprepared for

15. Decentralization with coordinated control
GM under Sloan is known for stratifying car makes according to market
segment. "A car for every purse and purpose," said Sloan. Chevrolet was the
volume car for the working masses. Pontiac came next, then Oldsmobile,
then Buick. Top-of-the-line Cadillac introduced innovations such as electric
starters and offered luxurious prestige to those who could afford it.
Socioeconomic status and consumer aspirations stepped upward with the
GM brands.
Alfred Sloan

16. Training Within Industry
(TWI)

17. TWI helped win the WWII
With a gun to their heads (literally),
the TWI founders had to find solid
principles of human nature that
• Work every time
• Inspire dedication
• Create performance results
• Build leadership
• Strengthen teamwork

18. Impact of TWI on the WAR Effort
Of the 600 client companies monitored by the TWI Service
throughout the war:
• 86% - increased production by at least 25%
• 100% - Reduced training time by 25% or more
• 88% - reduced labor-hours by over 25%
• 55% - reduced scrap by at least 25%
• 100% - reduced grievances by more than 25%

19. TWI goes to JAPAN
Toyota embraced TWI in 1951 to train their people in the evolving Toyota Production System and remains a
cornerstone of their leader training and standard work today
Mr. Taiichi Ohno

20. POST WAR JAPAN
Joseph M. Juran
William Deming Henry Ford
Kaoru Ishikawa Henry Ford

22. HBR – The New New Product Development
Game (1986)
Having observed teams at companies like Honda, 3M, Epson and Canon, they pulled together what they
considered key attributes of successful teams working on new products. “Like a rugby team”, they wrote, “the
core project members at Honda stay intact from beginning to end and are responsible for combining all of the
phases.”

23. Agile History Timeline
On February of 2001, seventeen people
met to talk about Agile. What emerged
was the Agile 'Software Development'
Manifesto
Dynamic Systems Development
Method (Agile delivery
Framework)
Feature Driven Development
(Agile Modeling)
Hirotaka Takeuchi 1986 1993 Jeff Sutherland, Jeff McKenna, John Scumniotales

24.  In the early 1990s, software development faced a crisis. Industry experts estimated that
the time between a validated business need and an actual application in production
was about three years
 Within the space of three years, requirements, systems, and even entire businesses were
likely to change. That meant that many projects ended up being cancelled partway through,
and many of those that were completed didn't meet all the business's current needs, even
if the project's original objectives were met
 In certain industries, the lag was far greater than three years. In aerospace and defense, it
could be 20 or more years before a complex system went into actual use. The Space Shuttle
program, which operationally launched in 1982, used information and processing
technologies from the 1960s
 In1990s, several technology leaders frustrated with these long lead times and decisions made
early in a project that couldn't be changed late, began informal talks about ways to develop
software more simply, without the process and documentation overhead of Waterfall and
other popular software engineering techniques of the time
Agile History
24

25. Agile Manifesto
25
Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.

26. Scrum Origins
• Jeff Sutherland
• Initial scrums at Easel Corp in 1993
• Coined term Scrum
• Ken Schwaber
• Scrum presented at OOPSLA 95 with Sutherland
• Author of three books on Scrum
• Jeff & Ken
• Creators of Scrum Guide
• Mike Beedle
• Wrote “Agile Software Development with Scrum” with Schwaber
• Ken & Mike Cohn
• Co-Founded Scrum Alliance in 2002
• Setup the Certified Scrum Accreditation series

27. References
• https://www.youtube.com/watch?v=LIMcTm8pA5A
• https://www.slideshare.net/kiroh/tps-lean-and-agile-brief-history-
and-future