The principles which drive Lean can be applied to software. Doing so provides guidance for those who are attempting to develop software more effectively. In this article, instead of describing Lean on its own, I will describe Lean in terms of the Agile practices it suggests. This will illustrate how Agile practices are manifestations of Lean principles. There is power to this understanding - when an Agile practitioner finds himself in a situation where a standard Agile practice cannot be followed, the Lean principles will guide him/her to a better way.

This featured article is a continuation of the article appearing in the October 2007 Ezine by Amir Kolsky, Senior Consultant, Agile coach and trainer at Net Objectives. This installment extends the discussion of the place documentation takes within an Agile process by considering the unreliability of written documentation in terms of accuracy and immediacy which often leads Agile teams to put an emphasis instead on warm, high bandwidth communication media such as face-to-face conversations.

This is an excerpt of Alan Shalloway’s and Jim Trott’s upcoming book – "Lean-Agile Anti-Patterns and What to Do About Them".
This chapter covers several critical issues surrounding the role of quality assurance in Lean-Agile software development

In this featured article, its author Amir Kolsky, Senior Consultant, Agile coach and trainer at Net Objectives, discusses the reasons for the emergence of the myth that Agile teams do not write documentation and the place documentation does take within an Agile process.

The software industry now builds the wrong software 64% of the time. How does this happen? What can we do to be more effective? This featured ezine article addresses these questions.

This featured article, Chapter 22 from the Second Edition of Design Patterns Explained: A New Perspective on Object-Oriented Design, focuses on a project done by following the guidelines of Design Patterns, Agile Development, and Refactoring to show how these ideas can inform each other.

Our view of eXtreme Programming (XP): a methodology we like even as we recognize its strengths and weaknesses