|
Another book that also referred to the concept of flow was Stumbling on Happiness. - which pretty much sums up some of the same thoughts. One of the ideas in the book is the concept of "flow" - then, years later I read Flow: The Psychology of Optimal Experience (P.S).
The ideas in this book are about many of the topics that "agile" teams speak about now, and there are some key ideas that make sense for any team of professionals who have to work together. Tom DeMarco and Tim Lister have gone on to write other key classics such as "Waltzing with Bears", but this is still my favorite. This book is one of the books I still recommend to people who are managing software development teams.
Great writing style, and you "get" what it's about almost immediately (unless you are one of the "office police"). Also great books.I still enjoy occasionally re-reading this classic that should be in every developer/manager's collection. I still use memorable phrases from this book such as "brain time vs.
body time", and "bring back the door".
Read this book in order to find out, and you'll have a facts-based tool chest that you can use to look for and solve potential problems in your future projects, before they even arise. What are the factors that influence the success or failure of software projects. DeMarco and Lister take a scholarly approach to some of the most important questions revolving around software project management. This book is full of references to real-life studies and examples, and does not rely on common-sense or assumption.
The book arrived on time and I am very happy with it. I got the book at a great discount in the condition that was described.
So much of our common practices and conventional wisdom have changed (in part due to the impact of this book) that much of the advice in the book is obsolete. This is the book whose title has become synonymous with managing teams in software companies. The fact is, today's programmer is a different beast from the programmer of the '80s.For more up-to-date material, you might look to the Joel on Software books, or any number of blogs. True, gems like the inverse relationship between noise and code quality will likely stay relevant for a century, but most of this book is about getting programmers to work together. Though this 2nd edition came out in 1999, most of the content is identical to that of the original 1987 edition. 22 years later, that's a problem.
I gave my son this book to read since he is a computer science major at Johns Hopkins University and I know that its information will be useful to his career. The basis for building effective project teams is always dependent on team dynamics, facilitation, the available technology as well as the work environment.In this book, the author's present well tested recommendations for effectively managing information technology (IT) projects and their teams.The book shows why the human aspects of project management are usually more difficult to manage than technology.
|
