Concepts
Understanding the historical development of Scrum and Agile methodologies provides an essential context to better grasp the core principles of Agile and Scrum practices, which indeed are a critical part of the Advanced Certified ScrumMaster (A-CSM) exam study syllabus.
I. The Genesis of Agile
The Agile methodology was born out of a need to address software development processes that were rigid, heavy-handed, and often led to project failures. The 1980s and 90s saw the widespread use of the Waterfall model for software development. This model was linear and sequential, giving little room for change or feedback. However, as the tech industry evolved, it became clear that a more flexible, collaborative approach was necessary to keep up with rapidly changing customer needs and technological innovations.
A. Agile Manifesto
In response, in February 2001, seventeen prominent figures in the software industry gathered at a ski resort in Snowbird, Utah. This group comprising of methodologists, consultants, and practitioners penned the Agile Manifesto – a short, succinct statement of values aimed at delivering high-quality software that meets customer needs while being flexible to deal with changes.
The Agile Manifesto stated four key values:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
This fundamental shift in values led to the birth of various Agile methodologies such as Kanban, Extreme Programming (XP), Lean, and notably, Scrum.
II. The Emergence of Scrum
A. Inception
The Scrum framework was born in the early 1990s, conceived by Jeff Sutherland and Ken Schwaber. The term ‘Scrum’ comes from a rugby move where players aim to restart the game after a minor violation or a play stoppage, symbolizing the essence of good teamwork.
B. First Scrum Team
The first Scrum Team was put together in 1993 when Jeff Sutherland implemented Scrum at Easel Corporation for a project called ObjectStudio. The productivity of this team saw an exponential improvement in comparison to earlier products, proving the effectiveness of the methodology.
C. Scrum Guide
In 2010, Ken Schwaber and Jeff Sutherland, the fathers of Scrum, collaborated to create the Scrum Guide, a document describing in detail the Scrum framework. It presented the roles, artifacts, and rules belonging to Scrum. The Scrum Guide undergoes iterative revision, with the latest update in 2020 making the guide leaner, more transparent, and more flexible.
III. Agile and Scrum: A Comparison
| Agile | Scrum | |
| Definition | Agile refers to a set of values and principles put forth in the Agile Manifesto. It doesn’t specify particular methods but foreshadows several methodologies that adopt these principles. | Scrum is a specific Agile methodology that uses iterative and incremental practices to deliver products of high quality. |
| Roles | Agile does not define any specific roles. It encourages collaboration and self-organizing teams. | Scrum has defined roles: Product Owner, Scrum Master, and Scrum Team. |
| Feedback | Agile emphasizes end-customer feedback and incorporates changes accordingly. However, it does not specify when and how the feedback should be taken. | Scrum insists on frequent and regular feedback through Sprint Review and Daily Scrum meetings. |
| Documentation | Documentation in Agile is flexible and focuses more on customer satisfaction and working software. | Scrum promotes lightweight documentation, focusing only on necessities. |
| Communication | Agile emphasizes face-to-face communication and promotes team collaboration. | In Scrum, communication is regular and structured, taking place in pre-defined ceremonies such as Daily Scrum, Sprint Planning, and Retrospective. |
In conclusion, understanding the historical development of Scrum and Agile is a crucial step not only for the A-CSM exam but also for anyone looking to implement these methodologies in their work environment. The evolution of these frameworks underlines the iterative and flexible nature of modern software development – a response to the ever-evolving technological and customer landscapes. It is this nature which is at the heart of both Agile and Scrum methodologies.
Answer the Questions in Comment Section
True or False: Scrum was developed in the 1990s by Ken Schwaber and Jeff Sutherland.
- 1) True
- 2) False
Correct answer: True
Who are considered the founders of Scrum?
- 1) Ken Schwaber and Jeff Sutherland
- 2) Michael James and Dean Leffingwell
- 3) Eric Ries and Jeff Patton
- 4) Jeffries Ron and Kent Beck
Correct answer: Ken Schwaber and Jeff Sutherland
In what year was the term “Agile” officially coined in regard to software development practices?
- 1) 1986
- 2) 1991
- 3) 2001
- 4) 2005
Correct answer: 2001
Which of the following are part of the agile manifesto?
- 1) Individuals and interactions over processes and tools
- 2) Following a plan over responding to change
- 3) Comprehensive documentation over working software
- 4) Customer collaboration over contract negotiation
Correct answer: Individuals and interactions over processes and tools and Customer collaboration over contract negotiation
True or False: The Scrum framework was initially introduced for managing and developing products.
- 1) True
- 2) False
Correct answer: True
Which of the following documents influenced the development of Scrum?
- 1) The Toyota Production System
- 2) The Agile Manifesto
- 3) The New New Product Development Game
- 4) All of the above
Correct answer: All of the above
What was the name of the project where Scrum methodology was first implemented?
- 1) Honda Supra project
- 2) OOPSLA project
- 3) Nissan New product development project
- 4) Easel PCX project
Correct answer: Easel PCX project
What is the difference between Scrum and Agile?
- 1) Scrum is a product development strategy, Agile is a project management methodology
- 2) Agile is a product development strategy, Scrum is a framework
- 3) Scrum and Agile are the same thing
- 4) Agile is a philosophy and Scrum is an implementation of the Agile philosophy
Correct answer: Agile is a philosophy and Scrum is an implementation of the Agile philosophy
True or False: Scrum is the oldest form of Agile methodology.
- 1) True
- 2) False
Correct answer: False
In the Agile Manifesto, how many principles underpin the concept of agile software development?
- 1) 10
- 2) 12
- 3) 15
- 4) 16
Correct answer: 12
True or False: In 1995, the first paper on Scrum was published titled “SCRUM: An extension pattern language for hyperproductive software development.”
- 1) True
- 2) False
Correct answer: True
The first version of the Scrum Guide was published in what year?
- 1) 1998
- 2) 2000
- 3) 2010
- 4) 2013
Correct answer: 2010
This blog does a great job of outlining the historical development of Scrum and Agile.
I agree! The evolution of Agile methodologies is fascinating. Does anyone know what inspired the creation of Scrum specifically?
Interesting read. However, I feel like the section on the Agile Manifesto could have included more detail.
The discussion on Agile’s adaptability over the years really resonated with me. Thanks for sharing!
How does the Advanced Certified ScrumMaster (A-CSM) certification tie into the history of Scrum and Agile?
Thanks for the informative post!
Loved the section about the Agile Manifesto and its principles. It’s great to revisit the basics sometimes.
Could you clarify the differences between Scrum and Agile?