4 ms·
I usually start a project with a hard launch date. We decide what we want to build, and then decide which 80% we can strip out to meet this launch date. You m
by kappaknight 15y ago
I usually start a project with a hard launch date. We decide what we want to build, and then decide which 80% we can strip out to meet this launch date. You may not have to start with a hard date, but if your runway is limited, it may help.
Either way, this will help you visualize the minimal viable product and you can go from there.
- chris_dcosta 15y agoI agree with this. A hard launch date helps to give you focus, and decide what can realistically be achieved by that date. It doesn't mean that your other features are discarded, it just means that you can get to where you need to be at the right time. One other thing it does too is give you an opportunity to stand back after the deadline has passed and look at the project with fresh eyes. For example, at the outset you aim at getting the ting up and running. Then once you are there, switch hats and become a user. Is the thing doing what you need? Are there bit's you don't actually like? Why don't you like them? Would one of your missing features solve the problem? Or, do you just drop that irritating feature? I think this can only happen if you set the date, execute, and then step back.