[Fiware-security] Security Chapter - Sprint Planning - Draft minutes of today's audio

[MANUEL ESCRICHE VICENTE]

Dear Pascal,

It's important that you keep meeting minutes in a way that allows to come back to them.
Other chapters hold google docs. By doing it this way, I have a chance to contribute on directly with my comments.

Thanks.
Manuel


From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com]
Sent: viernes, 09 de enero de 2015 17:07
To: KELLER Sebastien; FELIX Edith; BETTAN Olivier; Joaquín Salvachúa Rodríguez (jsr at dit.upm.es); Álvaro Alonso; Stephan Neuhaus (stephan.neuhaus at zhaw.ch); DANGERVILLE Cyril; MANUEL ESCRICHE VICENTE
Cc: BISSON Pascal; pascal.bisson at noos.fr
Subject: Security Chapter - Sprint Planning - Draft minutes of today's audio
Importance: High

Dear Colleagues,

Find hereafter are the short minutes of the Security Chapter Sprint 4.2.1 Planning meeting of today with Manuel.

Don't hesitate to complete if you see something missing.

Best Regards,
Pascal



Participants:
Joaquin (UPM) -IDM GE and PEP Proxy GE
Sébastien (TCS) - Trustworthiness GE
Cyril (TS) - Authorization PDP GE and WPA
Edith Félix (TS) -Cybersecurity GE

Excused:
Stephan (ZHAW) - Privacy GE
Olivier - CyberSecurity GE
Alvaro (UPM) - IDM GE and PEP Proxy GE


Were assessed at this meeting:

·         Planning of Release 4.2

·         Planning of Sprint 4.2.1

This assessment was done on a per GE basis. Hereafter are the main outcomes:

IDM GE:

·         Overall in good shape both Features and Work items were planned.

·         Action items:

o   SEC-146 to be corrected since allocated to a sprint and not a release as it should be.

o   Make sure User Stories for features planned (at least for current sprint ) have been defined.



PEP Proxy GE:

·         Overall in good shape both Features and Work items were planned.

·         Action items:.

o   Make sure User Stories for features planned (at least for current sprint ) have been defined.



Cybersecurity GE:

·         Overall in good shape both Features and Work items were planned.

·         Action items:

o   Make final decision regarding EPICS - If only one EPIC confirmed aka CyberSecurity it can be removed one of the Cybersecuriy in the naming of the issues. If more EPICS to be created they have to be defined and JIRA and WIKI (Technical Roadmap ..) have to be updated accordingly

o   Make sure User Stories for features planned (at least for current sprint ) have been defined.


Authorization PDP GE:

·         Overall in good shape both Features and Work items were planned.

·         Action items:

o   SEC-146 to be corrected since allocated to a sprint and not a release as it should be.

o   3 features vs 2 stories - Check this is correct.

Privacy GE:

·         Overall in good shape both Features and Work items were planned.

·         Action items:

o   Changes to Work items the features (issues SEC 141, 139, 133, 128) that refer to documentation and/or configuration since not allowed (they were removed from the Roadmap already so just a matter to put things into correspondence.

o   See problem of mis-assignement of features in previous sprint (December).

o   Make sure User Stories for features planned (at least for current sprint ) have been defined.


Trust & Trustworthiness GE:

·         Features and Work items were planned. Issues where fix versions was not enter have been corrected.

·         Action items

o   Marked as impeded issues were information coming from project management is missing to do the work and informed accordingly WP lead for him to create an issue for coordination team (TID) to step in and answer/solve.

o   Make sure User Stories for features planned (at least for current sprint ) have been defined.



PS: Following completion of sprint planning review, Manuel may come back to us and other chapters with some further instructions (especially with respect to issues naming) . So please stay tuned


[@@ THALES GROUP INTERNAL @@]


________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-security/attachments/20150112/22bcfd12/attachment.html>