ISSUE: Goal of problem-statement document
Jim.Bound at hp.com
Sun Jun 8 00:19:43 CEST 2003
no expliciy agreed mission is wishy washy with no meet and we will never
figure that out but get close by documenting our bullets.
Saying PS bar is to high now that has some meat.
> -----Original Message-----
> From: Harald Tveit Alvestrand [mailto:harald at alvestrand.no]
> Sent: Friday, June 06, 2003 10:55 AM
> To: Melinda Shore
> Cc: problem-statement at alvestrand.no
> Subject: Re: ISSUE: Goal of problem-statement document
> --On fredag, juni 06, 2003 10:47:01 -0400 Melinda Shore
> <mshore at cisco.com>
> >> SUGGESTED RESOLUTION: Change this section to say that the document
> >> attempts to be a basis for consensus on the root causes.
> > One of the things that's of concern here is an interest in
> trying to
> > find ways to make progress in the absence of consensus about each
> > identified problem, the dependency analysis, and a ranking. We
> > absolutely do believe that the document will provide guidance, but
> > it's reasonable to suspect that it's likely that the only
> way we'll be
> > able to reach real consensus on some of it is if we dilute the
> > discussion to the point it isn't useful.
> I think we do have consensus on a fair number of points
> (including the "no
> explicit agreed mission", for instance) - I'd like to probe
> and try to
> refine some more of these points before declaring that this
> document is "as
> good as we can make it".
> We might quickly come to consensus about what we can't come
> to consensus on
More information about the Problem-statement