# Choosing Between Projects the Scrum Way
**URL:** https://publichappinessmovement.com/t/topic/1362
**Category:** User Manual
**Tags:** useful-links
**Created:** [15 July 2019 01:42 UTC](https://publichappinessmovement.com/t/topic/1362 "2019-07-15T01:42:57Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@AndyatFocallocal](https://publichappinessmovement.com/u/AndyatFocallocal)
#### Post date: [15 July 2019 01:42 UTC](https://publichappinessmovement.com/t/topic/1362/1 "2019-07-15T01:42:57Z")
My suggestion for choosing a great idea fairly would be:
1. Take the 5 ideas which receive the most hearts and have the idea’s creator explain them to the rest of the team.
2. The team then write two scores on a piece of paper anonymously using a Fibonacci sequence scoring number.
> 1, 2, 3, 5, 8 or 13
- One score for how much impact you think it’ll have on the issue
- One score for how simple the idea is. Simple is always better when creating projects.
The reason for using Fibonacci is that the ever increasing difference between those numbers makes it easier to make a quick, accurate judgement on what you want to build.
1. Add the scores that each project receives to find the winner.
---
### Author:  [@AndyatFocallocal](https://publichappinessmovement.com/u/AndyatFocallocal)
#### Post date: [2 March 2022 15:57 UTC](https://publichappinessmovement.com/t/topic/1362/2 "2022-03-02T15:57:47Z")
@lylycarrillo I would appreciate your feedback on using this method to prioritise tasks as you are more experienced in Scum methodology than i am.
To make it more visual we would also be colour coding tasks by their priority, which is a task on the list for the [@WebDev](https://publichappinessmovement.com/groups/webdev) team.