"Stuff To Do" is based on a very simple concept: a prioritized list of things to do.
You can't do more than one thing at once. You can try, but if you're like me, you just end up wasting time switching between things, and don't get much at all done. Whether you're a programmer, or do anything else that requires thought and concentration, your best work is done when you're in "the zone" - free from distractions, and fully focused on the task at hand. By keeping an unobtrusive list of things to do handy, you can focus on one thing at a time, and then once it's done to your satisfaction, move on. "Stuff To Do" makes it easy to add, delete, and move tasks around, as well as generate simple reports to give you an idea of how you spent your time.
I originally created Stuff To Do for our programming team at the last place I worked, where we had a lot of things to remember for the future, in addition to keeping track of roughly how much time we spent working on different projects.
Not convinced that a simple "first things first" queue isn't the best way of dealing with the stuff you need to do? Check out what other people have to say:
Then all you need is a work queue. That's it. You want hand-wavy math? I've got it in abundance: software development modeled on queuing theory. Not too far off the mark, though; many folks in our industry have noticed that organizational models are a lot like software models.
Agile Work requires only a very small number of simple "artifacts". The most basic is the Work Queue.
Want to try it? Sign up.