Yes, I'm Published!

Cut to the Chase

Just want to skip right to the chapter I wrote? No problem! Download the PDF version here. Someday, if I can find the original word file, I'll webify this so you can easily move from page-to-page without downloading the whole 12 mb file.

Chapter Synopsis

As noted in the introductory paragraphs of the chapter, I use an analogy of a troupe of actors working from — and modifying — a script to explain the process of moving from the idea of a Windows 2000 deployment formulated in testing, to refining the deployment plan, and through the pilot deployment. It discusses the role of deployment team individuals, and the critical roles of the test lab and the pilot deployment itself in developing a stable rollout that meets an organization's business needs. The chapter does not dig into the details of Windows 2000 features, domain upgrade, or domain restructuring, which were covered in other chapters of the book — particular Chapters 18 and 19, respectively, regarding the topics just mentioned.

Personally, I think this allows my chapter to at least partly survive the ravages of time. Even though most people probably have already completed a Windows 2000 deployment, the chapter I wrote focuses on planning, testing and pilot deployments; many of the points I make will work for other projects as well and are not limited to Windows-NT-to-Windows-2000 migrations.

At any rate, if you take a look at the chapter, I hope you'll drop me an email with your impressions and thoughts! Send any email to "book-response" at Unspun dot US!

To learn something about how I came to do this book, read the next section of this page!

How It Happened

In addition to writing for The Unspun Zone™ and TechStop™, I've also written for the book-reading public.

At the time the book was written — December of 2002 — I had been working as a technical reviewer for The Coriolis Group. Some of these projects were quite interesting, but I was itching to do a little writing of my own.

For one thing, I had started doing technical reviews because I wanted to make a difference. When I first started out in the information technology field in the early 1990s, I was discouraged because so many books written "for average techs" contained misinformation. Sure, Douglas Comer's books on Internetworking, Nadia Perlman's classic text on Bridges and Routers and W. Richard Stephen's phenomenal series, TCP/IP Illustrated, were great. But not too many ordinary techs read these and, as I became busier, I wanted more "to the point, regular tech books" myself. Too many of these seemed slapped together without spotty accuracy.

As a technical reviewer, I found that some authors with whom I worked were glad I caught mistakes. Others were frustrated and said I "made too many comments." (Moi???) Regardless of the reaction, second drafts often came back with the mistakes uncorrected.

I was itching to write something myself.

Near the end of December 2000, opportunity knocked. I was working on a tech review when I got an email from the project editor saying that another book was having trouble with deadlines and the author wanted to know if there was anyone interested in helping by writing a chapter on "Test Labs & Pilot Deployments." Was I interested? And how! Here was an opportunity to get my feet wet without having to actually go it alone!

Although I'd written a few articles for small journals before, this was my first "real" professional writing job. I was excited!

Within a day or two, a contract had arrived, I signed it and the rest is history. For writing this chapter, which took perhaps 15 hours total, I was paid the (to me, at that time) princely sum of $1000.



© Copyright 2003, 2004, 2005 Unspun™. All Rights Reserved Worldwide.
Quick Reviews