Applying Moscow on FuseBase User Stories

A prioritization framework is a structured method used to evaluate and rank features, tasks, or projects based on various criteria. Its main purpose is to help teams decide what to focus on first, ensuring that resources are allocated to the most important, impactful, and feasible tasks.

Prioritization frameworks consider factors like customer needs, business value, effort, and time to help make strategic decisions. They are especially useful in product development, project management, and other areas where there are many competing priorities like time, value etc (ProductDive 2023). The 3 most popular frameworks are; Moscow, Rice and Kano . I will be using Moscow in this article.

MoSCoW categorizes tasks into four groups: Must-Have, Should-Have, Could-Have, and Won’t-Have. It’s a simple framework that helps teams understand which tasks are critical and which can be deprioritized I.e it gives clear direction on which task to focus on first.

Must-Have: Critical to the product’s success; without these, the product fails.

Should-Have: Important but not vital. These add value and enhance user experience.

Could-Have: Nice-to-have features, but not essential for the first iteration.

Won’t-Have: Features that are explicitly deprioritized for now.

FuseBase User Stories of Day 8.

1. Real-time data updates

As a user, I want to see real-time data updates so I can make quick decisions.

Priority: Must-Have

Reason: Real-time data is likely core to the value FuseBase provides, especially in helping users make informed decisions efficiently. Examples of this real time data are network latency, tracking users last viewed page,CPU/Memory usage by documents stored.

2. Data export in CSV/PDF formats

As a user, I want to export data into various formats (CSV, PDF) for offline analysis.

Priority: Should-Have

Reason: While it is important for users who analyze data offline, the core functionality of FuseBase might not hinge on this, so it could be implemented after the essential features are ready.The core value of FuseBase lies in its real-time capabilities and online access to up-to-date information. Users can still work within the platform for decision-making, so exporting data is an enhancement, not a necessity for the core function. This feature adds convenience and value but is not essential for the initial launch. It can be added once the more critical real-time functionalities are working smoothly.

3. Customizable dashboard

As a user, I want a customizable dashboard to view metrics that are most important to me.

Priority: Could-Have

Reason: A customizable dashboard enhances the user experience, but it can be considered a secondary feature, especially in early development. In the later stage of development, Nimbus can upgrade the App to make Clients to design how they wants their dashboard to be attractive to taste but this is not the core of the functionality neither the means of making workflows effective or efficient.

4. Notification alerts for specific triggers

As a user, I want to receive alerts based on certain data thresholds so I can act quickly.

Priority: Should-Have

Reason: Alerts add value and improve responsiveness for users, but they aren’t as foundational as real-time data itself.

5. Detailed user analytics report

As a user, I want to have access to detailed analytics reports that I can use for long-term planning.

Priority: Could-Have

Reason: Analytics reports can be useful, but in the short term, this feature may not be as critical as real-time decision-making tools.

6. Advanced machine learning predictions

As a user, I want to provide predictive analytics to forecast potential trends in the data.

Priority: Won’t-Have

Reason: Machine learning is valuable but may require more complex development. It can be planned for future iterations when basic functionality has been successfully implemented.

Summary.

I use Moscow framework due to its simplicity and, easy comprehension. It does not involve any mathematical format like RICE and, it can even be applied to our Day-to-day expenses.

Must-Have: Real-time data updates

Should-Have: Data export, Notification alerts

Could-Have: Customizable dashboard, Detailed analytics reports

Won’t-Have: Machine learning predictions.