The Delay in BusinessObjects 4.0: Small Tweaks or a Big Overhaul?
by Scott Wallask, Managing Editor, BusinessObjects Expert
July 21, 2011
One thing is clear with the delay of general availability for BusinessObjects 4.0: SAP is still working on the release.
If you deal with SAP software, chances are you’re used to delays, so news that the general release of BusinessObjects BI 4.0 has been pushed back until at least August isn’t a surprise.
I never know what to make of these fluid dates. Does a change indicate that SAP simply wants things just right with its latest BusinessObjects offerings? Was a bug uncovered? Were companies involved with the release’s ramp-up unhappy with what they saw?
You can tell some folks are itching to try out BusinessObjects 4.0 and have expressed aggravation at the delays. For them, the August release is like being told a long-awaited movie sequel isn’t hitting the screens on time. Hold the popcorn for BusinessObjects 4.0.
Others, however, seem content to wait for SAP to release the software, regardless of the schedule. Like awaiting your order a restaurant, sometimes it’s worth letting the chef get the full presentation ready for your meal.
For the record, John Schweitzer, senior vice president of business analytics for SAP North America, told ASUG News that SAP “is not going to deliver something that’s not great.” Clearly SAP’s teams are still working on final adjustments to the product.
Time will tell whether BI 4.0 needed just a dash of salt or a major re-edit of the film. But either way, the clock is now ticking for BusinessObjects 4.0’s general availability, and further missed deadlines may raise eyebrows given how much hype this release has under its wings.
Follow Scott on Twitter @BObjExpert or email him at scott.wallask@wispubs.com
Please
upgrade your license to comment on premium content.
Comments
Write your own comments
How do you rate this article?
Write a headline for your comments (optional)
Write your comments here (optional)
Enter your name as you would like it displayed alongside your comments (optional)
Enter the code below: