Jump to content

Talk:Program management/Archives/2013

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia


Program Management at Microsoft

Microsoft has a slightly different definition for Program Managers. It's more of a "vision thing" for them. As more and more MS alumni leave and start companies of their own, they are taking this definition with them and implementing it in their software development organizations. I've seen it first-hand. Someone should add a description like this but that isn't a copy-paste of MS HR's description. When I have time, I will try, but I'm banking there are more qualified people than me in the software development world to do this. Exbuzz 01:48, 22 February 2007 (UTC)


Here is a good description from someone that used to be a Program Manager at Microsoft: How to be a Program Manager. Leegrissom (talk) 20:26, 13 September 2009 (UTC)

"Program Manager"

Also, when I search for "Program Manager" I get a description of the old Windows shell. There should at least be a disambiguation that could lead here. Exbuzz 01:48, 22 February 2007 (UTC)

The 5th paragraph could probably be removed. This page doesn't define the meaning of "program". Arjscott (talk) 07:49, 13 February 2008 (UTC)

'The distinction between the terms "outcome" and "output" is far from clear'

Whose leg are the authors trying to pull here? It's sentences like these that help destroy the last remaining trace for any trust in "management". The question must be allowed whether this treatise couldn't be reduced to roughly 4 sentences without any conspicuous change in substance. -- Kku 11:15, 27 April 2011 (UTC)

Project vs Program - Simplified View

A simplifed way of distinguishing the two in this context could be (I'm not claiming the following to be perfect):

A Project:
- Time limited
- Fairly fixed amount of people (resources) to perform the work
- Fairly fixed scope (lets build a house or in software, this solution)

A Program:
- Not time limited per definition (can go on in perpetuity if need be...), I.e. continuous development of a software product (of course there can be tangible goals attached along the way...)
- Large shift in amount of people (resources) over time (scale up and down depending on market reality)
- Scope not fixed, but rather success is measured by some more abstract KPI (e.g. market increase by 5%...)
— Preceding unsigned comment added by 80.244.92.186 (talk) 20:30, 20 May 2013 (UTC)


This article needs serious editing and more objectivity. It is clearly written from a British perspective and with a nearly propagandistic style for British Public institutions. — Preceding unsigned comment added by 90.244.5.71 (talk) 23:24, 24 June 2013 (UTC)