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
Video:
The Role of Leadership in Software Development
Video:
Competing
on the
basis of time
Conference
Photos
| |
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.
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.
Dan Carrison,
Deadline! How Premier Organizations Win the Race Against Time,
American Management Association, 2002
Stories about how several large, high
profile projects met impossible deadlines. Check out the chapter on the
Boeing 777.
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.
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.
Larry Constantine, and Lucy Lockwood;
Software for Use,
Addison-Wesley, 1999
The authoritative book on
usage-centered design.
Michael A. Cusumano and
Richard W. Selby,
Microsoft Secrets,
paperback edition, Simon & Schuster, 1998. Originally published in 1995
How Microsoft developed software in the
mid-90's: Small teams, divisible architecture, daily integration,
releasable code every quarter.
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!
Martin Fowler,
Refactoring,
Addison-Wesley, 1999
The classic book on refactoring.
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.
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.
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.
Joshua Kerievsky,
Refactoring
to Patterns, Addison-Wesley, 2004
The best how-to guide on
refactoring.
Jeffrey Liker,
The
Toyota Way; 14 Management Principles from the World's Greatest Manufacturer,
McGraw-Hill, 2004
Worth the price of the book just for the two
chapters on the development of the Lexus and the Prius.
Robert C. Martin,
Agile Software Development: Principles, Patterns, and Practices,
Prentice Hall, 2002
Conveys deep wisdom about leveraging object-oriented concepts.
Matthew May,
The
Elegant Solution: Toyota's Formula for Mastering Innovation, The
Free Press, New York, 2007
If you ever wondered "How does Toyota do
it?" this book has answers - from an advisor to the University of Toyota.
Geoffrey A. Moore,
Crossing the Chasm,
revised edition, Harper Business, 2002; first published 1991
The classic marketing book for high-tech
products. If you are trying to sell lean / agile concepts, this is a good
book to read.
James Morgan
and Jeffrey Liker,
The
Toyota Product Development System: Integrating People, Process and Technology,
Productivity Press, 2006
A detailed study of how Toyota applies the principles of the Toyota Way to
product development.
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.
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.
Donald G. Reinertsen,
Managing the Design
Factory, The Free Press, New York, 1997
An excellent book on lean product
development.
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.
Jim
Surowiecki,
The
Wisdom of Crowds, Anchor, 2005
How it is that all of us make better decisions than any of us.
Harold Thimbleby, ‘Delaying Commitment,’
IEEE Software,
May, 1988
The classic paper discussing why experienced designers delay commitment when
they develop software.
Dave Ulrich, Steve Kerr and Ron Ashkenas,
The GE Work-Out, McGraw-Hill,
2002
Use this as a guide for conducting software development Kaizen Events.
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.
Top M
|
