The Art of Project Management

Assumptions I've made about you in writing this book

• You are not stupid. I assume that if I've picked the right chapters and write them well, you won't need me to spend time slowly constructing elaborate frameworks of information. Instead, I will get to the point and spend time there. I assume you're something of a peer—perhaps with more, less, or different experience—who has dropped by for some advice.

• You are curious and pragmatic. I draw on examples and references from many disciplines, and I assume you'll find value in pulling lessons from outside of web and software development. This won't get in the way, but pointers for curious minds will surface, sometimes just in footnotes. I assume you want to learn, are open to different ideas, and will recognize the value of well-considered opinions—even if you don't agree with them.

• You do not like jargon or big theories. I don't think jargon and big theories help in learning and applying new information. I avoid them, except where they provide a path to useful information or provide structure that will be useful later on.

• You don't take yourself, software, or management too seriously. Software development and project management can be boring to read about. While this book won't be a comical romp or satire (although a book by Mark Twain or David Sedaris that explains software engineering has potential), I won't hesitate to make jokes at my expense (or someone else's expense), or use examples that make a point through comedic means.