Esther and I are editing (the next-to-final pass, we think) the book this week, integrating comments from our reviewers. We are very fortunate; our reviewers provided wonderful feedback. And some of the feedback we’re not going to use — at least, not in this book. One of the hardest things to do, whether it’s […]
I’ve changed a few things about this blog: I enabled each post to be its own archive. You can click on the title or on the “link” in the byline. You should be able to use the little email icon to email a blog entry to someone. Please let me know if you find any
I maintain the AYE web site as part of my responsibilities this year for the conference. I post the news, the new articles, and do the general updating. Monday, I posted one of Don Gray‘s articles, Shifting the Burden – Whose Monkey Is It? Except, Don and I had both made a mistake. Don
It’s been a tough week, and it’s only Wednesday morning. We’ve had a bunch of family illnesses — nothing deadly, but difficult to diagnose with long term effects. A very old friend of the family died. And because it’s June, the kids have a gazillion things with school and sports. I’m not quite back
If you’re managing a project longer than a few weeks, you may realize that the project’s progress is not quite where you think it should be. It can seem impossible to change course. But choosing to continue what you’re doing is a choice. So you can choose to do something different. I started thinking
I’ve been thinking a lot about impossible schedules. I’m talking about the project schedules that no matter how you organize the project, it’s not possible for this group of people to cram that set of features into this much time. At least, the developers don’t think so. If people are up against impossible schedules,
I’m in Israel this week, continuing an assessment I started last week. For those of you in the US, sit down. The people who have offices on an outside wall have windows that open. Yup, they do. The A/C and the heat know to shut off when the window is open. (I think they do,
I’ve been thinking about project retrospectives. Too few project teams participate in end-of-the-project retrospectives, and to few managers arrange for them. My clients seem concerned by the price of an outside facilitator and the cost in time to the next project. To address the facilitator cost, I’ve suggested that any facilitator not on the
Frank sent me the music baton. I don’t do chain letters, but I thought this was cute. Sorry, Frank, I’m still going to relate it to work.The official stuff: Total volume of music on my computer: 1128 songs (or 3.2 days, 5.23 GB) The last CD I bought: I can’t remember if it was Saturday
Well, all the comments on my No More Bugs post got me thinking. To answer a few comments here and elsewhere, I’m not trying to blame developers for being human and making mistakes. When I was a developer, most of my mistakes involved code. As a manager, most of my mistakes were in my dealings