IVI/Dashboard

From Tizen Wiki
< IVI
Jump to: navigation, search

Program Dashboard for Tizen IVI and Tizen Common

Official Program-Level Jira Filters

Features

3.0 IVI M14.4:
3.0 IVI M14.4 and Common Q4 ONLY:
By State:
3.0 IVI M1/2 and M14.1/2/3/4 and Common Q2/3/4:
General:
Previous Releases:

SWQRC

Feature Complete Status:
Security Feature Complete Status:
Bug Status:
SecurityScan Issues:

CCB

Bugs

IVI:
Common-Only:

Miscellaneous


Change Control Board (CCB)

Purpose of CCB

The CCB manages the commitments of the Tizen Common and Tizen IVI projects. Specifically, it manages the Plan of Record (POR) features. "POR Features" is the term used to reference the set of features which are committed to be delivered per current project plans. The following types of feature changes are managed by the Tizen CCB process:

  • Committing any feature (Changing the status from Scoping to Approved)
  • De-committing any feature (Changing the status from Approved to Scoping or Rejected)
  • Pushing out when a committed feature will be released (Changing the Fix Version/s field of an already Committed feature to a later release.)
  • Note: Committed means the Status is Approved, Resolved, or Closed.
  • Changing the Priority field of a committed feature
  • Changing the Profile/s field of a committed feature
  • Changing the scope of a committed feature
  • Changing a feature in such a way that it causes substantial changes to the already planned work to implement and deliver the feature. This does not include changes that simply clarify the feature.

Optional, If Conditions Are Met
The following type of feature change does not have to be managed by the CCB, but if the Feature PM wants to propose the change to the CCB there is nothing wrong with doing so. It’s just not required.

  • Pulling in when a committed feature will be released (Changing the Fix Version/s field of an already Committed feature to an earlier release)
Note: This kind of change does NOT have to be managed by the CCB process assuming ALL of the following items are verified by the Feature PM who is delivering the feature earlier than planned:
  • QA is able to support the earlier testing of the feature
  • Tech Marketing is able to get any customer collateral created/updated in time for the earlier release
  • All dependencies (e.g. other related Tizen features, any work being done by other teams, etc.) are properly identified and these dependencies are “in sync” and the owners of these dependency items are also able to support the earlier release
If any of the above items are not completed or are not true, then the committed feature shall NOT be pulled in to an earlier release.

Out of Scope of CCB
All other changes to a feature are not managed by the CCB.

Tizen CCB Members
Bingwei Liu, Cathy Shen, Dominique Le Foll, Geoffroy VanCutsem, Mahesh Bhan, Mark Linkmeyer, Matti-Pekka Sivosuo, Mikko Ylinen

Tizen CCB Decision Making Process
The decision making process followed shall be: Consensus of the Tizen CCB Team (if consensus cannot be reached, Mahesh is the decision-maker)

How to Submit a Change Request to the Tizen CCB
For requesting new features be added to POR, do the following:

  • Create the new feature in Jira (by default it will be in the Scoping state. Leave it in that state.)
  • Add a Comment to the feature that includes as much of the following information that you know: (At a minimum, provide Reason for Change and Impact If Not Approved)
  • Reason for Change: [Describe the reason for the change, the benefit, etc.]
  • Impact If Not Approved: [Describe the impact of not approving the change]
  • Impact to Current Plans: [Describe the impact this change will have on already planned efforts. In other words, what’s it going to take to implement the change? Include architecture, design, implementation, testing, and performance impacts. Include any dependency impacts. Include which software components are affected.]
  • Add the "CCB" label to the feature
  • Send an email to all of the Tizen CCB Members (listed above) to notify them of your requested POR change. Include in the email the information you added into the Comment.

For requesting a change to or removal of a current POR feature, do the following:

  • Add a Comment to the feature that includes as much of the following information that you know: (At a minimum, provide Change Description, Reason for Change, and Impact If Not Approved)
  • Change Description: [Describe the change being requested]
  • Reason for Change: [Describe the reason for the change, the benefit, etc.]
  • Impact If Not Approved: [Describe the impact of not approving the change]
  • Impact to Current Plans: [Describe the impact this change will have on already planned efforts. In other words, what’s it going to take to implement the change? Include architecture, design, implementation, testing, and performance impacts. Include any dependency impacts. Include which software components are affected.]
  • Add the "CCB" label to the feature
  • Send an email to all of the Tizen CCB Members (listed above) to notify them of your requested POR change. Include in the email the information you added into the Comment.