Start With Something Simple

MSDN Blog Postings » Start With Something Simple

MSDN Blog Postings » Start With Something Simple — Sun, 10 Feb 2008 05:37:30 GMT

PingBack from http://msdnrss.thecoderblogs.com/2008/02/09/start-with-something-simple/

Interesting Finds: February 10, 2008

Jason Haley — Sun, 10 Feb 2008 20:39:55 GMT

re: Start With Something Simple

Shoaib Yousuf — Mon, 11 Feb 2008 01:52:14 GMT

Hi,

Excellent technique....I tried and it really worked for me. I came to work and thought i can do my emails in fast and effective way so lets start it with it...I started and i was bit more productive.

Thanks for excellent post.

Cheers

Shoaib

re: Start With Something Simple

Wed, 13 Feb 2008 18:51:43 GMT

Hi,

I know your techniques is very effective. But we always have a choice between the easy one and the right one, in the domain of getting a small chunk of job to be done. After reading your blog, people might get confused and some might also make the easy choices.

In the domain of very big product to be released, such easy choices may deteriorate the quality of the product. I think you should also consider writing on how to make the right choice for your overall success.

Thanks,

re: Start With Something Simple

J.D. Meier — Thu, 14 Feb 2008 10:11:48 GMT

Hey Shoaib - great to hear! Momentum is a powerful thing. If you need a technique for clearing you inbox and keeping it empty, check out The Zen of Zero Mail - http://blogs.msdn.com/jmeier/archive/2008/01/14/the-zen-of-zero-mail.aspx

Hey G - I agree -- some people may make the easy choices. Some easy choices can certainly deteriorate the quality of a product.

I've been seriously debating writing a full-length guide on software success. I've had the benefit of meeting with a lot of experts that have been through the school of hard knocks. Personally, I've learned a lot of lessons by focusing on security and performance.

Off the top of my head, if I had to think of three things that could help folks make the right choices in building a product, I'd say:

1. Use scenarios. http://blogs.msdn.com/jmeier/archive/2007/10/15/why-scenario-driven-engineering.aspx

2. Know Kano - http://blogs.msdn.com/jmeier/archive/2007/12/31/kano-satisfiers-and-disatisfiers.aspx

3. Know what you're trading/balancing: user experience perspective, business value perspective and technical perspective.

If I could add another, I would probably say, use a Scenarios and Features matrix - http://blogs.msdn.com/jmeier/archive/2006/12/09/scenario-and-feature-matrixes.aspx

If somebody asked me for the real secret, which applies whether it's software or you name it, it would be adopting a mindset of "Time-boxes, Rhythm and Incremental Value" - http://blogs.msdn.com/jmeier/archive/2006/03/17/time-boxes-rhythm-and-incremental-value.aspx

OK, here's two more things:

- High ROI Security Activities - http://blogs.msdn.com/jmeier/archive/2005/10/11/high-roi-security-activities.aspx

- Threat Modeling - http://blogs.msdn.com/jmeier/archive/2007/12/20/getting-started-with-threat-modeling.aspx

BTW -- you can apply the raw concepts of threat modeling to any quality attribute (performance, reliability, usability ... etc.)

Effectiveness Post Roundup

Justin — Tue, 28 Oct 2008 13:45:12 GMT

导读今天发现了这篇非常精彩的，内容超级丰富的文章，实在忍不住，转载于此。

原文地址：http://blogs.msdn.com/jmeier/archive/2008/10/13/effective...