Priority Explanation – MoSCoW Method
To help our team allocate resources and time effectively, we use the MoSCoW prioritization method to define the urgency and importance of each user story. This method breaks down features into four categories:
- Must-Have: Initiatives that must not lack in your product.
- Should-Have: Essential initiatives but not vital in your product.
- Could-Have: Initiatives that are nice to have in your product.
- Won’t-Have: Initiatives that are not the priorities in your product.
Story Point
We use PlanningPokerOnline.com as a collaborative tool to estimate story points through team voting. Each team member selects a number representing their estimate, and the team discusses discrepancies to reach a consensus.
We apply the Fibonacci sequence (0, 1, 2, 3, 5, 8, 13, 21, …) as the voting scale. This sequence reflects increasing uncertainty and effort as task complexity grows, making it ideal for agile estimation.
Reason of Choosing Fibonacci:
- Encourage discussion on tasks with large gaps in estimates
- Reflect the relative size and risk of each user story
- Provide a simple yet effective scale for general sense building
Please vote for the story point via the link. Voting Link: https://planningpokeronline.com/hEsEctBQ3fbNNypoIAH0/ Fibonacci specification as followed:
| Point | Effort Level | Description |
|---|---|---|
| 1 | Very Easy | Trivial task, no complexity, no dependencies. |
| 2 | Easy | Simple UI or logic, clear scope, low risk. |
| 3 | Moderate | Small feature, maybe 1–2 steps involved. |
| 5 | Medium | Average complexity; some UI + logic; moderate unknowns. |
| 8 | Hard | Complex feature, multiple parts; cross-team collaboration may be needed. |
| 13 | Very Hard | High uncertainty, unclear scope, many dependencies. |
| 21 | Extremely Hard | Epic-sized task. Needs to be broken down or discussed further. |
| Substitute Voting Plan: | ||
| Due to the team’s current difficulty in finding a suitable time for synchronous estimation, we have decided to conduct anonymous voting using Google Form instead of PlanningPokerOnline. |
- Each team member will cast their votes asynchronously using the form.
- Once all responses are collected, we will review the results together.
- Any User Stories with significant discrepancies in points will be discussed in our next team meeting to reach consensus. This approach ensures flexibility while maintaining collaborative estimation integrity. Voting Link: https://forms.gle/mR38nX5t6UrkPC6p6