News for hackers. Stuff that matters.
Re:Why I left Microsoft by amichail on Monday January 18, 2010 @11:38AM (#1060159)
What does a program manager do all day?
Re:Why I left Microsoft by raganwald on Monday January 18, 2010 @11:51AM (#1060205)
Traditionally, program managers say "What" and "Why," project managers say "When," and development managers say "How" (which encompasses "Who"). I guess facility managers used to say "Where," but that's stretching things...
Re:Why I left Microsoft by luminary on Monday January 18, 2010 @08:09PM (#1061230)
While recently interviewing for a similar position (Program Manager) at Microsoft, I told the interviewer that it's also important to get a feel of your competition 1 month/1year from the present by following the angel and VC investments. He got so turned off that I felt I just bombed the entire interview.
Re:Why I left Microsoft by brown9-2 on Monday January 18, 2010 @01:38PM (#1060529)
I always get lost on the difference between "program manager" and "product manager".

Is there a standard breakdown between these two?

For some reason I have the feeling that Microsoft popularized the usage of these titles - does anyone know firsthand if this trend started at Microsoft?

Re:Why I left Microsoft by osipov on Monday January 18, 2010 @03:30PM (#1060746)
"program manager" title has a long of history, it existed way before Microsoft was around. In the 1st half of 20th century, the common use of the word "program" was to describe an allocation of resources like manpower, production capacity, equipment, typically in the military setting. For example, the term "linear programming" as a mathematical optimization technique is based on using "programming" in the sense of allocating resources.

So historically, program managers handled decisions about how to allocate resources to accomplish a mission. These days, program managers usually allocate resources over a portfolio of projects and decide whether projects are helping to achieve the program's mission.

Product manager has a responsibility for one or more products and associated strategic and executive decisions , around business plan, marketing, sales, research and development.

Re:Why I left Microsoft by amichail on Monday January 18, 2010 @12:00PM (#1060231)
Wouldn't development managers and developers resent having program managers around telling them what should be built?
Re:Why I left Microsoft by raganwald on Monday January 18, 2010 @12:07PM (#1060252)
Well, no. If you're a developer or development manager working 70-90 hours a week developing and/or managing other developers, when do you have time to evaluate the market, keep track of every single competitor and potential competitor?

Do you run a spreadsheet loaded up with market data and demographics evaluating the potential revenue impact for all of the features you're thinking of including in the next release?

And so on and so forth. Product management is a full-time job on a substantial product. It may be that in small start-ups people wear many hats and you don't need it as a separate function. But if your team ever gets to the point that you can justify a full-time development manager, your team probably needs someone else with nearly full-time product management responsibility.

In addition to that, there are sometimes some benefits to separating product management from development management. Sometimes. Being a little divorced from the product's inner workings can provide a certain useful perspective. Hopefully, the product manager isn't wedded to the feature that a developer just spent three weeks building and can jettison it to ship on time :-)

Re:Why I left Microsoft by bmj on Monday January 18, 2010 @12:47PM (#1060370)
Product management (at least where I am) also does a fair bit of marketing work. They tend to shape the overall product, but all technical decisions are made by engineering, not marketing.
Re:Why I left Microsoft by amichail on Monday January 18, 2010 @12:13PM (#1060279)
You are thinking of what's best for the company, not the developers. For some people, development is only rewarding if they determine what to build.
Re:Why I left Microsoft by mahmud on Monday January 18, 2010 @12:23PM (#1060313)
Yes, and those people are called hobbyists.

Even if you work for yourself, you decide which market to be in, and the market decides what you must build and when.

Re:Why I left Microsoft by raganwald on Monday January 18, 2010 @12:25PM (#1060321)
Sure. I don't have some belief that all developers are incapable of product management. The very best, IMO, have strength in understanding what and why as well as how. But I do have a belief that in some cases, there is value for everyone in having a team with specialized roles. For all products there is a need for product management. And for some product teams, there should be a specialized product manager leading product management.

Interestingly, the push to smaller start-ups and smaller teams does create more opportunities for developers to wear multiple hats. That's a good thing too.

Re:Why I left Microsoft by rmaccloy on Monday January 18, 2010 @12:21PM (#1060306)
Then they should work somewhere they can do that. Most likely that's a small company or a startup.
Re:Why I left Microsoft by wgj on Monday January 18, 2010 @12:55PM (#1060396)
Actually, I was at Microsoft between '94 and '05 and that's close to what happened in many cases, but not because of a single program manager. (At least not in cases that I saw directly.) Rather, as the company grew, and more program managers and project managers were assigned to things, a lot of developers felt less in control of their work due to the collective influence of a non-programmer organization.

That kind of growth probably has to happen. To be fair, most all the program managers had engineering degrees, and some had been successful developers. The project managers came from a different track entirely, and I think that was a more challenging relationship for a lot of developers.

Re:Why I left Microsoft by easp on Monday January 18, 2010 @02:07PM (#1060585)
If they had a problem with that sort of thing, then they shouldn't have taken a job at Microsoft, or even a corporation of modest size. Division of labor, and all that.

Besides, for a great many developers, dealing with a PM is better than dealing directly with people in finance and marketing, or customers themselves.

Re:Why I left Microsoft by ruff on Monday January 18, 2010 @12:50PM (#1060384)
Re:Why I left Microsoft by DanielBMarkham on Monday January 18, 2010 @11:41AM (#1060164)
I didn't RTA, but traditionally? Work with marketing, infrastructure, release, and project managers to create the program and ensure it stays on-track.
Re:Why I left Microsoft by amichail on Monday January 18, 2010 @11:44AM (#1060177)
What sort of authority does a program manager have?

Can't employees just ignore what he/she says?

Re:Why I left Microsoft by raganwald on Monday January 18, 2010 @11:50AM (#1060203)
If the only reason people pay attention to you is that you have the ability to fire them, you aren't much of a manager. I worked for years as a team lead. I had no authority to fire anyone, or dock their pay, the most I could do was to say nasty things about them like "They have their own independent ideas about how to get things done instead of genuflecting to me."

If he was a good program manager, people would have respected what he did, which was to understand the market for the product so well that he could inspire and lead the team to build the right thing at the right time.

Re:Why I left Microsoft by DanielBMarkham on Monday January 18, 2010 @11:58AM (#1060225)
Depends on the company. Since a Program Manager sits above multiple projects, some companies think of them as just a coordination role -- a little more than a PM but not yet a director. But other companies think of them more like super-PMs, parachuting into their poorer-performing projects and taking over until the PM and the team can get their act together. In these tougher Program Manager roles, they're responsible for the day-to-day life-or-death of the project.

Sadly, more companies are leaning to the idea that the Program Manager is more like a fancy clerk. They end up pretty stressed out and under-appreciated.

This gets to the central question: How do you create, run, and release a huge effort that might take hundreds of man-years, like Office 2012? Something like that covers a lot more ground than simply kicking out some code. There are all sorts of things that need to be coordinated.

Companies are still sorting through how to set up and run programs, in my opinion. There is a LOT of room for screwing things up between 5 guys and 150 guys. There are a lot of tricks to use, but many times people want simple answers and the simple answers are not forthcoming.

A lot of time employees just go to their PM and then go around the Program Manager directly to the higher-ups in the organization. Makes the whole thing quickly devolve into a Charlie Foxtrot.

(Disclaimer: I've done quite a bit of setting up programs and helping companies manage them)

EDIT: I've describe a Program Manager as being "over" the entire effort. Some companies just kick them out to the side of the whole thing. This is an even worse setup, because the business drivers aren't directly connected to the work.

Re:Why I left Microsoft by nostrademons on Monday January 18, 2010 @04:16PM (#1060848)
"How do you create, run, and release a huge effort that might take hundreds of man-years, like Office 2012?"

I think that more and more, companies are realizing that the answer to this is "You don't."

Google Chrome is a good example. Instead of trying to figure out exactly what needed to be in the product, they built a kick-ass updater (which is now open-source). One that let them transparently and efficiently download and install updates whenever necessary, so they could treat desktop software like a webapp.

And then instead of having to coordinate hundreds of man-years of work, they can have small independent teams that crank out a feature, release it, see if the feature works well, and back it out if necessary.

The best way to deal with an O(N!) problem is to keep N small.

Re:Why I left Microsoft by robryan on Monday January 18, 2010 @07:00PM (#1061118)
Their worlds apart though, enterprise would be bringing in a lot of the money on Office, they'd want something they can roll out and only periodically patch, they want something they can rely upon from day one.

Chrome is a free product that already achieves it's main aims, if chrome was a $200 browser or something I'd imagine it would have to conform to the big release idea to.

Re:Why I left Microsoft by nostrademons on Monday January 18, 2010 @07:20PM (#1061162)
Chrome got out of beta before GMail because Chrome has a bunch of OEM deals. I don't know the terms of those deals, but I imagine there's money changing hands, and that they are of strategic importance both for the OEMs and for Google:

http://news.cnet.com/8301-13846_3-10106174-62.html

There's some resistance to using auto-updating software in enterprises simply because it's not the way things have traditionally been done, but IT departments are warming up to it. The huge pain of doing a major upgrade and the constant security fiascos that come from using software that's 5 years out of date are a major incentive for departments to switch to a model where individual changes can be canaried and tested in isolation before bringing down the whole enterprise. Google Docs is certainly having some measure of success in the enterprise arena, despite being a webapp with this development model. And outside of Google, Salesforce.com has revolutionized their market with a webservice-based enterprise app.

Re:Why I left Microsoft by jac_no_k on Tuesday January 19, 2010 @01:30AM (#1061642)
The resistance to auto updating software is the amount of risk involved.

If say Chrome was your sole web browser and an update broke compatibility with a business process, who is responsible?

It's a constant struggle to balance the business needs of predictable use and the need to stay competitive with up to date products. Mainframes and WinXP's default browser will continue to stay until the benefits can be clearly shown to out weigh the risks.