Framework Design, Agile Coach, President Oklahoma City Developers Group, Microsoft MVP C#, TDD, Continuous Integration, Patterns and Practices, Domain Driven Design, Speaker, VB.Net, C# and Sql Server
I recently finished reading the
Extreme Programming Pocket Guide.
I don't think you will find a more precise, to the point, compact
package of XP anywhere like you find in this little book. It is
only 80 pages and can be read in about 3 hours. In some near
future posts coming up, this book will be my primary reference for the
direct, no-fluff, short explanations of XP methodologies. I do
not, however, recommend reading this book first if you haven't delved
into XP much. I would recommend starting with
Extreme Programming Explained: Embrace Change by Kent Beck, or the
2nd Edition of the same
by Kent Beck and Cynthia Andres. I have not read the 2nd edition.
Planning Extreme Programming by Kent Beck and Martin Fowler is another great book to start with.
If you are giving talks, presentations or dicussions on XP, this little
pocket guide is a must have. Thanks to Dino Esposito for turning
me on to it.
Extreme Programming (XP) is a radical new approach to software
development that has been accepted quickly because its core
practices---the need for constant testing, programming in pairs,
inviting customer input, and the communal ownership of code---resonate
with developers everywhere. Although many developers feel that XP is
rooted in commonsense, its vastly different approach can bring
challenges, frustrations, and constant demands on your patience. Unless
you've got unlimited time (and who does these days?), you can't always
stop to thumb through hundreds of pages to find the piece of
information you need. The Extreme Programming Pocket Guide is
the answer. Concise and easy to use, this handy pocket guide to XP is a
must-have quick reference for anyone implementing a test-driven
development environment. The Extreme Programming Pocket Guide
covers XP assumptions, principles, events, artifacts, roles, and
resources, and more. It concisely explains the relationships between
the XP practices. If you want to adopt XP in stages, the Extreme Programming Pocket Guide will help you choose what to apply and when.
About Raymond Lewallen
Working primarily in the public sector during his career, Raymond has designed and built several high profile enterprise level applications for all levels of the government. Raymond now works as a solutions architect for EMC. Raymond is an agile coach, Microsoft MVP C# and also president of the Oklahoma City Developers Group and Oklahoma Agile Developers Group. Raymond spends a lot of his time learning and teaching such things as Test Driven Development, Domain Driven Design, Design Patterns and Extreme Programming practices and principles, to name a few. Raymond is also an advocate of Alt.Net. Raymond is primarily a framework guy, so don't ask him anything about UI :)
