Hmm... going over the issues file now, I kind of wish we had covered a
few issues during commitment. Specifically, jdc-5 indicates that
resolution would done in commitment review. Likewise kb-02 wasn't fully
addressed.
How best to handle the fact that the project was voted on, but these
issues weren't covered at commitment?
-- Garrett
Mark A. Carlson wrote:
> Garret,
>
> If, in your opinion, you find any inception issues
> (even if they were resolved) that other projects
> can learn from, please include the issue and it's
> resolution in the opinion.
>
> Thanks,
>
> -- mark
>
> Garrett D'Amore wrote:
>> Gary Winiger wrote:
>>>> 4. Opinion
>>>>
>>>> No issues were raised for the project team at commitment
>>>> review.
>>>>
>>>
>>> There seemed to be issues discussed at the inception review.
>>> Were none of them worthy enough to note in the opinion?
>>> Gary..
>>>
>>
>> There were issues at inception, indeed. They had all been resolved
>> before commitment though. I am uncertain what the procedure is for
>> noting issues that are resolved before a project comes for commitment
>> -- certainly there was no advice or discussion at commitment.
>>
>> Put another way, I _thought_ that the opinion does not stand alone,
>> but exists in conjunction with the case materials. Those case
>> materials (the commitment versions) had, I presume, been found
>> acceptable without need or desire for change. So I called out a
>> reference to them, and didn't mention it further.
>>
>> Admittedly, I'm still new to the process here, but if there is
>> something else that folks would like this opinion to reflect, I'm
>> happy to change it. In such a case, though, I'd like to have a
>> little more guidance as to what should or should not be recorded in
>> the opinion.
>>
>> -- Garrett
