[Fiware-wpl] Regarding re-submission of rejected deliverables

[Juanjo Hierro]

Hi all,

  Regarding re-submission of rejected deliverables, or deliverables not submitted, following is my take:

  *   D2.1.3 - FI-WARE Requirements Backlog (not submitted, no re-submission required)
  *   D2.1.4 - FI-WARE Requirements Backlog (no re-submission required)
  *   D2.1.5 - FI-WARE Requirements Backlog (no re-submission required)

This is a sign that we have to be more serious with description of the backlog.   We insist once more: looking at the backlog of each chapter in its tracker within a given month (matching a Sprint) it would be feasible to understand what every company in that chapter is doing.   You should track all kind of activities through WorkItems as well as development activities (development of user-stories or at least refinement of Epics and Features).

Note that the next (and theorically last) release of this deliverable is end of this month !   (with an extension of 4 months to the project, it may lead to definition of an additional release of the deliverable, but we should definitively be able to address this in this release)


  *   D2.4.2 - FI-WARE Technical Roadmap (no re-submission required)

Still analyzing the comments.   However, my view on this is that the reviewers don't criticize the approach but point out several aspects in which there is actually a space of improvement:

  *   The Technical Roadmap ends referring to the backlog, so that every weakness in the backlog propagates to the roadmap.   In particular, there is a lack of detailed description for some features of several GEis (they are too high-level or vague) including non-functional features (e.g., it is stated that "mass provisioning of users" should be supported, but no target values are provided).   There are also some inconsistencies found which has been reported by the reviewers.
  *   Correlation with demands from UC projects.   This proved to be unimplementable with phase 1 projects, but should improve in phase 2 with the implementation of the JIRA projects for each of the FI-WARE GEi.     We may require UC projects to provide feedback through JIRA and, if not provided, at least we would have a justification for the lack of traceability with respect to requirements by UC projects (hopefully it won't be the case but UC projects will actually provide their feedback).
  *   Cross-chapter Epic/Features and cross-GEis Epic/Features within a chapter should be captured


  *   D2.5.2 - Third party innovation enablement in FI-WARE (not submitted, submission required after 1 month of the review report)

We all know that this deliverable was not submitted because there was no one willing to lead the task of editing it.   This is not acceptable.
I expect proposals on the matter given the fact that this project is a cooperative project.


  *   D2.6.2 - State of the Art Analysis - Emerging Technologies (no re-submission required)

We have to carefully analyze the review report comments.   It theory, there is plenty of time (next version of this deliverable is planned to be month 36, i.e., end of April 2014) but we should at least start discussion about how we will organize its development.


  *   D8.1.2 - Security Chapter GE Open Specifications (re-submission required within 1 month of the receipt of the Review Report).

I believe this re-submission is already being handled.


  *   D9.1.3 - FI-CoDE Basic Framework (no re-submission required)
  *   D9.2.2 - FI-CoDE Handbook (no re-submission required)
  *   D9.3.2 - API IDE Support (no re-submission required)
  *   D9.4.2 - Application Testing and Deployment Support (no re-submission required)

Engineering should come with a plan here.    They should provide an analysis of the comments and a concrete action plan about how to address those comments.


  *   D10.5.2 - Report on Validation Process including Validation with Use Case projects (re-submission required within 1 month of the receipt of the Review Report).

SAP already proposed an action plan so unless other feedback, we will stick to it.


  *   D11.2.2 - Exploitation Plan, including IPR Management (re-submission required by Month 30)

I have already shared with you my plan on how to address this re-submission.

  Nevertheless, we will review all this during our follow-up confcall today.

  Cheers,

-- Juanjo






________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20131014/01b871d9/attachment.html>