I’ve encountered a number of projects where people didn’t know the context of their work. As developers, they were working on the thing they had to develop or fix today. They might remember what they had done yesterday, but there was no sense that they knew what they needed to do tomorrow, or that they […]
I facilitated a management problem-solving session at the STARWest conference yesterday. When I was debriefing the activities, one participant said he’s met a bunch of testers and test managers who had a “siege” mentality. He was surprised by that. I’m still surprised when I meet people like that. I sometimes see developers who feel
I’m thrilled to be going back to the Softed folks (in Wellington, Auckland, and Sydney) who are doing a project management conference next March. I’m working out with them what topics I’ll be covering. I have a 3-hour workshop in the afternoon. It’s enough time to cover a couple of topics with interactions and
Keith Ray, Dale Emery, and I are writing books. Keith and Dale are tracking their writing with spreadsheets. Dale is posting his progress online. You can see his Oct 8 progress.I decided they were on to something, and start tracking my progress in a spreadsheet also. I have about 35,000 words written. I have about
A colleague asked me what to do when you’re in an iteration and you realize that the story you’re working on spawns other requirements. I suggested that the person add them to the product backlog (the backlog of everything you want to do for the product) and re-rank the requirements in preparation for the next
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?