When it comes to projects, there are as many questions to answer as there are project teams, but “Where are we?” is by far the most popular. The key to understanding a project is to make regular measurements—both quantitative and qualitative—and display the measurements publicly. When project managers display these measurements as part of the
Senior managers — the people who make strategic product decisions — need to know when they can expect those products to release. The organization of current product releases against a timeline is a project portfolio. And, planning the project portfolio in an agile environment is different — but not harder — than planning the project
Technical debt is the unfinished work the product development team accumulated from previous releases. This debt includes: design debt, where the design is insufficiently robust in some areas; development debt, where pieces of the code are missing; and testing debt, where tests were not developed or run against the code. Technical debt is common, but
Summary: If someone on your project team isn’t working up to par, it might take more than a simple showing of your disapproval to put him on the right track. Johanna Rothman suggests trying specific and useful feedback—show your employees the light before you show them the door. Margaret, a manager, was concerned about one of
My column over at the Fast Company/Inc hiring site is up. See Developing a Professional Portfolio. You can’t leave comments there, so please leave comments here.
I’ve been working with some companies who do hardware/software systems. Most often, they have some embedded code too, just to make life interesting. To be honest, I don’t know how to do implementation by feature for a whole brand new system. Here’s what I’ve been suggesting: Prototype the software architecture as early as possible,
I led a very short interviewing class when I was in Israel, mostly teaching project management. One of my classes wanted a few tips on how to interview more successfully. I asked them what they were doing now, and they claimed to be asking behavior-description questions and using auditions. Those techniques should work, so I
One of the scheduling tips I discuss in my project management workshops is “Plan to refactor.” I explain that if you’re using a lifecycle other than Agile, where the integration and testing is built into every iteration, you’re going to have to refactor at the end, when you do integrate and test. At one
I’m in Israel now (for workshops). I was traveling through Newark yesterday, and had to change terminals between the domestic flight that got me to Newark and the international flight that was going to leave from Newark. Turns out, a bunch of other people had to change terminals too. The signs are so bad,
I saw this gem of advice: ask for a candidate to explain his/her most significant accomplishment when sending a resume. (Found on Recruiting.com.) This is a great screening device (better than technical tests, in my opinion). Candidates, this means you need to be thinking about your significant accomplishments (work-related please, unless you can make a