We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
How to handle FI-WARE Theme/Epic/Feature requests issued by UC projects - FIWARE Forge Wiki

How to handle FI-WARE Theme/Epic/Feature requests issued by UC projects

From FIWARE Forge Wiki

Jump to: navigation, search
FIWARE WIKI editorial remark:
This process is not applicable any more as the testing of the Use Cases has ended

Requests for the addition of new Epics/Features in the FI-WARE Backlog are issued by UC projects by means of creating tickets in the FI-WARE Epic/Feature requests tracker in FusionForge. More information about how these tickets are opened can be found in the tutorial followed by UC projects on How to request for the addition of new Themes/Epics/Features in the FI-WARE Backlog. Once they are opened, tickets transition through several states until they are definitively closed. Following is the description of the workflow associated to each tickets which does not only show the several states through which a ticket may transition but also the valid transitions between states.

[[

Image:FI-WARE_Theme_Epic_Feature_requests_tracker_workflow.jpg|1500px]]


The following table summarizes the meaning of each state. It also indicates whom should be assigned the ticket at each state.

Estado
Meaning
Who sould take care of the ticket once the state is reached

Open

The ticket has been created in the tracker and is pending of evaluation by the FI-WARE team

Admin users

Under Evaluation by FI-WARE

The ticket is under evaluation by members of the FI-WARE project. Typically, it will be first assigned to the proper FI-WARE Chapter Lead who, in turn, may assign the ticket to a member of his/her team.

FI-WARE Chapter Lead or FI-WARE project Member

Needs Revision by Issuer

The FI-WARE team has determined that some fields of the ticket have to be revised by the issuer or the issuer has to provide a reply to comments or questions made by the FI-WARE team (attached to the ticket)

FI-WARE User (Issuer of the ticket)

Revised

The issuer of the ticket has fixed the ticket or replied to last comments or questions formulated by the FI-WARE team attached to the ticket

Admin Users, FI-WARE Chapter Lead or FI-WARE Project Member

Out of the Scope of FI-WARE

After evaluation, the FI-WARE team considers that the requested functionality is definitively out of the scope of FI-WARE

Admin users

Already Covered by Baseline Asset

After evaluation, the FI-WARE team considers that the requested functionality was already covered by a baseline asset. They have to work in creating one or several FI-WARE Backlog Feature entries that document that the functionality is actually covered.

FI-WARE Chapter Lead or FI-WARE Project Member

Accepted for Inclusion in FI-WARE Backlog

After evaluation, the FI-WARE team considers that the requested functionality was not planned initially, but they agree to incorporate it by means of adding one or several FI-WARE Backlog entries (Epics and/or Features).

FI-WARE Chapter Lead or FI-WARE Project Member

Covered by FI-WARE Backlog Entries

There are two scenarios in which this state can be reached. On one hand, the FI-WARE may determine that the requested functionality is already covered by a number of already existing FI-WARE Backlog Entries. Alternatively, you reach this state once the team had accepted the inclusion of the requested new functionality in the FI-WARE Backlog and has already created the suitable FI-WARE Backlog entries (Epics and/or Features)

Admin users

Closed

The ticket is closed because it doesn’t require further management

Nobody


The following table shows who may transition from one given state to another.


From \ To

Open

Closed

Under Evaluation

Needs Revision by Issuer

Revised

Out of the Scope of FI-WARE

Already Covered by Baseline Asset

Accepted for Inclusion in FI-WARE Backlog

Covered by FI-WARE Backlog Entries

Open

X
Admin
Admin,
FI-WARE Chapter Lead
Admin, FI-WARE Chapter Lead
-
Admin
-
-
-

Closed

-
X
-
-
-
-
-
-
-

Under Evaluation

-
-
X
Admin, FI-WARE Chapter Lead, FI-WARE Project Member
-
Admin, FI-WARE Chapter Lead
Admin, FI-WARE Chapter Lead, FI-WARE Project Member
Admin, FI-WARE Chapter Lead, FI-WARE Project Member
Admin, FI-WARE Chapter Lead, FI-WARE Project Member

Needs Revision by Issuer

-
-
-
X
Admin, FI-WARE User
-
-
-
-

Revised

-
-
Admin,
FI-WARE Chapter Lead
Admin,
FI-WARE Chapter Lead
X
-
-
-
-

Out of the Scope of FI-WARE

-
Admin
-
-
-
X
-
-
-

Already Covered by Baseline Asset

-
-
-
-
-
-
X
-
Admin, FI-WARE Chapter Lead, FI-WARE Project Member

Accepted for Inclusion in FI-WARE Backlog

-
-
-
-
-
-
-
X
Admin, FI-WARE Chapter Lead, FI-WARE Project Member

Covered by FI-WARE Backlog Entries

-
Admin
-
-
-
-
-
-
X


IMPORTANT NOTES:

  • Some of the functionality that will be supported in FI-WARE for a given Generic Enabler (GE) has not been initially captured in the FI-WARE Backlog because it is already supported by some of the products adopted as baseline asset for the reference implementation of the GE (see Creating the first version of the FI-WARE backlogs). In these cases, the FI-WARE team will change the state to "Already Covered by Baseline Asset". Then, afterwards, they will create a number of FI-WARE Features in the Backlog describing the supported functionality. FI-WARE Features created this way will be labeled as belonging to FIWARE.Release.0.0. Thanks to this, UC projects will be able to map all the functionality they seek for in the product into Features in the FI-WARE Backlog.
  • It is highly recommended that transitions from one state to another are accompanied by information that may help the assignee to understand what is expected from him/her. As an example, a FI-WARE project member or FI-WARE Chapter Lead should formulate concrete questions that a FI-WARE User has to reply when a ticket is transitioned to the "Needs Revision by Issuer" state. You can add comments/questions and even attach files to any ticket by using the "Followups" tab.
  • It is highly recommended that you assign the ticket to the issuer whenever you pass it to the "Needs Revision by Issuer" state.


You may also follow-up evolution of a ticket by clicking on the “monitor” button of the page where info about the ticket is displayed.


Personal tools
Create a book