Hi Philipp,
Thanks fro taking the time to look into this. Inline
El 20/05/2015 a las 13:54, Philipp Slusallek escribió:
> Hi,
>
> Given that May 15th is already gone and the timeline for actual delivery
> is already planned, I guess we should move the chapter arch deliverables
> to beginning or mid of June. Saying now that we would like to move it to
> a date in the past looks strange.
M9 (May/15) is the end of May. Not in the past, it is reasonably aligned
as we intend to deliver asap.
>
> I understand the reasoning for removing the global Arch/Roadmap/and
> Backlog. However, I believe it is a pitty.
I do belive it's a pity as well. But I am trying to be realistic. I am
trying to handle things as they are, not as they should be.
> We are actually too much
> working in silos of each chapter and we are missing cross-chapter
> activities. If we keep things within each chapter there is even less
> incentive to do any cross-chapter activities. Maybe we should replace
> them with some other activity in that direction. The demos come to mind,
> but then they would need to be designed in the right way and would need
> committments form each of the chapters.
Exactly. Demos seem a good context for this.
>
> We should make sure that we have the "deliverable from the web"
> functionality working for the SW/admin/install/user deliverables in
> September. This would greatly help all of us by only having to update
> the Wiki.
I agree and had my 3rd internal meeting dedicated to this with Bitergia
last Monday. It is not blabla, they show me prototypes and they are
getting there. I intend to have it for the end of May. It is critical
for us, this contingency method we have not is a nightmare for all.
>
> I have difficulties understanding the difference between the backlog and
> the roadmap deliverable. Aren't they both about what we are planning to
> do. When we have them both at yearly points couldn't we merge them?
Manuel may be able to provide a better answer as I tend not to mess with
the backlog. Roadmap is course grain (up the level of Features) and
reflected in the wiki. Backlog is finer grain (user stories and workitems).
In my view, the focus of the roadmap is timing, the focus of the backlog
is functionality (but this is arguable)
The Roadmap did not have too much of details. Alex insisted in adding
the feature descriptions etc. on the grounds of providing a more
comprehensive deliverable (I did not object, no one else did at the time
as it makes some sort of sense). But this, as I pointed out, blurs the
boundaries between both deliverables.
>
>
> Best,
>
> Philipp
>
> Am 20.05.2015 um 10:45 schrieb MIGUEL CARRILLO PACHECO:
>> Dear all,
>>
>> As discussed in previous coordination calls, we need to propose a
>> simplification of the deliverables in the current project. This is what
>> I intend to send to Arian:
>>
>> * https://docs.google.com/spreadsheets/d/1vEFqA7ZumHjgT1bcDl7nST_ZI7YfXILGTbjkIb-tgFU/edit#gid=1371822969
>>
>>
>> Note that:
>>
>> * The description of the proposal for change is in column C
>> * The deliverable timeline on the right is the initial one in the
>> current DoW that we put here for reference and to make this self
>> contained (if you detect any mistakes, please let me know!)
>> * Joel will provide feedback on 32.2 by the end of today (deadline:
>> 5pm) and this deliverable may change. This is reasonably isolated
>> and should not interfere with your review of the rest of the
>> deliverables.
>> * If you can think of reasonable simplifications in the scope of the
>> deliverables, this could also be added. It is not only delivery
>> dates and the number of deliverables, we can also lighten what we
>> are expected to provide in each deliverable.
>>
>> _*Deadline for comments(if any): Tomorrow EOB*_. I'll send this to Arian
>> early on Friday
>>
>> Regards,
>>
>> Miguel
>>
>> --
>>
>> Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com
>>
>> ----------------------------------------------------------------------
>> _/ _/_/ Miguel Carrillo Pacheco
>> _/ _/ _/ _/ Telefónica Distrito Telefónica
>> _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 6
>> _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
>> _/ _/_/ 28050 Madrid (Spain)
>> Tel: (+34) 91 483 26 77
>>
>> e-mail: miguel.carrillopacheco at telefonica.com
>>
>> Follow FIWARE on the net
>>
>> Website: http://www.fiware.org
>> Facebook: https://www.facebook.com/eu.fiware
>> Twitter: http://twitter.com/Fiware
>> LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
>> ----------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------
>>
>> 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
>>
>>
>> _______________________________________________
>> Fiware-chapter-architects mailing list
>> Fiware-chapter-architects at lists.fi-ware.org
>> https://lists.fi-ware.org/listinfo/fiware-chapter-architects
>>
--
Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito Telefónica
_/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 6
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
_/ _/_/ 28050 Madrid (Spain)
Tel: (+34) 91 483 26 77
e-mail: miguel.carrillopacheco at telefonica.com
Follow FIWARE on the net
Website: http://www.fiware.org
Facebook: https://www.facebook.com/eu.fiware
Twitter: http://twitter.com/Fiware
LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------
________________________________
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
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy