Perhaps you’ve heard the terms Priority Spectrum or Task Priority (aka Spectrum of Priorities or Prioritization of Tasks). These are essentially a way to categorize tasks based on their importance level and are very useful for website projects.
One of the more popular priority systems is the MoSCoW Prioritization Method (aka MoSCoW Method or MoSCoW Analysis), often used in Agile Methodology for software development. But you know, the MoSCoW Method always left me a little cold because I feel it tries too hard to fit the acronym and partly fails the intuitive test. MoSCoW stands for must-have, should-have, could-have, and won’t-have (or will not have right now, or wish or even would-have). BTW, you’re supposed to ignore the lower case O’s in the MoSCoW Method acronym.
What’s a guy to do when he doesn’t like their acronym? Start his own, of course! So the acronym I favor is CIBA (chee-bah), translated from Italian, it means to feed or to eat. I like that symbolism! Plus, I’m partly Italian, so CIBA it is. Bravo!
Here’s how CIBA breaks down:
- Critical (must-have, can’t live without)
- Important (should have, ought to do)
- Beneficial (good to have, helpful)
- Aspirational (would like to have someday, wishlist)
I use this list to help my clients decide what to include and what to put on the backburner. I find it extremely useful for website content and website functionalities.
The egg has hatched, feel free to give little CIBA wings and use it, if you’d like to.
Saluti…
Forté
