write the MRD first?
ack/nak: rule: write the MRD first
quick quiz: How many of you Product Managers out there are doing this? What, we need more than a functional spec?
Heh.
ack/nak: rule: write the MRD first
quick quiz: How many of you Product Managers out there are doing this? What, we need more than a functional spec?
Heh.
January 25th, 2006 at 11:48 am
Eh. Whether this is 100% true all the time is up for discussion. Scope of work, amount of cross-functional coordination that needs to be done, amount of business risk associated with the product, profile of the product, and the extent to which the product departs from what your business has done in the past should all factor in to how much pre-planning you do.
There’s a time for airtight coordination, and there’s a time to get stuff out the door.
January 26th, 2006 at 1:26 pm
Yes, there is a time to think “don’t worry, be crappy” and get something out the door. But if you are spending limited resources on development, you darned well better have a defensible business reason for doing it.
Building software without an explicit understanding of what you plan to accomplish with it is something you do as a hobby, not as a business.