[Fiware-wpa] [Fiware-wpl] Plenary WPLs/WPAs confcall and next steps

[Bohnert, Thomas Michael]

Dear Maarten,

Let me add a few comments since I don't think there is need for escalation nor formal complains.

Upfront, you are right. No explicit attempt has been made to achieve consensus. The reason is simple. Before we can discuss something, especially with a complexity that reaches way beyond a single Chapter, FI-WARE, and potentially even beyond the FI-PPP, we should have a sound basis upon which we can have a profound discussion.

It was indicated in several mails  that we are working on such a proposal- one that serves the needs of the whole program. I thought to have the same over the phone when we spoke last week.

Anyways, you'll receive a presentation as soon as we have it at the next stable level. The reason why we presented a  "sneak preview" to the AB is that AB meetings are scheduled periodically and right in advance. We simply didn't manage to get draft procedures defined and a system up early enough (we settled at 2.30am at the day of the AB meeting). I trust that that there is no need to elaborate more on vacations periods and other delay factors of the like.

So let me ask for a bit more patience in order to let us finalize the approach (concepts + prototypical implementation).  The first feedback was encouraging and I am convinced that we can get your concerns addressed as well.

Perhaps to alleviate your worries for the moment. Rest assured that you are, as a task leader, not solely responsible for this task. On top of, mind that requirements collection/engineering is not necessarily the same as the collection of User Stories/Epics, etc. Task leadership is foremost a management activity. For the content and procedures, you can count on the support by other project members.

Comments welcome.

Best - Thomas



From: fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] On Behalf Of Maarten Los
Sent: Dienstag, 30. August 2011 13:32
To: Juanjo Hierro; fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Subject: Re: [Fiware-wpl] [Fiware-wpa] Plenary WPLs/WPAs confcall and next steps

Dear  Juanjo,

Regarding point b), I would like to indicate that from Atos' standpoint this topic is far from concluded. In the last months, despite repeated attempts, as far as we know, no concrete effort has been made to reach consensus with us as the leader of the requirements specification task.

For example, we have outlined on various occasions our vision on the risks, and proposed mitigating procedures to follow, when ingesting the huge amount of requirements that will be generated, as well as a supporting tool, but this has been ignored. Instead, an alternative approach is now being proposed (and apparently has already been presented to the FI-PPP Architecture Board).

We would like to object formally to these proceedings, as we think it is not compatible with the way the consortium should work, especially given the scope and impact of a project this size.

In any case, we are looking forward to hear, and make an evaluation of what is proposed in this Friday's meeting with respect to the requirements specification process.


Best regards,

 Maarten


From: fiware-wpa-bounces at lists.fi-ware.eu [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro
Sent: jueves, 25 de agosto de 2011 18:00
To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Subject: [Fiware-wpa] Plenary WPLs/WPAs confcall and next steps

Hi all,

  First thing I wanna say is that I have just come back from holidays.   I hope you have already enjoyed yours !

  Now that I came back, and the August period is almost finished, we will resume our follow-ups.

  We will start with a plenary confcall involving all WPLs/WPAs.    Then, we will resume our WP-specific follow-up confcalls but will go for trying to have them bi-weekly.

  The plenary confcall would take place on Friday September 2nd at 10:00am CET.   Please pencil this on your agendas.  Dial-in details to be provided later.    There, Thomas and me will share with you the process (and supporting tools) we will put in place for managing:

a) Communication with UC projects regarding doubts, clarifications and any other sort of Technical Support.   As an example, clarification of parts of the FI-WARE High-level Description (Product Vision) document
b) creation and lifecycle of entries in the FI-WARE backlog

  Therefore, it is crucial that you attend this confcall.   We will not only explain you the process but rather show you the tools we are configuring for this purpose.   Then you should start using them to feed the FI-WARE backlog with the entries you are supposed to be working on these days (I remind you that deadline for first list of EPICs was planned for end of August, check my previous email on the matter)

  An early presentation of both the process and the tools has been made today to the rest of members of the FI-PPP Architecture Board and has been rather welcomed.    Still we have to fine-tune a couple of things but we should have everything ready (at least regarding definition of the process) for our plenary confcall.   Then we would collect your feedback and do any additional-final fine tuning until a presentation we have committed to make to UC project by September 7-8.

  As an advanced notice, prior to official distribution of the minutes of the AB meeting that took place today, we can tell you that UC projects are mostly in the process of finishing the requirements of their end users and are now in the process of performing the necessary analysis of those requirements as to be able to produce the first requests for entries to the FI-WARE backlog by end of September on the average (one project mentioned they will try to start providing input by mid September while some would be doing early in October, but most of them mentioned "end of September").   This matches pretty well with our current planning so that we should be able to endup with a collection of FI-WARE backlog entries by the end of September (part of it being generated by us on our own, part coming from the UC projects).

  Regarding the bi-weekly follow-up confcalls, we will keep them on Mondays and Fridays because this will allow us to resume weekly confcalls whenever is needed (hopefully not that frequently).    The next three bi-weekly follow-up confcalls will be scheduled as follows:

 *   for those on Mondays: September 5th, September 26th, October 10th
 *   for those on Fridays: September 2nd, September 23th, October 7th
  Main topic for the first of these list of bi-weekly follow-up confcall will be to revise the status on collection of the EPICs related to your chapter as well as discussion on assets adopted as baseline for GEs in your chapter and issues about their integration.

  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

------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.

Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20110830/60749c49/attachment.html>