SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 12 | Next

David J Murphy

"Managing Software Development with Trac and Subversion"

Just marking a task as completed is part of the reviewing
process, but when doing so we can take the opportunity to see how our
progress is affecting the list. Are we behind schedule? Has the task we have
just completed brought new tasks or dependencies to mind? Always take
time to review your tasks, even if doing so is a task in itself.
By now project management practitioners will be complaining about the exclusion
of priorities and timescales for tasks, but including these is purely down to your
personal preference.
With regards to priorities, if we choose to incorporate them we need a method of
representing the priority of a given task. While assigning numerical or alphabetical
labels is common practice, it is far easier and more accessible to think of them simply
in terms of low, normal (or medium), and high. As part of task determination and
dependency management activities, it will also be apparent which tasks are of a
higher or lower priority compared to others. A simple rule of thumb would be that if
a task is of high priority then, it will most likely have a number of dependencies and
hence top our task list.
As for timescales, these will either be so fine grained (task a will take x minutes) or
broad (1 week to complete three dependent tasks) that they will just make things
complicated for us.


Pages:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25