When my team writes features, I want them to be sure to at least think about - and typically actually write - things like key Acceptance tests, a short narrative about the market problem the feature solves (could be in user story form), and how the feature affects key areas of the product (e.g., reporting, upgrades, backward compatibility, searching - plus lots more specific to the specific product). Today I can copy an existing feature as a template, but that means I can't use that lovely big "+" button that's so appealing.
This enhancement would be used all the time - every time I or one of my team members created a feature. And the result would be better feature specifications, because they'd always have an Acceptance test - or clearly be missing one - and they'd always have something done on the list of impact areas, and they'd always provide the motivation - the customer or market problem - for building it. My features would be higher quality, engineering would have a much better idea what to build and why, and my company's revenue and profit would accelerate.
|Release time frame|
We agree with this and have an existing feature planned to allow for templates.