I wouldn't mind a 'done', 'ToDo' and 'todo if possible' list with an estimate attached to the bottom.
I think that would be a really good idea. Ofcourse things that are "done" should just be released already.Ofcourse BRL might use a timeboxed process (like SCRUM or XP) where a Gantt chart (or similar time based reference) doesn't make much sense, but in that case, a backlog of what "needs to be done" might still be useful.
I'm guessing these lists already exist in some form already.
Without a doubt, although they may not be meaningful in their current form to anyone outside of BRL.Although I'm still not entirely clear on why people need to know, and in which ways such knowledge would benefit the advancement of their respective projects.
wouldn't it be best if Mark wrote a very small worklog, let us say - twice a month?!?
I think that's clearly a matter of preference. I prefer more in-depth worklogs, less often, even if they are mostly interesting from an academic, rather than a productive point of view.Progress should be measured in working software.