Discussion Forum > DIT and Dealing with Projects that don't have a deadline ( organizational projects)
Leon:
My recommendation has always been that projects with deadlines should be dealt with as soon as received, using the "little and often" approach so that you make the most of the time available, while projects without deadlines should be dealt with one at a time - preferably by making them the Current Initiative in turn.
My recommendation has always been that projects with deadlines should be dealt with as soon as received, using the "little and often" approach so that you make the most of the time available, while projects without deadlines should be dealt with one at a time - preferably by making them the Current Initiative in turn.
November 26, 2008 at 10:17 |
Mark Forster
Mark Forster
Thank you Mark. I get a lot of benefit from being able to verbalise and work out solutions re DIT on this Forum.
November 26, 2008 at 11:09 |
Leon
Leon
I am seeking a little clarification on dealing with projects that do not have a deadline (also described here as organizational projects) within DIT. On one hand, my understanding is that a useful DIT approach is to start projects as early as possible, little and often so they do not become urgent. I find this approach useful, particularly with projects that have a specific, or assumed, deadline.
On the other hand, I also find that having too many balls to juggle dilutes my abilty to focus and slows tangible results. It can also result in an overwhelming will do list that may need auditing regularly. With this in mind, I find the one-at-a-time approach useful for projects that do not have a deadline.
Do you feel a one-at-a-time approach to projects without a deadline is compatible with DIT? Or do you recommend starting every project that you have committed pretty much straight away?