Software Engineering, Project Management, and Effectiveness
Whether I'm dealing with software requirements, or I'm prioritizing my personal TO Dos, I think in terms of MUST, SHOULD, COULD. It's simpple but effective.
Here's an example of some scenarios and usage:
It's easy to get lost among SHOULDs and COULDs. I find factoring MUSTs from the SHOULDs and COULDs helps get clarity around immediate action.
Building software involves a lot of communication. Behind this communication, lies perspectives. These
Why don't you just say that you are using the MoSCoW prioritisation system popularised by the DSDM methodology? :-)
You just forgot to mention the Wish (aka "Would like to but will not this time round")
I'm rolling my own task management database [!] so I found this post somewhat useful -- now I will separate Crucial tasks from Important, Useful, and Optional. Thanks!
How do I efficiently and effectively prioritize my day ... my week ... my life? In an earlier post, I
If you're backlogged and you want to get out, here's a quick, low tech, brute force approach. On your
Hello! Good Site! Thanks you! jdpbpxpuhhc