|
Thursday, June 06, 2002
|
|
|
Schedules are lies. Schedules suck. Yes, yes, yes. But we still
need them.
The most effective scheduling rule i've used is to
schedule so as to unblock others.
The idea is to complete the portions of a feature that will unblock those
dependent on you. This way development moves along smoothly because
more lines of development can be active at a time. For example, instead
of implementing the entire database, implement the simple interface
and stub it out. People can work for a very long time this way using
that portion of the feature that caused others not to block. Plus
it's a form of rapid prototyping because you get immediate feedback
on these parts. Don't worry about the quality of implementation
because it doesn't matter yet.
10:47:17 AM
|
|
|
|
© Copyright
2002
todd hoff.
Last update:
7/13/02; 9:09:04 PM.
|
|
June 2002 |
Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
|
|
|
|
|
|
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 |
26 |
27 |
28 |
29 |
30 |
|
|
|
|
|
|
Apr Jul |
|