Skip to content

Instantly share code, notes, and snippets.

@anodynos
Last active October 10, 2018 20:47
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save anodynos/7ccc84273c3ca1821b37 to your computer and use it in GitHub Desktop.
Save anodynos/7ccc84273c3ca1821b37 to your computer and use it in GitHub Desktop.
@todo: "Urgency Easiness Gracefulness"

@todos: the Urgency Easiness Gracefulness scheme

In my @todo's, I (intend to) use the following scheme:

@todo (Urgency Easiness Gracefulness)

For example: @todo (3 5 7)

The larger each number, the more of Urgency, Easiness and Gracefulness this @todo has!

Why ?

This scheme, has a thorough benefit: You pick the @todo with larger numbers, from left to right!.

Think about it! Who wouldn't like to tackle a @todo (9 9 9), right now! ?

Sometimes, you can adjust and pick larger second number (an easier one), even if there are more urgent things. Because perhaps you're bored and its too early in the morning and you need to warm up... Or perhaps its a kinda og a Graceful todo!

Actually, their product is also a very interesting indicator to follow...

So, Pick your 3 numba's, and start todo-ing :-)

You just remember UEG, and you're way there!

In detail, U E G means:

Urgency

Current/temporal importance:

  • Does this need to be done now?

  • Is it preventing us from having reliable execution in the following term ?

  • Is it a burden to other things ?

The higher, the more urgent. eg:

  '1': 'It can wait and wait. Its probably just cosmetic. '

  '5': 'This should be fixed, cause its kinda ugly...'

  '9': 'This must be fixed now! It breaks everything else.
        We can't even continue working until this is solved... 
        Should not even exist in a 0.1prepreviewalpha!'

Easiness

Not all problems are solved as easy. Some some are 5 days, some are 5 minutes. Some can be solved by anybody, some require skills, deep thought and time.

Note: You shouldn't really use metrics as days, minutes, or moan-months literally. Its about easiness, not estimated time to spend. Adjust to your scale thoughtfully.

The larger the number, the more easy is it to implement: eg:

  '1': 'This is very hard - it seems like it can not be done with the current knowledge/team/formation.'

  '5': 'In needs some thought & design, but it can start pretty easily...'

  '9': 'Its a fiver, a no brainer. \
        Any intelligent monkey can do it... \
        Go on, kill it!'

Gracefulness

Its the future importance, the Ultimate Grace!

Not all solutions, to all problems are worth the same. Some are just rudimentary work you just need, some take you higher.

The larger the number, the more Grace you 'll (sometime in the future) get. eg:

'1': 'Its a trivial necessity - everybody has it.'

'5': 'Its kinda nice, elegant, it works ok. But nothing the world ain't seen before...'

'9': 'The mother of all inventions.
    You `re either gonna be Bill Gates or Linus Torvalds...

Numbers should be 0..9, but improvise, When you have to!

AnoDyNoS

@anodynos
Copy link
Author

Obviously one could use SCRUM Fibonacci numbers 1, 2, 3, 5, 8, 13 :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment