TechCouncilReviewFramework

Technical Council Review Framework

This page describes a framework (process) used to conduct reviews at the NetBeans Tech Council.

What is reviewed

For each release, the Technical Council reviews the major features planned by each team. The reviews are conducted on the per-team (per-area) basis, and the main features ("release themes") are reviewed more thorougly. There are two kinds of reviews:

  • Full reviews (involving a meeting or several meetings)
  • Fast track (e-mail only)

Here are the descriptions of the two kinds of reviews

Full review - appropriate for major features (release themes)

  1. Project team prepares the specification that follows the format specified by the template
  2. Project team sends the specification to nb-tech-councilATsun.com, in advance of the review meeting
  3. The review meeting is called, with the participation of the project team
  4. Possible follow-up e-mail discussion and/or additional meetings are conducted
  5. When decision/recommendation is made, it is published on the summaries page

Fast track review - appropriate for other release features

  1. Project team prepares the specification that follows the format specified by the template
  2. Project team sends the specification to nb-tech-councilATsun.com
  3. E-mail discussion of the specification is conducted, with the participation of the project team
  4. When decision/recommendation is made, it is published on the summaries page

Focus of the review

The following aspects of the release features are considered, for each review.

  • Are we focusing on the right features (or aspects/subfeatures of a feature), relative to other features we could be doing?
  • Are there any additional features/subfeatures that should be considered in the plan?
  • At the high level, is the implementation approach (including UI) suitable?
  • Are there any assumptions (stated or hidden) on work done by other teams? What is the interaction with other IDE features? Are all the parts of the effort in the respective teams' plans?
  • Does the plan match what users are telling us we should do?

Important notes

  • The reviews by the TC are not blocking, i.e. the implementation of features does not need to wait for the TC to issue a decision/recommendation.
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo