Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
If you’ve been following my blog for a while, then you’ve heard about these things we call “Power Tools”. You might have even tried them out and found out they could be darned useful :) We’ll if you’ve been following my blog long enough, you’ll know that at one point they were called Power Toys but we changed the name to Power Tools because we got a bunch of feedback that “Toy” was disturbing to people. Back in Sept 2006, I wrote a post that described the Power Toy philosophy (the philosophy didn’t change when we changed the name). And in November, I wrote a slightly higher level post positioning Power Tools in the overall pantheon of release mechanisms that we have.
Power Tools have been one of the most popular things we’ve done. They’ve been a terrific way to deliver cool value to customers quickly and relatively hassle free. They fill a need between product and free community content. They come with a promise that we’ll stand behind them and help you if you have issues and fix bugs that you run into. Some of them will even ultimately get incorporated into the product eventually.
For the last couple of years we’ve been feeling like there’s another gap in our release spectrum. That gap is between where Power Tools are now and “real product”. We’ve been feeling a need to have a way to release new features that essentially are part of the product but to do it without waiting for a full release or a Beta. We build a fair amount of stuff that is relatively stand alone and ready to deliver but because we want to treat it like “real product”, it has to wait for the next major release (which as you know happen about every 2 years). It’s not particularly fun for us and I know customers would rather get it sooner than later.
Our new term for this is “Feature Pack”. So what is a Feature Pack and how does it differ from other things? If you read one of my previous descriptions of Power Tools you’ll find them defined along the lines of:
Feature Packs are similar in some ways and different in others. As I said, they fill the gap between Power Tools and Product.
Feature Packs are like Power Tools in the following ways:
Feature Packs are more like Product in the following ways:
As you can see Feature Packs are a lot like product. Essentially, think of them as a way to deliver fully complete product features off cycle from the major releases.
One other difference between Feature Packs and Power Tools is that Feature Packs are not “free”. I wrote a post a couple of years ago about the role of Power Tools with respect to our various subscription options. Feature Packs are our first experiment in this vein. Only people who have current MSDN subscriptions will qualify for Feature Packs. As I’ve said, Feature Packs are like “real product” and as such they cost money like real product. I know many, many of our customers already have MSDN subscriptions and for you all it is going to feel a lot like “free” :) For those of you who don’t, you should seriously consider it. There’s a ton of value in MSDN and Feature Packs are just one more component of that value.
Very soon (like later today :)) I’ll be writing a post about or first Feature Pack. Keep your eyes peeled – it’s going to be unbelievably cool!
So does this mean that Power Tools are a thing of the past? Not at all. Also later today, I’m going to tell you about some awesome new Power Tools available from the VS Pro team (yep, they are joining the Power Tools bandwagon too). My team (TFS) is also hard at work on our next Power Tools release and I’ll let you know what is coming in that as soon as I can.