#TestCulture πŸ¦… Episode 1 β€” The foundations of the Agile method

3 min readJan 30


In 1986, Ikujiro Nonaka & Hirotaka Takeuchi, two academics who observed companies such as Toyota, defined 3️⃣ categories of companies:
πšƒπš’πš™πšŽ 𝙰 companies, such as NASA πŸš€, which divide work into well-defined phases and do not move on to the next phase until the previous one has been completed.
πšƒπš’πš™πšŽ 𝙱 companies, where the phases overlap slightly, based on the observation that it is conceivable, for example, to start the architecture when 80% of the specifications have been completed.
πšƒπš’πš™πšŽ 𝙲 companies where everything is done at the same time, like in a rugby scrum.

The term 𝐚𝐠𝐒π₯𝐞 appeared in the English-speaking business world in the early 1990s. In 1991, James Martin based his vision on the continuous evolution of computer techniques and proposed a π‘šπ‘’π‘‘β„Žπ‘œπ‘‘ for rapid application development. ✍

πŸ’‘ If you don’t know who is James Martin:
James Martin is an English consultant and author in information technology. He is known for his work on information technology engineering.

Subsequently, in 2001, a manifesto for Agile Software Development was written in the United States by 1️⃣7️⃣ software development experts. πŸ”Ž Each of these experts had already developed new methods that were lighter than traditional methods inspired by civil engineering. βš™πŸ› 

If agile methods did not appear thanks to this manifesto, it does however officially refer to these methods under the term 𝐚𝐠𝐒π₯𝐞.πŸ€“
The 4️⃣ values of the agile manifesto have been broken down into 1️⃣2️⃣ principles in order to provide operational support to teams wishing to follow them. πŸ’ͺ

The 4 values are:
πŸ‘‰ 𝐈𝐭𝐞𝐫𝐚𝐭𝐒𝐯𝐞: Delivers a full system at the very beginning and then changes the functionality of each subsystem with each new release. πŸ”
πŸ‘‰ 𝐈𝐧𝐜𝐫𝐞𝐦𝐞𝐧𝐭𝐚π₯: The system as specified in the requirements is partitioned into small subsystems by functionality. New functionality is added with each new release. πŸ”ƒ
πŸ‘‰ π’πžπ₯𝐟-𝐨𝐫𝐠𝐚𝐧𝐒𝐳𝐒𝐧𝐠: The team has the autonomy to organize itself to best complete the work items. πŸ“°
πŸ‘‰ π„π¦πžπ«π πžπ§π­: Technology and requirements are β€œallowed” to emerge through the product development cycle. πŸ“ˆ

Agile is currently an umbrella concept encompassing many methods. πŸ“œ Agile methods will not out rule traditional methods because diverse processes for software engineering are still needed. ☝️


Learn more about the foundations of the #Agile method on Agilitest’ blog.



#TestCulture πŸ¦… Episode 13β€Šβ€”β€ŠWhat is continuous testing

2 min read

Apr 24

#TestCulture πŸ¦… Episode 12β€Šβ€”β€ŠWhat is data-driven testing

1 min read

Apr 17

#TestCulture πŸ¦… Episode 11β€Šβ€”β€ŠWeb development jobs

2 min read

Apr 11

#TestCulture πŸ¦… Episode 10β€Šβ€”β€ŠPodcasts on Software Testing to follow

2 min read

Apr 3

#TestCulture πŸ¦… Episode 9β€Šβ€”β€ŠBlog recommendations

2 min read

Mar 28

#TestCulture πŸ¦… Episode 8β€Šβ€”β€ŠDifferent types of tests

2 min read

Mar 20

#TestCulture πŸ¦… Episode 7β€Šβ€”β€ŠBest practices for working on a collaborative project

2 min read

Mar 13

#TestCulture πŸ¦… Episode 6β€Šβ€”β€ŠMine canaries to Canary Releasing

2 min read

Mar 6

#TestCulture πŸ¦… Episode 5β€Šβ€”β€ŠMust-read books for testers

3 min read

Feb 27

#TestCulture πŸ¦… Episode 4β€Šβ€”β€ŠGrace Murray Hopper, or the birth of the term β€˜Bug’

2 min read

Feb 20


Codeless functional testing at scale is now a reality.