PS 2002 versus 2003

A

Aardemen

We are looking to articulate to a customer the feature differences and
improvements between 2002 (currently in place at this site) and 2003 (being
considered for an upgrade) and I was hoping that there might be some old
(pre-2007 marketing days) content somewhere that could speed and simplify the
process. (and save all the cutting, pasting, formatting and editing from
different sources) All the material I can find is already 2007-centric and
doesn't do much of a historical comparison of the earlier versions.

Also, is there a direct upgrade path from 2002 to 2007 or is there a
required stop at 2003 first?

TIA
 
A

Aardemen

Well, I've confirmed what I believed about needing to be at MS Project Server
2003 SP2a in order to ultimately get to 2007. I'm still chasing a lot of
threads about the feature / fixes between 2002 and 2003. If anyone has some
old material on that, I'd really appreciate being pointed to it.
 
B

Ben Howard

If you download the EPM2003 solution guide from
http://office.microsoft.com/en-us/epmsolution/HA102122691033.aspx you'll be
able to see the (as was) new features of 2003 :)

From memory, the main differences were

1. Improved WAN perf between 2002/2003 (option in Pro not to load summary
resource assignments, better views perf in WSS).
2. Ability to have proposed bookings.
3. Multi value skill assignments.
4. Support for larger no of projects (2002 was based on STS which has a
site number limitation, 2003 on WSS)

Cheers, Ben.
 
A

Aardemen

Thanks Ben. I'll certainly grab this to see if I can pull what I need.

I am still hoping that there is some legacy marketing piece that already
does this that someone can find or point me to, but this will be a big help.
 
B

Ben Howard

Hi, AFAIK there isn't. MS doesn't trash it's old products when it releases a
new one, it just points out new/improved features, which is what the product
guide does. You'll find all there is in there.
 
G

Gary L. Chefetz [MVP]

Aardemen:

2003 is essentially the same product as 2002, except with the most egregious
errors corrected and the 2003 system is much more stable. It shouldn't be a
question of marketing, it should be a question of choosing a stable product
over a flaky one.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
 
A

Aardemen

Thanks for the response Gary. That's exactly what I am trying to get across
and why I am seeking specific examples of what was fixed / improved and
how...etc. I have a number of raw documents now that I am processing to try
to provide a clear, concise picture.

Thanks again.
 
G

Gary L. Chefetz [MVP]

I hate to say it, but that's a bit of a fool's task becuase Microsoft
doesn't publically document its flaws. Try to convince your users that peer
experts in the field, with no particular connection to Microsoft and nothing
to lose or gain by the recommendation, are telling you this.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
 
A

Aardemen

Hi,

Thanks for the reply. I know that there are never any MS "bugs", only
"features" so what I was looking for was as concise a list as possible of the
DEFECTS resolved in 2003, as well as a marketing doc that would say all the
great things now in 2003 (and it would have to compare to 2002) more than
just a list of 2002 flaws.

I was able to pull together most of what I needed and can now show them
something in "exec-speak" versus "tech-talk" and most likely get them to move
up.

thanks to all...
 
Top