On Tue, 2006-04-25 at 14:01 -0500, Patrick W. Barnes wrote: > Thus far, I've tried to use simple classification to separate efforts that are > organized and worthy of things like meetings and efforts that are young or > too small or simple to warrant meetings and committees. Although I haven't > stuck to it 100%, and can't provide specific guidelines, I've tried to > classify the former as "projects" and the latter as "programs". I've had to > do this in order to maintain related wiki pages and to establish the > relationships between many of the smaller efforts. The problem with this usage is that it is the exact opposite of the usage of the two terms in project management.[1] A program is a large, overarching project that consists of multiple projects. A program manager is a PM over many projects that have their own PMs, etc. If we use this language backwards from the way the rest of IT uses it, we're more likely to foment confusion. [1] I just made Jeremy's blood pressure go up a few ticks, but recall that there are always useful things to learn from a discipline even if you don't adhere to it. - Karsten -- Karsten Wade, RHCE * Sr. Editor * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Fedora Documentation Project http://fedoraproject.org/wiki/DocsProject Learn. Network. Experience open source. Red Hat Summit Nashville | May 30 - June 2, 2006 Learn more: http://www.redhat.com/promo/summit/
Attachment:
signature.asc
Description: This is a digitally signed message part