<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d6651501\x26blogName\x3dNotes+on+tech\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLACK\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttp://ypjain-notesontech.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://ypjain-notesontech.blogspot.com/\x26vt\x3d8064441079851785414', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Notes on tech

Notes on technology, business, enterpreneurship, economy, markets along with interesting general tidbits.


Product management - CRWF philosophy

9/04/2005 07:37:00 AM, posted by anand

Charlie Woods describes a management philosophy that he has been applying to ruthlessly optimize the product development process. Its called "CWRF", for "crawl, walk, run, fly".

Version 1 of a product should crawl. This means it should do the bare minimum to be recognizable as what it's intended to be. If it's supposed to be a foo, and someone could look at version 1 and say, "That's a foo," you're done. Ship it.

Version 2 should walk. This is where you add enough functionality that the product is useful in day-to-day life. This is not the time for polish. Basically, it's just adding the things that most people insisted should have been in version 1, because without them, they said, the product is completely useless. They were wrong then, but they're right now.

Version 3 should run. This is where the product hits its stride. What it does it should do well. It should be comfortable to use. It should be strong, polished, and effective.

Version 4 should fly. This is where the, "Oh man, wouldn't it be awesome if..." features get added. This is where you start implementing things that aren't necessarily useful now, but have a lot of possibility.
« Home

» Post a Comment