How to translate “business value” of things that are technically important

Posted . Visible to the public.

User Stories should describe what a user wants the system to do. Purely technical tasks should usually be implemented as part of a User Story. But, sometimes there are technical tasks which cannot be directly linked to customer value. Things like “Upgrade to MySQL 6.0″ or “replace magic numbers with enums” need to be done. How can you prioritize these critical chores against User Stories? How can you make the product owner aware of the importance of such tasks (and the business risks of procrastination)?

Last edit
Keywords
project-management, development, makandra
License
Source code in this card is licensed under the MIT License.
Posted by Lexy to makandra dev (2011-04-24 14:40)