Hi, About...
Sheila Mooney wrote:
+ There is some anxiety around the uncertain release date. Some are not comfortable with a release date that is constantly slipping or not being able to rally and plan/pace around a fixed solid date. They would like to pick a fixed date and cut in order to make it.
...the only way I know of handling risks is to mitigate them with some level of process, i.e. predetermine check lists used to assess the health and progress of the project. In that particular instance (schedule uncertainty) there's no substitute to pacing ourselves through a set of identified milestones and check if we pass them or not.
I wrote such a list of fine granularity milestones and associated criteria some weeks ago: http://lists.osafoundation.org/pipermail/chandler-dev/2007-February/007658.html
I didn't receive any comment on it meaning that either everyone agreed or, more than likely, the objective of such process was unclear.
So, here we go: the objective of this process is to mitigate the risk of an uncontrollably slipping schedule: identify were we are in the schedule, how we are doing and how far we are from the final objective.
Of course, this is of little use if there's no buy in from the interested parties, so I think I'm asking the question again: comments on the proposed process?
Cheers, - Philippe _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
