[Fiware-wpa] FI-WARE Backlog Management

[Maarten Los]

Dear all,

In the telco of 28/7 about the coordination of FIWARE Backlog related
activities, as leaders of Task 2.1, we proposed a procedure and a
supporting tool (to be set up, hosted and supported by Atos) for the
requirements gathering process, as an entry point for the backlog
entries to be passed into AgileFant.

The idea behind our proposed tool and procedure is that requirement
contributors can directly provide their input into the system, requiring
it to be assigned to a relevant WP representative (no 'dangling',
un-owned requirements allowed). It allows for a decentralized way of
handling the requirements and for a one-to-one dialog between those
providing the requirements and the technical leaders responsible for
fulfilling them. In our opinion, there is a risk involved when one
single point of contact (whether that's Atos or anyone else), is
responsible for evaluating, assigning, discussing and coordinating all
the requirements between all contributors and all WP representatives.
The amount of requirements that will be generated will be of a too
significant amount to be realistically dealt with that way.

The proposed tool supports topics (for a division between WPs),
visibility/access levels for different staff, transfer of tickets, both
private and public discussion threads for the tickets (to facilitate
mentioned one-to-one dialogs), access without required registration, as
well as the usual features such as email notifications, attachments,
etc.

Meanwhile, it is becoming apparent that the proposal is being
disregarded in favor of Forge Tracker and a different process (more
centralized). Let's be clear upfront that we have no problem with any
tool that does the job right.

However, we would like to emphasize that Atos will not assume the role
of a central requirement handler. 

Atos will contribute to this task by providing end user and technical
requirements and is still open to contribute with any further
coordination activities required by the WP leader, as far as they
reasonably fit within our assigned efforts.


Best regards,

 Maarten



-----Original Message-----
From: fiware-wpa-bounces at lists.fi-ware.eu
[mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Bohnert,
Thomas Michael
Sent: martes, 16 de agosto de 2011 10:45
To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Subject: [Fiware-wpa] FI-WARE Backlog Management

Dear all,

We are getting closer to a final concept for maintaining the FI-WARE
backlog.

As you may recall, the system we will use to manage requests and actual
backlog entries is a combination of the FORGE tracker, AgileFant, and a
media wiki.

Based on my own experience AgileFant in particular requires some effort
to get acquainted with. 

Since the FI-WARE internal backlog will be managed by
WP-Leads/-Architect I enclose the demo presentation provided by the
AgileFant providers. Please make yourself familiar with it. In the near
future we'll go through an some examples on how to use AgileFant within
FI-WARE and familiarity with AgileFant terminology and concepts will be
a prerequisite.

I'll also put additional documentation on FORGE, under "WP2 - Global
Technical Activities".

In case of questions drop me mail.

Best - Thomas

  
------------------------------------------------------------------
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. 
------------------------------------------------------------------