article thumbnail

Kanban History: Origin & Expansion Across Industries

ProjectManager.com

Learn more History of Kanban Kanban was first introduced in Japan as a lean manufacturing approach pioneered by Taiichi Ohno in the late 1940s. The book laid out the principles of lean manufacturing, which focuses on reducing waste, creating customer value and seeking continuous process improvement, and kanban.

article thumbnail

The Agile Manifesto from a Lean Perspective

Scrum.org

So where were you between February the 11th and 13th, 2001? To what extent, for example, is the Manifesto a reflex of “lean thinking”? There’s a clear synergy between lean and agile practice, and attempts to tease them apart can often seem contrived and artificial.

Lean 163
Insiders

Sign Up for our Newsletter

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

article thumbnail

What Is the Definition of Done for Agile Teams?

ProjectManager.com

In terms of software development, done is when something is coded to standards, reviewed, implemented, tested, integrated and documented. Agile has been around since 2001, when a small group created the Agile Manifesto in response to traditional approaches of managing software development. The Principles are Constant.

article thumbnail

5 Agile Methodologies for Project Managers that are not Scrum Framework

Project Pulse Journal

Understanding these top five Agile methodologies that are not Scrum Framework: Kanban, Extreme Programming (XP), Lean Software Development, Feature-Driven Development (FDD), and Dynamic Systems Development Method (DSDM) is crucial for any team or individual looking to implement Agile practices effectively.

article thumbnail

Agile and Scrum: Unravelling the Misconceptions

Scrum.org

Agile eliminates the need for planning or documentation. In 2001 the Agile Manifesto for Software Development was introduced to encapsulate a new way of thinking with 4 values and 12 principles on how to deliver software products better. There are other agile approaches such as Kanban, Lean, and Extreme Programming (XP).

SCRUM 172
article thumbnail

A PM’s Guide to Agile Software Development

Project Bliss

It came about during a ski trip in 2001. This group of guys recognized a need for a more adaptive alternative to the regimented, documentation-driven software development process. Working software over comprehensive documentation. They took lean manufacturing principles and applied them to software development.

article thumbnail

The Complete History of Agile Software Development

Agilemania

After the Oregon meeting, Jon Kern and the 17 groups of developers (Kent Beck, Ward Cunningham, Arie van Bennekum, Alistair Cockburn, and twelve others) met at a snowbird ski resort, Utah in 2001. Working software over comprehensive documentation. In 2001, Agile started its journey, but the legacy of agile had only just begun.