Updated: Mar 14, 2019
I wrote this article from my experience after coaching and teaching Agile for companies in the U.S.A, Australia, and Thailand
1. Read and understand the Manifesto for Agile Software Development.
Note: You can replace the word Software to Products or Services if you do not produce Software.
2. Read and understand the Principles behind the Agile Manifesto.
3. Read and understand the History: The Agile Manifesto.
4. After reading and analyzing this paragraph from the History of The Agile Manifesto as below,
"But while the Manifesto provides some specific ideas, there is a deeper theme that drives many, but not all, to be sure, members of the alliance. At the close of the two-day meeting, Bob Martin joked that he was about to make a "mushy" statement. But while tinged with humor, few disagreed with Bob’s sentiments—that we all felt privileged to work with a group of people who held a set of compatible values, a set of values based on trust and respect for each other and promoting organizational models based on people, collaboration, and building the types of organizational communities in which we would want to work. At the core, I believe Agile Methodologists are really about "mushy" stuff—about delivering good products to customers by operating in an environment that does more than talk about "people as our most important asset" but actually "acts" as if people were the most important, and lose the word "asset". So in the final analysis, the meteoric rise of interest in—and sometimes tremendous criticism of—Agile Methodologies is about the mushy stuff of values and culture."
- Jim Highsmith -
A co-author of the Agile Manifesto
I would like to recommend
A. Forming a reference model team, a transformation team and an executive action team as the ONE LAB DESIGN model.
B. a reference model team to select and follow a framework under the Agile umbrella or construct its own framework which is compatible with the Agile Manifesto values and principles.
Practices and methods that had an influence on the manifesto for Agile software development
- Modeling Languages
- Pragmatic Programming
- Dynamic Systems Development Method (DSDM)
- Test Driven Development (TDD)
- Adaptive Software Development (ASD)
- Design Driven Development, Refactoring
- Feature Driven Development (FDD)
Agile at Scale
C. a transformation team to work with an executive action team to create Agile environments by deeply understanding the Agile Manifesto values and principles.
5. Practice Practice and Practice