Now reading: Integrating Program Management and Systems Engineering

Eric Rebentisch (editor), Integrating Program Management and Systems Engineering: Methods, Tools, and Organizational Systems for Improving Performance

I've had this one on my reading list since sitting in on a meeting of the INCOSE PM-SE Integration Working Group at a conference last year. (PM = program management, SE = systems engineering.) The topic is right there on a bridge that I'd like to build... or cross... depending on the day. But now I've bumped it up to the top of my reading list while working with the local PMI chapter to do a joint PM/SE online meeting in September. What topics to cover? I don't quite know yet—so let's start with the topics in the book, fan out on the references, and go from there. I'm thinking about how to get one SE and one PM and have them go at topics from their side of the fence, giving a little bit of perspective for the other side to consider. Stakeholder management will certainly be one. Certification might be another. Or not—or more. There's time yet to figure it out.

No one wants to admit it, because there's professional pride involved, but these two disciplines ("disciplines") are mostly the same thing, but with one side focusing a little more on time and the other side focusing a little more on technical content. At a big organization, they are separated to suit the hierarchy of the organization—nerds go this way, suits go that way. Go to a smaller organization and you'll see what it's really about—time and money and technical content are managed by the people who are available to manage them. Oh you're a program manager? That's great. Hold this screwdriver. Oh you're a systems engineer? That's great. Why is this equipment late and expensive? There's no magic in the title—your product is either in the box or not in the box when it's time to ship. If you need something to make you feel good about your role, get a dog.

Leave a Reply

Your email address will not be published.