Deprecated: Assigning the return value of new by reference is deprecated in /home/warped/public_html/sfdc-heretic/wp-content/plugins/codesnippet/codesnippet.php on line 248

Strict Standards: Non-static method GoogleSitemapGenerator::Enable() should not be called statically in /home/warped/public_html/sfdc-heretic/wp-content/plugins/sitemap.php on line 2452
Salesforce Heretic » Dare to Dream…

October 6, 2006

Dare to Dream…

Filed under: Salesforce.com, The Soapbox — heretic @ 1:51 am

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-content/plugins/codesnippet/codesnippet.php on line 260

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-content/plugins/codesnippet/codesnippet.php on line 261

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-content/plugins/codesnippet/codesnippet.php on line 262

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-content/plugins/codesnippet/codesnippet.php on line 263

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-includes/functions-formatting.php on line 76

I’d be hard pressed to find a Salesforce customer who doesn’t know there’s 3 days until the start of Dreamforce now… You could barely miss the advertising — something akin to using a nuclear warhead to clear out a tree stump. If you want to meet me I won’t be at Dreamforce this year. My operatives will be in place, so I’ll pass along anything major that goes public. Me and 50 other blogs. ;)

I haven’t been very deep ‘in the loop’ with this release like I normally try to be. It’s a culmination of a number of factors, but mostly I want to take a step back and really evalaute this release without all the inside information and getting caught up in the hype and anticipation. So in keeping with that idea I won’t be blogging anything dreamforce specific, however I do plan on scoring the new release.

Yes, scoring.

Herein likes the fun. I’ve been kicking around a scoring-chart amoung some other SFDC admins and consultants for the last few days getting opinions on how I’m weighting things. Every time I kick it around I make so many changes it goes back out and around and around and around. So My plan is to publish my scoring rules and template over the weekend before the conference so everyone can score along at home (or at the keynote / hands-on). But the current system works something like this:

  • The system scores on a 100 point scale. I’m a brutal scorer so frankly a 100 would be neigh impossible. Anything above 65 would be probibly be passing, but that’s me.
  • It’s broken down into mutiple sections, each worth some fixed portion of the total:
    • Innovation - Maximum 20 Points
      • Each truly innovative feature or addition (AppExchange would be one from last year, formula fields would be iffy, and the new UI would not), up to 4, could get 0-5 points each.
      • If you have more then 4 items for this category, the top 4 scored items would apply.
      • Items in this section (new features) can be used in other sections.
      • If you have less then 4 innovating items, fill with zero.
    • New Features - Maximum 50 Points
      • For each new feature, that you can use, (I.E. Any API additions would be moot if you’re on Team Edition) you would score it as follows
        • (1 to 10) Weight the features importance or applicability to your org
        • (-5 to +10) Estimated productivity loss or gain from this feature
        • (0 to +10) How likely are you to implement this feature
          • Forced features, things that are on at release and can’t be disabled get 10pts
        • (-5 to +5) If there is an added cost (changing editions doesn’t count) rate the estimated value for your money.
          • Cost is amount you pay to SFDC or partner for the feature
          • The PRM AppForce extension announced in the last *cough* release *cough* would be an example
          • Internal cost to code an API enhancement, for example would not count
          • Break even would be 0 points.
        • (0 or +5) Does this feature solve a problem or limitation you’ve had in the past?
        • (-5 to +10) Estimate how complete this feature is. Are there any obvious limitations that will require workarounds or cause other issues?
          • This early in the release cycle obvious showstopping limitations would warrant a negative score.
        • (0 to +10) How will your users adopt to the change?
      • Using the weight you gave each feature, take the weighted average for the section score out of 50 points.
    • Bug Fixes - Maximum 20 points
      • There’s value in not having to deal with users problems because of bugs in the system. Can you really put a point value on piece of mind?
      • Take your list of top 10 bugs in the system. If you have less then 10 for each one under 10 score +2 points. (8 bugs = +4 points to start with)
      • For each bug
        • Fixed +2 points
        • Mabye fixed (some feature or enhancement has altered the area the bug occured in, or it’s not clear) 0 to +2 - judgment call.
        • Not fixed 0 points
          • If the bug was reported over 6 months ago -1 point
          • Over 1 year ago, -2 points
          • Over 18 months ago -3 points
      • Your score cannot be < 0 for this section.
    • Delivery Timeline - 5 points
      • Give 5 points if you think the timing of the release is excellent
      • 3 points if it’s a bit too long out
      • 0 if it’s just too far away
      • If no timeframe is announced give 5 points.
    • Overall Impressions - 5 Points
      • Give your overall impression to the release on a scale of 1 to 5.

I will likely alter this system a bit before I settle on it. Your opinions are welcome.

License

This work is published under a Creative Commons Attribution-ShareAlike 2.5 License.


Strict Standards: Only variables should be assigned by reference in /home/warped/public_html/sfdc-heretic/wp-includes/functions.php on line 590
« The AppExchange…  
Strict Standards: Only variables should be assigned by reference in /home/warped/public_html/sfdc-heretic/wp-includes/functions.php on line 590
“You had me at Apex”… Well, almost. »

1 Comment


  1. Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-content/plugins/codesnippet/codesnippet.php on line 260

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-content/plugins/codesnippet/codesnippet.php on line 261

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-content/plugins/codesnippet/codesnippet.php on line 262

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-content/plugins/codesnippet/codesnippet.php on line 263

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/warped/public_html/sfdc-heretic/wp-includes/functions-formatting.php on line 76

    […] As I previously covered in my “Dare to Dream” blog entry I outlined a scoring system for the Winter ‘07 release. Now that Dreamforce has passed, and hopefully those at Salesforce.com are well into the post-Dreamforce recovery period we can take a look ahead into the new release. Scott Hemmeter over at Arrowpointe wrote a nice summary of the announced features over on his blog. […]

    Pingback by
    Deprecated: Function ereg() is deprecated in /home/warped/public_html/sfdc-heretic/wp-content/plugins/google-analyticator.php on line 272
    Salesforce Heretic » “Survey Says….” Winter ‘07 Preliminary Scoring… — October 16, 2006 @ 9:56 am

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.