The Orasi folks have posted my fall webinars, both the audio and PDF presentation. If you missed What Makes a Great Product Manager? Managing the Project Portfolio Delivering the Right Product on Time: Setting Expectations between Engineering and the Three PMs check out the webinars.
I received an email from a reader today, along with an outline of their hiring process. They spend about 6-8 hours with each candidate, most of which is a series of auditions. They spend maybe an hour with behavior-description questions. These folks have an atypical problem—they’re hiring for consultants, so they need to know how
Warning: I’m on a rant. Yesterday’s Wall St. Journal had an article called “Behind ‘Shortage’ of Engineers: Employers Grow More Choosy” (if I could figure out the URL, I would paste it in here, but I can’t figure out how to do that. Sharon Begley is the author, and the WSJ requires registration. If you’re
In the immortal words of Dilbert/Scott Adams, “Agile programming doesn’t just mean doing more work with fewer people.” See today’s cartoon.
One of my students emailed me recently, asking about how to assess project complexity. He said, “I think it would be pretty neat and also quite useful if you could define a project as say a .60 Apollos or what have you… I don’t imagine it would be at all easy to come up
Last week, at the AYE Conference, I led a workshop called “Conversations with Candidates.” One of the participants wanted to know, “How do I build off a behavior-description question?” I’ve always led the conversations intuitively, so I had to think for a minute to describe what I do. If the next questions doesn’t just come
In my project management class a few weeks ago, I did an activity on feedback. In my experience, many project managers are also functional managers, so they need to give feedback. And, in highly collaborative teams, the person called “manager” isn’t the only one to give and receive feedback. One team got stuck. One
I’m reviewing an article from a long-time colleague who’s just started to write. He has great ideas. And the way he’s packaged his ideas (the writing part) doesn’t do justice to them. There’s a mnemonic* I use (when I remember 🙂 to help me package my ideas better. It’s Hey! You! See? So… Hey! grabs
Don has a great post on Single Point Requirements. You get one example of the requirements: “This product needs to do this. Just this.” Sure enough some months (or years) later, that single example is not sufficiently general to do everything you want the product to do. That’s ok, as long as you plan to
I’m guest blogging this week on computerworld.com. It’s different from what I normally post here.