Vous vous attaquez à un projet de conception de système agile. Comment décidez-vous des commentaires des utilisateurs à prioriser ?

Assess the number of users affected by the feedback. Feedback impacting a larger user base generally takes precedence. Consider the severity of the issue addressed by the feedback and how frequently it occurs.

Prioritize Widespread Issues: Focus on feedback addressing common problems. Enhance User Experience: Aim for changes that significantly improve satisfaction and engagement. Evaluate Impact: Consider how suggestions will affect user frustrations and add value. User-Centric Decisions: Ensure the product meets users' most pressing needs to make it loved and useful.

Ensure feedback aligns with the overall project and business objectives. Prioritize feedback that adds significant value to the user experience or system functionality.

Align with Business Goals: Prioritize feedback that supports critical business objectives. Increase Market Share: Move feedback up if it helps in capturing a larger market. Improve Retention Rates: Elevate feedback that enhances user retention. Weigh ROI: Consider the potential return on investment for implementing changes. Strategic Alignment: Ensure feedback aligns with strategic direction for overall business success.

That's true, we have to look into the technical feasibility of any use case. For a user it might be a feature but as a developer we have to think whether it is feasible to deliver or not based on system architecture. With all analysis, we have to prioritize the user feedback.

Technical Feasibility: Assess if feedback can be implemented within the current system. System Overhaul: Recognize that some suggestions may need significant changes. Prioritization: Focus on achievable feedback with existing resources. Balance: Weigh user needs against practical limitations. Realistic Implementation: Ensure changes don't compromise stability or incur high costs.

Prioritising user story has to be done by the developer with approval from the product team. User story changes, additional features prioritisation done by developer is good since he knows the technical challenges to implement the change.If it is production fix which has high severity has to be prioritised immediately based on user feedback.

Feedback Source: Evaluate the origin of the feedback. Key Users: Input from power users or key stakeholders may carry more weight due to their deeper engagement. Casual Users: Don't disregard feedback from less active users; they can highlight barriers to frequent use. Balanced Feedback: Balancing input from various user segments ensures a comprehensive understanding of system interactions.

Must have: Non-negotiable for system functionality or legal compliance. Should have: Significantly improves user experience, but not critical for launch. Could have: Nice-to-have features, added if time and resources allow. Won't have: Low-priority items, to be considered in future iterations.

Critical Bugs: Immediate attention. High Impact Features: From highly active users. Common Requests: From daily users. Strategic Enhancements: Aligning with long-term goals.

Evaluate the resources required to implement the feedback, including time, cost, and expertise. Assess whether the feedback can be implemented within the current technical constraints and architecture. Prioritize feedback that significantly enhances user satisfaction and experience. Focus on feedback that helps retain users and reduces churn.