Agile in non-software development

This blog collects a number of sources on the subject of applying Agile methods to areas other than software development.

The Agile Manifesto

"The Manifesto for Agile Software Development

We are uncovering better ways of developing software by doing it and helping others do it.

Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan


That is, while there is value in the items on the right, we value the items on the left more."

Agile in non-software development

Declaration of Interdependence
"Agile and adaptive approaches for linking people, projects and value..."


Agile Software Qualities
"Not long after I encountered the Agile Manifesto, it struck me that the Values and Principles could be applied to work other than software development." Scott Duncan


Ten Practices for Applying Agile/Lean Software Management Principles to Other Knowledge Work
Dean Leffingwell, author of Scaling Software Agility: Best Practices for Large Enterprises, suggests that other types of knowledge work can apply useful principles learned from Agile, Lean, Scrum, and XP software development.


What is the Scrum method?
Scrum is one of several light-weight agile methods that use an iterative and incremental approach for the development of information systems.  The Scrum method brings a small team together to work on a specified set of features over a period of 30-days (called a sprint).


Agile Work Uses Lean Thinking
Lean and Agile are both methods of improving the effectiveness and performance of
work processes. Lean comes primarily from manufacturing and in particular the Toyota
Production System. Agile comes primarily from Agile Software Development and
Project Management. Agile Work has borrowed heavily from Lean thinking and
practices. There are three important connections between Lean and Agile: queueing
theory, empirical process control, and team self-management.

No comments:

Post a Comment