I ran into Dan North at the Agile conference today, and explained a little about the project portfolio book. I’m writing it because I have a number of clients who are having trouble breaking the multitasking habit (working on more than one project at one time.) Dan said, “Oh, you want them to commit to […]
I’ve been steadily writing the project portfolio management book this summer, and was describing what I do to Steve Freeman someone today. (I’m at the Agile 2008 conference.) I explained that I had a list of things I thought should be in a chapter, but it wasn’t a real outline the way other people outline.
Dwayne’s comment on my post, Architecting from the Features, made me realize I hadn’t provided an example of how I’d changed the book. Head slap on me! One of my rules of writing, which I use when I’m revising because I rarely remember as I’m writing the first draft, is to explain what I’m writing
I’m writing the portfolio management book, and I just finished a whole big re-architecture. I’m so excited. I realize most people aren’t that excited about a rearchitecture :-), especially not of a book in progress. But I am, because I took my own advice. When I started writing the book, I had several partly done
I was under the weather last week, and am finally well enough to think. I still have the raspy voice from coughing all week, but you can’t hear me. Since I worked out this morning, my brain is actually firing on all cylinders. I signed a contract with Pragmatic Bookshelf for my next book about