A number of people still subscribe to this blog with an email subscription. I had used Bloglet to do process the emails, but the service didn’t always work. And to be fair, Bloglet was a free labor of love 🙂 I’m now using Feedblitz, assuming I didn’t make any mistakes. As always, feel free to […]
It’s been quite the Monday so far. My office toilet started spewing water, a cabinet door fell off one of the cabinets in the kitchen, and I’m trying to back up and duplicate my hard disk because both latches on my Powerbook broke at the Agile conference and I need to send my computer
Several years ago, a colleague emailed me, asking how to keep sponsors involved. My colleague was using company-mandated phase-gate lifecycle with long project durations (18-24 months). I’d recommended providing a project dashboard and showing the sponsor progress. My colleague was stumped–the dashboard wasn’t particularly helpful until they were in the testing phase and it
If you’ve ever tried to look at my articles page, you know how hard it was to find anything. Well, my updated version of the site is finally up. I have a few broken links, which I expect to fix, hardware willing, in the next week or so. If you find anything broken, do let
A couple of weeks ago at our Managing One-on-One workshop, Esther and I were teaching about how to give feedback. Here’s the “recipe”: Create an opening to deliver feedback. Describe the behavior or result in a way the person can hear. State the impact using “I” language. Make a request for changed behavior. When
Also this week, over at the AYE Conference, my Starting With Rolling Wave Planning is up.
I’ve had technical debt on my mind recently, so I’ve been writing about it. This week, the good folks at Stickyminds published my column, An Incremental Technique to Pay Off Testing Technical Debt. Enjoy!
I was at the Better Software conference last week, met a bunch of great people (including Jim Shore and Joel Spolsky). Another important person is someone who’s not famous–and important nevertheless. A senior tester explained her situation and asked for some help. “Most of our testers can’t read code. And, we don’t know what
A reader was reading Characteristics of Great Project Managers and asked, “Do you feel that to be a great Project Manager one need not know completely about the technology involved?” No. Project managers need to understand enough about the technology so that they can make tradeoff decisions (or help product owners make tradeoff decisions) about
When I teach project management, I ask the participants to create a project charter (See my templates page for one I use to start). I recently encountered a battered project manager who does not have a project charter for a project with 6 or 7 sub-projects. This PM is smart, but has never managed a