In terms of the assertion that, "..both early adopters and system integrators have so far had a tendency to underestimate the complexity of the (SharePoint) platform and very few have delivered on time and on budget," we actually deployed an outward facing publishing portal, last January, for a site that averages nearly 300K page views per month. It was only slightly over budget and it was only delayed by about two weeks as compared to the original project/deployment plan.
I do concur that there is quite a bit of customization required to derive list and usage date (a la SQL Reporting Services), but overall, I am very pleased with our deployment. Our phase II enhancements were, however, quite a bit more unruly, with about a 10% cost overrun and a one-month deployment delay. However, most of our customizations have been limited to the dynamic display of formatted list data within various Web parts, but the few third-party Web parts we've deployed are very stable. We have learned, though, that CAML querying is definitely an art, not a science.
Until SP 1 -- and later MOSS 14 -- are released, I won't have a good sense of the impacts that our customizations have had on our upgrade path. However, per our Gold Certified development partner, everything we've done has followed MSFT's best practices/recommendations.
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
