So after I posted the Probabilistic Scheduling post, I was working merrily away. I had made some small progress on the book, but was still finishing up other things. Finally, Wednesday I had cleared the entire day to work on the book. I was having trouble with one chapter, so I decided to make […]
I’m writing my project management book. I have no idea how far along I am. (Wait, I promise to explain.) When I write, I have several phases: the exploratory phase, where I write articles, the write-it-down phase, where I write the whole thing down (in chunks, of course), and the editing phase. I’m in the
Last week at SD Best Practices, I led an experiential half-day session about coaching. A significant number of the participants thought their job was to teach the other person what to do. (I think one person actually said “lead them to enlightenment.”) While it may be true in sports or school coaching, peer-to-peer coaching
I’m writing the project management book. I’m noting that sometimes PMs (and teams) perform activities that have no lasting useful effect on the project. One example is doing estimation with feedback. If you estimate but never check reality against those estimates, that’s an example of “mental masturbation: it feels good but there’s no lasting
I read RadioShack employees get pink slip via e-mail and at first thought I must have read it wrong. I was stunned to think that anyone would think an email notification of a layoff was acceptable. What were the managers thinking?
This is a little off topic, but it’s a big deal to me 🙂 We hit a major milestone this week. Daughter #1 is off to school. (For my non-US readers, that means university.) We have just one daughter at home, who starts high school this week. Sending a child to school is not like
I’m in the midst of writing the PM book (which is why I haven’t blogged much). One of my tips is that projects have both requirements and goals–and that the PM (at least) needs to know the difference. A requirement can be a use case, user story, a shall statement, whatever. So can a
I’m leading several sessions at SD Best Practices, Sept 11-14, 2006. Here’s the list: Monday, Sept 11: Coaching Your Peers and Staff to Excellence (half-day experiential) Wednesday, Sept 13: Predicting Project Completion Wednesday, Sept 13: Develop Your Interviewing Skills Thursday, Sept 15: Managing the Project Portfolio Thursday, Sept 14: Successful Software Management: 15 Lessons
There’s a fascinating email thread started by David Anderson about What would Agile Auditing Look Like?. Part of the discussion stems from what the definition of an audit is. Audits are about compliance to a defined process. Do we need audits? Sure, for some projects. I would very much like to know that any project
Want to save time on your next project? Improve working relationships? Understand what contributed to your success–or what didn’t? You’ll need a retrospective to do these things, and if you want a great retrospective, you’ll buy a copy of Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen. A retrospective provides