Welcome to TechNet Blogs Sign in | Join | Help

BillCan's Place

Life at Microsoft
Cross-Group Collaboration Training Tomorrow

With everyone back from vacation, my project has kicked into high gear.  I've not been as good as I should be on posting, but things are a little crazy.

I will fill you in on a training session that I am going to tomorrow.  It is called "Cross-group Collaboration" and is apparently one of the hottest classes at MS.  I have learned that working as a PM at Microsoft requires working extensively with other groups (e.g., test, marketing, product management, documentation, localization, etc.)  All these groups have different drivers, and although we are all working toward the same goals, it is sometimes difficult to get the other groups to work with the same urgency that you have, especially when they are getting similar requests from 10 different PMs.

This class will hopefully provides some tips about how to make this situation work for both teams.  If nothing else, it ensures that all the PMs that are communicating and negotiating are doing so from a similar frame of reference.

I'll post later what I learned in this class.  In the meantime, I'll mention that I've been re-reading the classic book "Getting to Yes" by Roger Fisher and William Ury.  This is a great reference book for negotiating, and I can personally attest to the value of its recommendations.

Posted: Thursday, January 06, 2005 4:59 PM by BillCan

Comments

Sheeshers said:

I work at a company with more managers than real developers

(by the way, real developers = developers - useless developers).

But with that many managers, the issue isn't limited to just a management tug of war. The real developers get dragged into it as well. Several often receive emails and/or visits from more than just their immediate supervisor telling them tasks that are "extremely urgent" and require immediate attention. In such cases, it's the PM's job to make sure their team stays focussed and is not feeling pressurised to stray from the objectives.

What are your thoughts on this? Does this routinely happen in an organization like MS? Lastly, I'd be interested in knowing if this class you're going to covers this at all.
# January 6, 2005 6:07 PM

Bill Canning said:

In my opinion, a PM's responsibility is to do everything required to keep the project moving forward and complete the project. This should definitely mean sheltering the devs from being randomized. It also means keeping business owners or product managers from asking for features, etc. (devs are notorious pushovers for these requests, aren't they?!)

I will let you know what is covered in the class tomorrow.

# January 6, 2005 10:40 PM
Anonymous comments are disabled
Page view tracker