[arc-discuss] case/project inception

[James Carlson]

Cyril Plisko writes:
> What is the formal definition of case inception ?
> It seems that not every case has it, so when one is needed ?
> What deliverables are expected from project team by the
> time of inception ?
> What are possible outcomes of inception ? There are cases
> marked "inception held", are there any other possible statuses
> after inception ?

This was the first hit that google returned:

  http://www.opensolaris.org/os/community/arc/handbook/

A little later in the list:

  http://www.opensolaris.org/os/community/arc/arc-faq/arc-review-prep/

The short answers are:

  - The formal definition of an "inception" is that it's the first
    review of a full case (as opposed to a fast-track or automatic
    review).

  - Full cases need an inception.  Things that are considered
    "obvious" are supposed to go via the email-based fast-track
    process.  See:

  http://www.opensolaris.org/os/community/arc/handbook/arc-dev-process/arc-fasttrack-process/

  - What's expected at inception varies; discuss it with your case
    owner.  In general, we need enough to understand the boundaries of
    the review, but it's expected (and desirable) that many parts of
    the project specification are "TBD" or just unknown at this point.
    Inception review works best when performed _early_.

    More generally, here are the things that the ARC is normally
    interested in looking at (in inception and other reviews):

  http://www.opensolaris.org/os/community/arc/handbook/questionnaire/

  - The normal outcome of inception is that the project team gets
    feedback on their proposal, and has a list of unanswered questions
    and issues from the ARC members and other review participants.
    (Note that ARC reviews are open; anyone can ask questions.)  The
    project team then works on resolving those issues and answering
    the questions for commitment -- often with the help of the
    assigned case owner or intern.

    Sometimes, enough information is available at inception that we're
    able to complete the inception and then proceed directly to a vote
    -- as though the inception were also the commitment review.

The "normal" path for a full project is inception review, perhaps one
or more interim reviews, and then commitment (where the ARC members
vote).  Many other things can happen.  Project teams can decide to
withdraw.  Projects can get redirected (outside of the ARC) to do
something different, and end up starting over.  Inception review may
turn up the need for additional projects elsewhere in the system to
cover exposed gaps.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677