Disclaimer

The content of this blog is my personal opinion only. Although I am an employee - currently of Imagination Technologies's MIPS group, in the past of other companies such as Intellectual Ventures, Intel, AMD, Motorola, and Gould - I reveal this only so that the reader may account for any possible bias I may have towards my employer's products. The statements I make here in no way represent my employer's position, nor am I authorized to speak on behalf of my employer. In fact, this posting may not even represent my personal opinion, since occasionally I play devil's advocate.

See http://docs.google.com/View?id=dcxddbtr_23cg5thdfj for photo credits.

Monday, October 15, 2012

Task dependencies

I know that Kent Beck says that we should not need to record task dependencies in our Agile Scheduling.

But, for my personal tasks, it would be nice to have task dependencies taken into account.

E.g. perhaps hiding or graying out tasks that cannot be done yet because of other tasks they depend on.

(In many ways, a task dependency is like a "start by" date.    As in "this task cannot be started until such and such a date.  Whereas other tasks can be dome at any time, but you just give them a "tickle date" to remind you to pay attention.  I may want to hide the former, although I think that I opreger graying.)

As in, propagating due dates: if Task B depends on Task A, and B has a due date Tb, then  A must be done by that date - and possibly earlier, e.g. if you provide a work estimate.   (Hmm, work estimates could be "number of days", "number of weekend days", etc.)


No comments: