Transparency - key to effective product development

re: Transparency - key to effective product development

James Snape — Fri, 12 Nov 2004 23:31:00 GMT

Whatever you're planning, sign me up :-) One thing I would add is that I find it pretty easy to evangelise the developer benefits (apart from the release dates :) but I'm struggling with the business benefits (to end customers) some help there would be of great use.

Transparency in Product Development

Eric Gunnerson's C# Compendium — Tue, 16 Nov 2004 03:44:00 GMT

re: Transparency - key to effective product development

Matt Garven — Tue, 16 Nov 2004 04:34:00 GMT

That's great - I love what I'm reading. Getting the product as right as possible the first time makes sense.

What happens once the product is released though? I work with a team of 50 developers using .NET and have found many bugs with both Visual Studio and the .NET Framework itself.

We've never had much luck with reporting the issues in newgroups and having them dealt with in a manner which corresponds with the ideology you've talked of in your post. We've always resorted to finding our own work-arounds, which doesn't benefit the community or improve your product.

So you release a great product, that's cool, but there are always more bugs to be found. What then?

re: Transparency - key to effective product development

Ricky Datta — Tue, 16 Nov 2004 19:17:00 GMT

Product Feedback Center

A feedback - most of the suggestions are
usually marked by Microsoft reviewers as

"Fixed and Resolved"

even though they do nothing about it.

So it is mostly useless feedbackk for suggestions.

Ricky

What build tools does Microsoft use?

vincem's WebLog — Wed, 17 Nov 2004 08:25:00 GMT

What build tools does Microsoft use?

vincem's WebLog — Wed, 17 Nov 2004 08:30:00 GMT

re: Transparency - key to effective product development

S. Somasegar — Thu, 18 Nov 2004 05:12:00 GMT

James, for Visual Studio 2005, we are still working on pulling together appropriate ROI information, case studies and other materials to help with what you are specifically asking for.

At Visual Studio 2005 Beta2, some of this material will start becoming available on-line.

re: Transparency - key to effective product development

S. Somasegar — Thu, 18 Nov 2004 20:58:00 GMT

MSDN Product Feedback Center is already having a meaningful impact on the work that our development teams are doing. Over time we expect it will be integral and critical to how we scope, design, build, release and service products. Mark Cliggett from our Customer Connection team talks about this in the PFC blog here (http://blogs.msdn.com/productfeedback/archive/2004/11/09/254712.aspx)

MBA

MBA — Sat, 18 Dec 2004 18:45:00 GMT

Helpful For MBA Fans.

Imperfect Feedback Loops

Panopticon Central — Fri, 29 Apr 2005 20:52:25 GMT

Imperfect Feedback Loops

Panopticon Central — Fri, 29 Apr 2005 20:48:30 GMT

Soma's Take on Transparency

One Agile Tester — Wed, 17 Aug 2005 08:29:58 GMT

In my quest to acclimate myself to the MS world, I&rsquo;ve been poking around a bit.&nbsp; Today, I...

Soma's Take on Transparency

One Agile Tester — Wed, 17 Aug 2005 09:38:41 GMT

In my quest to acclimate myself to the MS world, I&rsquo;ve been poking around a bit.&nbsp; Today,...

Personas don't review specs... People do

scooblog by josh ledgard — Mon, 01 May 2006 19:43:53 GMT

I've spent a lot of time bloviating on the Mort vs. Elvis thing. I got confused once, and thought I was...

More on transparency

The Feedback Loop — Fri, 18 Aug 2006 22:40:45 GMT

A quick followup to my&nbsp;earlier post about&nbsp;transparency and Microsoft. Back in 2004, Somasegar...

Soma's Take on Transparency

The Process Wonk — Fri, 23 Mar 2007 07:48:34 GMT

In my quest to acclimate myself to the MS world, I’ve been poking around a bit. Today, I found a great

Somasegar s WebLog Transparency key to effective product development | Paid Surveys

Fri, 29 May 2009 22:47:37 GMT

PingBack from http://paidsurveyshub.info/story.php?title=somasegar-s-weblog-transparency-key-to-effective-product-development