New feature pitfalls

New features or products are exiting, and can get a disporpotionate amount of attention. Developers are often more engaged when tackling new concepts and code, while the account managers and sales teams are anxious to present the added value to the customer.

New features are wonderful, but can distract from more important updates.  A new feature is presented, and a flood of enhancement ideas rush in.  A common trap is when improvements on a new feature take priority over more important updates. Backlogs get re-prioritized to focus on enhancing a new feature that customers have barely seen without  considering of the value added to the product.

New features have the lowest amount of customer feedback or any demonstrated sales data. A development manager/product owner should consider postponing any updates on a finished, new feature for a few sprints. A month of reflection and additional customer feedback can radically change the direction of the new feature.

Advertisements
This entry was posted in Product Management, Software Development. Bookmark the permalink.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s