Order The Book
Introduction
Sample Chapter 1
Table of
Contents
Interview
Order The Book
Table of
Contents
Preface
Sample Chapter 1
Sample Chapter 2
Interview
Order The Book
Table of Contents
Introduction
Sample
Chapter
Book Review 2005
Book Review 2007
Interview:
Hanselminutes
Video: A
History
of Leadership
| |
Recommended Reading
Sanjiv Augustine,
Managing Agile Projects,
Addison-Wesley, 2005
A nice summary of agile leadership practices.
Rob
Austin,
Measuring and Managing Performance in Organizations,
Dorset House, 1996
You get what you measure, but you can't measure everything, so what should you
do? One of the best books on performance measurement we've seen.
Rob Austin & Lee Devin,
Artful Making, Prentice Hall, 2003
A play comes together on opening night, no matter what. With the same
philosophy, software can come together on time, every time.
David Astels,
Test-Driven
Development, Prentice Hall, 2003
Award-winning book. This is the book to get
if you are implementing test-driven development.
Kent
Beck,
Extreme Programming Explained, Addison-Wesley, 2000;
Second Edition (with Cynthia Andres), 2004
The book on XP that started it all.
The second edition is a completely new book, and it's great.
Kent
Beck,
Implementation Patterns, Addison-Wesley, 2008
Thinking tools for creating great
code.
Bjarte
Bogsnes,
Implementing Beyond Budgeting, Wiley, 2009
Agile ideas from the executive suite
for the executive suite. Frederick Brooks,
The Mythical Man-Month,
Anniversary Edition, Addison Wesley, 1995, originally published in 1975.
A classic that has stood the test of
time. It shows how little things have changed in 30 years.
Clayton M. Christensen,
The Innovator’s
Dilemma, Harvard Business School Press, 1997
A great book on how disruptive
technologies displace market leaders almost every time.
Lisa
Crispin and Janet Gregory,
Agile Testing: A Practical Guide for Testers and Agile Teams,
Addison Wesley, 2009
Broad and in-depth coverage of how to
move testing to the front of the development process.
Kim B. Clark and
Takahiro Fujimoto,
Product Development
Performance, Harvard Business School Press, Boston, 1991.
Shows how the key to product integrity
is information flow, from the market to the technical team, and among all
members of the technical team.
Alistair Cockburn,
Writing
Effective Use Cases, Addison-Wesley, 2001
The classic book on writing use cases,
and still the best one on the subject.
Mike Cohn,
User Stories Applied, Addison-Wesley, 2004
The details about how to use
stories to drive your development process.
Mike Cohn,
Agile Estimating and Planning, Addison-Wesley, 2005
So you want to be agile and want to know what happens to planning? Read
this!
James C. Collins,
Good to Great,
Harper Business, 2001
The five basis for creating great
organizations: a great book.
James C. Collins,
How
the Mighty Fall,
HarperCollins, 2009
Everything you always wanted to know about
Big Company Disease.
Larry Constantine, and Lucy Lockwood;
Software for Use,
Addison-Wesley, 1999
The authoritative book on
usage-centered design.
Mark Denne & Jane Cleland-Huang,
Software by Numbers; Low-Risk, High Return Development,
Prentice Hall, 2004
This book shows how to benefit
from staged deployment based on economic analysis. Provides solid
financial justification for agile development.
Jeffrey H. Dyer,
Collaborative Advantage:
Winning Through Extended Enterprise Supplier Networks,
Oxford University Press, 2000
The economic rationale behind
collaborative relationships with suppliers. Good background for
establishing a contracting philosophy.
Eric Evans,
Domain Driven Desig n:
Tackling Complexity in the Heart of Software,
Addison Wesley, 2003
An extremely important book -
proposes that domain understanding is at the heart of great software design, and
shows how to do it.
Michael Feathers,
Working Effectively with Legacy Code, Addison-Wesley, 2005
If you are working with Legacy
Code, GET THIS BOOK!
Jamie
Flinchbaugh and Andy Carlino,
The
Hitchhiker's Guide to Lean, Society of Manufacturing
Engineers, 2006
A really good basic introduction to lean thinking.
David H. Freedman,
Corps Business;
The 30 Management Principles of the U. S. Marines,
Harper Business, 2000
A great book on leadership, management, and
bringing out the best in front line workers.
Malcolm
Gladwell,
Outliers: The Story of Success, Little, Brown and Company,
2008
This is a fascinating book
about how culture and chance combine with hard work to create amazing success.
Eliyahu Goldratt
and
Jeff
Cox,
The Goal,
2nd Revised Edition, North River Press, 1992, first published in 1984
If you haven't read this
business novel on the Theory of Constraints applied to manufacturing, you've
missed a classic.
Jeremy
Hope, Robin Fraser,
Beyond Budgeting, Harvard Business School Press, 2003
Agile ideas from the executive suite
for the executive suite. The book that started the movement.
Michael N. Kennedy,
Product Development for the Lean Enterprise, Oakela Press, 2003
If you want to know how the company that invented Lean (Toyota) does product
development, this is the book to read.
Michael N. Kennedy,
Kent Harmon, Ed Minnock,
Ready, Set, Dominate, Oakela Press, 2008
Implement Toyota's Set-based Learning for Developing Products and Nobody Can
Catch You. RECOMMENDED!
Joshua Kerievsky,
Refactoring
to Patterns, Addison-Wesley, 2004
The best how-to guide on
refactoring.
 Henrik
Kniberg,
Scrum and XP
from the Trenches, InfoQ, 2007
An immensely practical guide to getting started with agile.
Henrik
Kniberg and Mattias Skarin,
Kanban and Scrum
- making the most of both, InfoQ, 2009
If you want to know the differences between
scrum and kanban, this is the place to find out.
George
Koenigsaecker,
Leading the Lean Enterprise Transformation, Productivity Press, 2009
If you really want to know how it's done, then read the book by someone who has
lead several successful lean transformations.
Corey Ladas,
Scrumban: Essays on Kanban Systems for Lean Software Development,
Modus Cooperandi Press, 2009
If you want to know how Kanban works, this is the book to get.
Gerard
Meszaros,
xUnit Test Patterns: Refactoring Test Code, Addison-Wesley, 2007
Tests
are software too. But they have their own set of patterns, and this book is the
insiders guide.
Bob Martin,
Clean Code: A Handbook of Agile Software Craftsmanship, Prentice
Hall, 2008
What
simple, clean code is, why you need it, and how to do it. Every developer
should read this book.
Matthew May,
The
Elegant Solution: Toyota's Formula for Mastering Innovation, Free
Press, 2006
A look at the culture driving the innovations in both manufacturing and product
design at Toyota.
Rick Mugridge and Ward Cunningham,
FIT
for Developing Software, Addison-Wesley, 2005
Anyone doing automated
acceptance testing, including retrofitting legacy code with acceptance tests,
should READ THIS.
Michael
Nygard,
Release It!: Design and Deploy Production-Ready Software,
Pragmatic Bookshelf, 2007
If your code has to stand up to relentless
stress in a production environment, this book is required reading.
Taiichi Ohno,
Toyota Production System,
English,
Productivity, Inc.
1988, published in Japanese in 1978
A MUST READ book by the Father
of the Toyota Production System. Easy to read, engaging, and profound.
Jeffery
Pfeffer and Robert Sutton,
Hard Facts, Dangerous Half-Truths, and Total Nonsense: Profiting from
Evidence-Based Management, Harvard Business School Press, 2006
A wonderful book about how some of the most
unassailable management wisdom is clearly wrong - based on the evidence.
Jeffery
Pfeffer,
What Where They Thinking? Unconventional Wisdom About Management,
Harvard Business School Press, 2007
Any book by Jeffery Pfeffer is always full of a lot of wisdom.
James
Parker,
Do
the Right Thing: How Dedicated Employees Create Loyal Customers and Large
Profits, Pearson Education, 2008
A GREAT book on leadeship.
Mary Poppendieck and Tom Poppendieck,
Lean
Software Development,
Addison Wesley, 2003
If you have a lean initiative in your company and you do software development,
you should read this book.
Mary Poppendieck and Tom Poppendieck,
Implementing Lean
Software Development, Addison Wesley, 2006
The sequel to Lean Software Development.
Mary Poppendieck and Tom Poppendieck,
Leading Lean
Software Development, Addison Wesley, 2009
For Leaders of Software-Intensive
System Development.
Donald G. Reinertsen,
Managing the Design
Factory, The Free Press, New York, 1997
An excellent book on lean product
development.
Donald G. Reinertsen,
Principles of Product Development Flow, Celeritas Publishing, 2009
Empirical vs. defined processes is not the
point. It's the economic consequences of the choices we make that matters.
Mike
Rother,
Toyota Kata, McGraw-Hill, 2009
How Toyota does Relentless Improvement.
Preston G. Smith and
Donald G. Reinertsen,
Developing Products in
Half the Time, Second Edition, John Wiley and Sons, 1998. originally
published in 1991
Still the classic on rapid product
development.
Harvey M. Sapolsky,
The Polaris System Development,
Harvard University Press, 1972
An out-of-print book about a
stunningly successful large system development project. Although PERT
was invented for this project, it had little to do with the program's
success.
The real reasons for Polaris's success reads like a textbook case of
applying Lean principles to large projects.
Ken Schwaber, and Mike Beedle,
Agile Software
Development with SCRUM, Prentice Hall, 2001
The book to read for an introduction to
Scrum.
Ken Schwaber,
Agile
Project Management with SCRUM, Microsoft Press, 2004
A book filled with case studies and
down-to-earth tips about how to do Scrum.
Peter Scholtes, Brian Joiner, Barbara Streibel
The
Team Handbook, Joiner/Oriel, Third edition, 2003
A classic on applying Deming's ideas: the team perspective. Tools
for making team improvement efforts highly effective.
Peter Scholtes,
The
Leader's Handbook, McGraw-Hill, 1998
A classic on applying Deming's ideas: the management perspective.
RECOMMENDED!
John
Seddon,
Freedom From Command and Control: Rethinking Management for Lean Service,
Productivity Press, 2005
Systems thinking for any organization that provides a service.
John
Shook,
Managing to Learn, Lean Enterprise Institute, 2008
Using the A3 management process to solve problems, gain agreements, mentor, and
lead. HIGHLY RECOMMENDED!
Durward
Sobek and Art Smalley,
Understanding A3Thinking, Productivity Press, 2008
An excellent toolbox for those who are looking for those who are sharpening
their focus on relentless improvement.
Steven
Spear,
Chasing the Rabbit, McGraw Hill, 2008
How Market Leaders Outdistance the Competition and How Great Companies Can Catch
Up and Win.
HIGHLY RECOMMENDED!
Jim
Surowiecki,
The
Wisdom of Crowds, Anchor, 2005
How it is that all of us make better decisions than any of us.
Allen
Ward,
Lean Product and Process Development,
Lean Enterprise Institute, 2007
A deep look at how Toyota develops products, with critical guidance on how to
apply lean to a development environment. RECOMMENDED!
Karl Weick and Kathleen Sutcliffe,
Managing the Unexpected; Assuring High Performance in the Age of Complexity,
Jossey-Bass, 2001
A fascinating book about what makes
very dangerous places safe: aircraft carriers, chemical plants, emergency
scenes.
James P.
Womack, Daniel T. Jones, and Daniel Roos,
The Machine That Changed the
World; the Story of Lean Production, Rawson and Associates; 1990
The classic book with the sub-title that gave Lean its name.
James P.
Womack, and
Daniel T.
Jones,
Lean Thinking, Simon & Schuster, 1996;
Second Edition, Free Press, 2003
For almost a decade, this was the best book on Lean. The revised
edition remains a classic.
Andreas Zeller,
Why
Programs Fail: Systematic Debugging, Morgan Kaufmann, 2005
How to gain design knowledge by finding and fixing defects that escape into
production.
Top M
|
