Remove 2001 Remove Book Remove Documentation
article thumbnail

In Appreciation of the Agile Manifesto

Vitality Chicago

I was busy in 2001 with the challenges of delivering technology solutions using the waterfall approach that was dominant at that time. The waterfall approach was heavy on process and documentation and light on success rates. The meeting in 2001 represented a crystallization of great ideas from different approaches.

Agile 52
article thumbnail

Software Craftsmanship

My Agile Partner

Software Craftsmanship: Rooted in the Agile Manifesto Written in 2001, the Agile Manifesto was crafted by 17 recognized specialists in the world of software development. A book titled “Software Craftsmanship” was published in 2001 to differentiate between developers confined to an industrial mindset and agile developers.

Agile 52
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Agile Methodology vs Framework vs. Toolkit – Does it Really Matter Eddie?

Vitality Chicago

Jim Highsmith highlights these and more in his 2002 book, Agile Software Development Ecosystems. At the time, Highsmith called it the best supported training and documentation of any of the ecosystems. Crystal is described in the 2005 book, Crystal Clear though it never really got much traction. We’ll never know I guess.

Agile 74
article thumbnail

Agile History and Archaeology

Managed Agile

However, even Dr. Winston Royce who documented the initial Waterfall process in his 1970 paper recognized the limitations in this process. Taiichi Ohno publishes the book “Toyota Production System – Beyond Large-Scale Production” describing LEAN, Lean Manufacturing and Kanban. 2001 – Agile Manifesto. Womack and Daniel T.

Agile 59