I'd agree with this assessment. New Features are bigger pieces of work -- more design, documentation, marketing, etc. Improvements are smaller bits of work. Still may need some documentation tweaks, but these type of changes would not make a big splash with marketing.
On 2/5/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
I like to reserve New Feature to high level new stuff that should be marketed. Normally, I like to break these down into bite-sized sub tasks. Most other changes are bug fixes or iterative improvements to the code base. -dain On Feb 5, 2007, at 6:52 PM, Patrick Linskey wrote: > Hi, > > Does anyone understand what the difference is between an "Improvement" > and a "New Feature"? My hope is that "Improvement" is a strict > superset > of "New Feature". > > Should we strive to use "Improvement" rarely, only for bits of > functionality that exist but need to be nominally tweaked, and use > "New > Feature" for other things? Maybe "New Feature" is for things that will > need mentioning in docs etc, and "Improvement" is for things that just > need tweaks in code? > > -Patrick > > -- > Patrick Linskey > BEA Systems, Inc. > > ______________________________________________________________________ > _ > Notice: This email message, together with any attachments, may > contain > information of BEA Systems, Inc., its subsidiaries and > affiliated > entities, that may be confidential, proprietary, copyrighted > and/or > legally privileged, and is intended solely for the use of the > individual > or entity named in this message. If you are not the intended > recipient, > and have received this message in error, please immediately return > this > by email and then delete it.
