http://en.wikipedia.org/wiki/Getting_Things_Done http://en.wikipedia.org/wiki/Getting_Things_Done calls these "next actions", things you can just do instead of

http://en.wikipedia.org/wiki/Getting_Things_Done http://en.wikipedia.org/wiki/Getting_Things_Done calls these "next actions", things you can just do instead of having to decide (probably at the last moment) where to start on them. You may like more of Allen's ideas if you weren't already familiar. Thinly slicing a software project is also the only way I can produce a schedule that is remotely plausible, since easy task (half day) + easy task (half day) != easy project (half day).