...

Each of the 5 phases has entry requirements that must be met before it can start and exit criteria specific goals that must be met achieved before it can complete.   The working
The phases after Conception cannot start until it's exit criteria For all phases except conception, the exit criteria of the. No phase can start until it's exit criteria has been defined. Exit criteria are the goals that the working group agree must be met during that phase in order to be successful. It is used to keep the participants focused and to provide a way to measure progress and successes. for that phase must be defined before the step can start. The purpose for this restriction is to avoid confusion, focus the effort and provide a concrete way to answer the question "are we done yet?" In the event that a process gets "stalled", the exit criteria provide a quick and easy way for someone to see what needs to be done in order to move the process along. This is the most important feature of the "incubation thing". It allows the work during the phases to happen in a free and open way but provides well known and well defined checkpoints during the process.

The tasks that happen during a specific step in the "incubation thing" may be different for each instance and should are be determined by the working group. This is in recognition that every instance is unique and we are not trying to shoe horn every "incubation thing" into the same process. That being said, when defining the exit criteria, it is important to match the goals of the phase with the intent of the phase. For example, no one should be coding features during the conception phase.

A phase is not complete until there is a satisfactory review. During the phase review, the working group must agree that the exit requirements ide for that phase have been met satisfied and that the entry requirements for the next phase have been met.

...

The working group leader will report the status of the review to Pentaho Community.

Conception

...

The conception phase is mostly about the communication of ideas: brainstorm requirements, discuss use cases, look for existing software, generate interest, etc.   By the end of the conception phase, there should be an initial set of high level requirements with enough detail for someone to generate a prototype or start on seed code.

...

No requirements beyond the Requirements for initiating a new "incubation thing".

Typical Tasks

Pathfinders

This has not been decided on yet -

These are the initial dudes that could participate in "the incubation thing."  All the phases are not fully defined which is ok.  These pathfinders will help flesh out the process.

Click the link to go to that process:

• Mondrian Schema Design (Cube Designer)Define the process - Define the unique attributes for this specific "incubation thing" process. What is the end game? Will we need new seed code or does it already exist?
• Identify stake holders - Who are the interested parties? Users, contributors, resellers etc. Recruit people for the working group. Build interest in the project.
• High level requirements - By the end of this phase, there should be enough requirements to start prototyping and costing. This usually results in a Product Requirements Document (PRD)
• Storyboards - Create storyboards and use-cases
• Architecture design - The high level framework will be needed in order to define the seeding requirements for the next phase.

Seeding

The seeding phase is where the initial coding begins. Seed code in the form of a prototype or proof of concept is typically generated by a small few and put out for people to try, comment on and modify. It is usually easier to discuss features and requirements when there is code to try out and comment on. This is where the strength of early and often come in. By the end of seeding, most or all requirements have been defined, tasks have been identified and big chunks of work can be assigned.

Entry Requirements

• Defined Seeding Requirements - The things that need to be proven or prototyped are identified
• Define Exit Criteria - What must be accomplished before this phase can be considered complete.

Typical Tasks

• Code the framework - Initial architecture framework provides straw-man for evaluating requirements. It may morph into the implementation.
• Proof of concept (POC) - Usually throw-away code to demonstrate a feature or concept. Determine the feesability of a technology or help visualize a UI.
• Prototype - Similar to a POC, usually more complete and likely that some or all of the code will be used
• Define Exit Criteria - What must be accomplished before this phase can be considered complete.

Incubation

TODO

Entry Requirements

• XXX - DDD
• Define Exit Criteria - What must be accomplished before this phase can be considered complete.

Typical Tasks

• XXX - DDD

Hatching

TODO

Entry Requirements

• XXX - DDD
• Define Exit Criteria - What must be accomplished before this phase can be considered complete.

Typical Tasks

• XXX - DDD

Product

TODO

Entry Requirements

• XXX - DDD
• Define Exit Criteria - What must be accomplished before this phase can be considered complete.

Typical Tasks

• XXX - DDD