Lean Software Development: An Agile Toolkit | 
| Manufacturer: Pearson Education (USA)
Category: EBooks
List Price: $49.99
Buy New: $38.95
You Save: $11.04 (22%)
Avg. Customer Rating:  37 reviews
Sales Rank: 6941
Format: Kindle Book
Media: Kindle Edition
Number Of Items: 1
Pages: 240
Dewey Decimal Number: 005
Publication Date: March 16, 2007
Availability: Usually ships in 24 hours
|
| Similar Items:
|
| Editorial Reviews:
Product Description
Lean Software Development shows software professionals how to achieve breakthrough quality, savings, speed, and business value by adapting the seven "lean" principles that have already revolutionized manufacturing and R&D. Drawing on 25+ years’ experience leading enterprise projects, the authors show how to use these principles to create agile processes that work - because they’re optimized for your environment.
|
| Customer Reviews: Read 32 more reviews...
 Excellent read November 30, 2008
This is a great introduction to Lean software development principles. It makes a logical connection from lean product development and manufacturing systems to software development systems. It was so good that I also started reading the 2nd version.
 Comes complete with instructions and a warranty July 19, 2008
Shortly after leading my first Six Sigma process improvement project, which involved my constructing of software to automate client business processes, I came across this book by the Poppendiecks. At the time, the integration of Lean and Six Sigma seemed to be picking up steam, and rather than reading a general text on Lean, getting a better understanding of how to apply Lean to software development seemed to make sense. In reading through this book, although Lean and Six Sigma (now often called Lean Six Sigma) share some commonalities, it became quickly apparent that Lean shares much in common with practices set into motion by the agile software development movement. The introduction to this text lists seven Lean principles as applied to software development: eliminating waste, amplifying learning, deciding as late as possible, delivering as fast as possible, empowering the team, building integrity in, and seeing the whole. In addition, it is also indicated that the Lean principles, respectively, do not mean throwing away all documentation, continuously changing one's mind, procrastinating, rushing and delivering sloppy work, abandoning leadership, performing big upfront design, or ignoring the details. It is interesting that the authors wait until the last chapter to disclose what the authors deem as instructions and a warranty card. The authors caution the reader that "one team's prescription is another team's poison", one should "not arbitrarily adopt practices that work in other organizations", and "the right amount of features analysis and traceability depends on the nature of the system and the probability of change" just as "the right amount of user interaction design depends on the users of the system, their background, and how they might use the system". These cautionary notes present a reminder of what the Lean principles applied to software development are all about. The authors also briefly discuss such areas as "special work environments" like the government, where skeptics to agile methods are common. I would like to see the Poppendiecks (or someone else) write an entire book on special work environments. En route to the closing chapter, the authors present 22 tools to help customize the right agile practices for any particular environment. Much of the material will probably already be familiar to agile practitioners, but a substantial amount of the discussion is on Lean. Most of the diagrams presented are well done, although some are a bit amateurish and do not aid the associated discussions. Small case studies that are provided throughout the text are beneficial (although sometimes minimally so) in helping the reader understand the problem space as well as apply the tools. The first few chapters are well suited for an introduction to Lean, and the book in general is recommended for those interested in exploring how Lean might be incorporated into software development.
The Best Introduction I've Read May 31, 2008
It's pretty much all been said by previous reviewers but this one is worth another accolade. As a CIO with over 20 years in software engineering, I've just about read it all, seen it all, tried it all. As a result I'm a big believer in Lean/Agile, and this is the best introduction I've come across. It's a nice, practical mix of principles and practices and touches on all the right themes.
A previous reviewer laments the authors' distaste for CMMI and PMI. For instance:
"Between PMI and CMM certification programs, a heavy emphasis on process definition and detailed, front-end planning seemed to dominate everyone's perception of best practices...spending a lot of time and getting the requirements right upfront was the way to do things `right the first time'...CMM, in its eagerness to standardize process, leaves out the heart of discovery and innovation..." Spot on.
As a PMP with CMMI experience, I couldn't agree more with the Poppendiecks' observations and concerns. They go on to say, "This is not to say that CMM and PMI are bad, but only that for anyone who has lived through the lean revolution, they tend to give the wrong flavor to a software development program." That "wrong flavor" is called "waterfall."
Of course there are Level 5 Agile shops out there, and the author's recognize that "CMM is not supposed to dictate approach, but only assess..." But here's the problem: "CMM programs...may standardize on less than ideal practices...they may be better implemented separate from--and after--process improvements."
This book is a must read for software development managers and other business execs pursuing the promise of an Agile company (vs. IT shop). I'll definitely be passing out a few copies!
 Unimpressed March 17, 2008
1 out of 6 found this review helpful
I found nothing concrete or useful in this book. It is loaded with interesting anecdotes but they're vague with regard to execution and follow through. The success stories generally end with the release date. Never mind the poor slobs who had to maintain whatever was slapped together at the last minute.
Recommended January 2, 2008
This book is excellent. Both Mary and Tom compares the software development with other fields of production. I've to say that if the steps planted in this book are followed seriously, your company will be great.
|
|
|
|
