<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Peanut butter and software planning</title><link>http://blogs.msdn.com/brada/archive/2005/11/21/PeanutButterInSoftwarePlanning.aspx</link><description>One of the reasons planning software projects is so much fun is that there are tons of inputs… customer requests, what the competition is doing, what the business needs to grow, supporting other groups at the company, our own personal pet peeves about</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Peanut butter and software planning</title><link>http://blogs.msdn.com/brada/archive/2005/11/21/PeanutButterInSoftwarePlanning.aspx#495735</link><pubDate>Tue, 22 Nov 2005 17:55:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:495735</guid><dc:creator>Walter Lounsbery</dc:creator><description>The decisions you talk about are broadly valid, but I think ignore the real benchmarks and drivers.  We would all like to decide on resource allocation based on logic and the best information at hand from the development perspective.  That set provides enough hard work and has logically defined limits.&lt;br&gt;&lt;br&gt;But if we produce a product, it is meant to be consumed.  There is a customer who makes their decisions differently and is the ultimate arbiter of significant support and features.  That is the only real driver, and the one that is least quantifiable.  Especially when it comes to new key features that excite the development team.&lt;br&gt;&lt;br&gt;Maybe that's why I like the Web application arena.  It's a lot easier to establish short delivery cycles and feedback channels!  When .NET first appeared on the scene, it looked like workstation software delivery could get more like Web applications, and Microsoft would support that.&lt;br&gt;&lt;br&gt;So my meandering bottom line suggestion: keep improving the great deployment and support story for .NET workstation software!  The rest will fall out from listening to the customer and acting on that in a reasonable way.&lt;br&gt;</description></item><item><title>re: Peanut butter and software planning</title><link>http://blogs.msdn.com/brada/archive/2005/11/21/PeanutButterInSoftwarePlanning.aspx#495755</link><pubDate>Tue, 22 Nov 2005 18:30:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:495755</guid><dc:creator>Val Savvateev</dc:creator><description>&lt;a rel="nofollow" target="_new" href="http://blog.onthematter.com/archive/2005/11/22/26.aspx"&gt;http://blog.onthematter.com/archive/2005/11/22/26.aspx&lt;/a&gt;&lt;br&gt;</description></item><item><title>re: Peanut butter and software planning</title><link>http://blogs.msdn.com/brada/archive/2005/11/21/PeanutButterInSoftwarePlanning.aspx#495837</link><pubDate>Tue, 22 Nov 2005 21:05:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:495837</guid><dc:creator>BradA</dc:creator><description>You are right Walter – you still have to do what customers want or more specifically what customers will value.  That is fundamentally how you pick the few areas you invest in.  Think of the target customer (maybe new or existing customer base) what are the few things that really get the excited?  Focus just on those.  &lt;br&gt;&lt;br&gt;To Val this concept of no-peanut butter is self-evident.  No one that wanted to make money would peanut butter.  But I have seen software projects that make lots and lots of small investments… each one doesn’t look like it takes away from the “big things”, but in sum it is a huge drain.  So I am arguing for a more extreme approach… Do zero, none, zilch features outside of the target area..  &lt;br&gt;As far as their being no such thing as good and bad – well, I will not go their in this blog ;-)&lt;br&gt;</description></item><item><title>re: Peanut butter and software planning</title><link>http://blogs.msdn.com/brada/archive/2005/11/21/PeanutButterInSoftwarePlanning.aspx#495858</link><pubDate>Tue, 22 Nov 2005 21:39:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:495858</guid><dc:creator>Val Savvateev</dc:creator><description>Brad, don't get me wrong, I sympathize your idea of &amp;quot;no features outside the target area&amp;quot; and believe that the most, especially the developers here, will like it as well.&lt;br&gt;The truth is, my company had a number of &amp;quot;quality improvement&amp;quot; releases. The scope for those included a couple of &amp;quot;big fish&amp;quot; items, but the majority of work was devoted to exactly &amp;quot;face-lifting&amp;quot; all across the application (i.e. bunch of fixes such as changing colors, button placements, corky error messages etc). When the user experience can be improved at a relatively low cost, I kind of like that too. I don't know if this example falls under the &amp;quot;peanut buttering&amp;quot; category however, because we were still trying to please the customer (and so, keep being customer-aware) with a reasonable amount of effort.&lt;br&gt;I'm glad you didn't take the &amp;quot;no good or bad&amp;quot; idea seriously - that was a tongue-in-cheek conclusion (wanted to see if somebody gets into the trap).</description></item><item><title>re: Peanut butter and software planning</title><link>http://blogs.msdn.com/brada/archive/2005/11/21/PeanutButterInSoftwarePlanning.aspx#503741</link><pubDate>Wed, 14 Dec 2005 23:29:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:503741</guid><dc:creator>JD</dc:creator><description>I think that's wrong, Brad.&lt;br&gt;&lt;br&gt;Peanut butter is needed, but you only put one flavor of Jelly on top of it. The jelly is your sweet new single-focus improvement, but make sure you've got a nice layer of peanut butter down there of solid improvements for your base.&lt;br&gt;&lt;br&gt;In 2.0 for example, wow generics are sexy. Awesome. But hell yeah I like the peanut butter of wrapping non-Exception exceptions (removing the need for catch{} mostly) and fluff like string.IsNullOrEmpty).  You can try to argue that those were targetted too, but in reality there's a grab bag of small improvements that really affect people, and they don't add up to some grand Vision or Feature or Target. They're just peanut butter.&lt;br&gt;&lt;br&gt;All peanut butter can be hard to swallow, and all jelly can be too much sweetness for the adults. The mix, though, is surprisingly good.&lt;br&gt;</description></item><item><title>冒似我创造了一个新词汇：浇花生酱（peanut buttering）</title><link>http://blogs.msdn.com/brada/archive/2005/11/21/PeanutButterInSoftwarePlanning.aspx#8955111</link><pubDate>Wed, 17 Sep 2008 11:14:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8955111</guid><dc:creator>Joycode@Ab110.com</dc:creator><description>&lt;p&gt;【原文地址】 Looks like I created a new word: Peanut Buttering 【原文发表日期】 03 September 08 09:28 回到早先在做VS2008计划的时候&lt;/p&gt;
</description></item><item><title>Looks like I created a new word: Peanut Buttering</title><link>http://blogs.msdn.com/brada/archive/2005/11/21/PeanutButterInSoftwarePlanning.aspx#8970323</link><pubDate>Tue, 30 Sep 2008 17:20:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8970323</guid><dc:creator>Programming</dc:creator><description>&lt;p&gt;Back in the early days of VS2008 planning, I captured some of our thoughts on planning and looks like&lt;/p&gt;
</description></item></channel></rss>