As the system I was testing didn’t work out the way I was hoping, I’ve changed to Fast FVP which is proving to be everything I’ve been looking for. A bit of loosening up of the rules has made it much more flexible and seems to have overcome most of the problems I have found with it before and with such systems as Simple Scanning and FVP.
Basically what I’ve done is to stick to what I said in the first paragraph of the Fast FVP article without adding the further complications in that article.
“Whenever a task is dotted which I am ready to do right now I stop scanning and do it. That’s all there is to it - it’s as simple as that, but the effect on the speed of the system is enormous.”
However that’s not going to make much sense to anyone who reads this without being already acquainted with FVP and FV. So here’s a complete set of rules. As always, I’ve written the rules for paper and pen, but it’s easy to implement them electronically if you so wish:
To sum up, except where rules 7.1 and 7.2 apply you always have a choice of:
Afternote:
Fast FVP acts like a mixture of FV, FVP and Simple Scanning. In fact you can simulate FV and FVP within the rules of Fast FVP, and you can also simulate Simple Scanning with the one change that you have to do the first task on the list on each pass. You can also switch between them at any stage.
I’m not suggesting that you should consciously think about this while doing Fast FVP. I’m just pointing out how very flexible the system is.