[Fiware-wpa] Creation of Backlog Management Trackers in FusionForge

[Alex Glikson]

Well done!

Few comments regarding custom fields in Backlog tracker: 
1) I would recommend defining the Releases and Sprints as Multi-Select box 
rather than text area -- it is important to make sure that the project 
schedule is aligned across WPs. For example, the releases could be coded 
as follows: "R0.1 M9 - Jan12", "R1.0 M12 - Apr12", "R1.1 M15 - Jul12", 
"R1.2 M18 - Oct12", "R1.3 M21 - Jan13", "R2.0 M24 - Apr13", and sprints: 
"M07 - Nov11", "M08 - Dec11", etc
2) I would suggest the following set of Status choices: New, Scheduled, In 
Progress, Ready/Pending, Done. This could make the tracking & reporting a 
bit easier.
3) I am still struggling to figure out how to easily track the hierarchy 
of GEs --> Themes --> Epics --> Features. We can define queries to see 
work items of a specific GE, but this would potentially show tens if not 
hundreds of items (for larger GEs), combining themes, epics and features.. 
One possible way to handle this is to define an additional custom field, 
"Parent", of type "Relation" -- which would allow specifying the ID of the 
parent item and using it in queries. Thoughts?

Also, regarding the Backlog Wiki -- having the list of ALL the work items 
on a single Wiki page could be an issue, especially when there are many 
editors who might potentially make their changes in parallel. Wiki is 
typically not designed to handle concurrent changes, and does not have any 
locking or merging capabilities. Perhaps, it could make sense to have a 
separate page per Chapter.

Regards,
Alex




From:   Juanjo Hierro <jhierro at tid.es>
To:     "fiware-wpl at lists.fi-ware.eu" <fiware-wpl at lists.fi-ware.eu>, 
"fiware-wpa at lists.fi-ware.eu" <fiware-wpa at lists.fi-ware.eu>
Date:   03/10/2011 02:27 AM
Subject:        [Fiware-wpa] Creation of Backlog Management Trackers in 
FusionForge
Sent by:        fiware-wpa-bounces at lists.fi-ware.eu



Hi all,

  Now, everything is ready for setting up the trackers for your Chapter 
projects in FusionForge.

  I have created a comprehensive and exhaustive tutorial on how to create 
and configure trackers that is now part of the Project Handbook available 
on the Wiki:

https://wiki.fi-ware.eu

  I have also updated the name of Roles in all chapter projects so that:
previous "Admin" role remains the same
previous "Senior Developer" Role becomes "FI-WARE Chapter Project Member" 
previous "Junior Developer" Role becomes "FI-WARE Project Member" 
previous "Doc Writer" Role becomes "FI-WARE Reviewer" (this is a 
placehoder for allowing reviewers to the project to get access to 
different spaces in FusionForge) 
previous "Tech Support" Role becomes "FI-WARE Tester" (may be helpful once 
we setup the FI-WARE Testbed) 

  As per now, most of the chapters only have users that are either "Admin" 
or "FI-WARE Chapter Project Member".   I would suggest that you assign the 
"FI-WARE Chapter Project Member" just to people from partners that have 
resources in your Chapter, assigning the rest of them a "FI-WARE Project 
Member" Role.

  Pascal: I have found that you have created an "Observer" Role in your 
chapter that you seem to have assigned to other FI-WARE project members. 
For consistency reasons, I would suggest you use the new "FI-WARE Project 
Member" Role for this users (but check that the privileges are assigned as 
you wish)

  As a reminder of the "very next steps" we were carrying out regarding 
the FI-WARE Backlogs:
You should have uploaded to the Wiki the full description of 
Themes/Epics/Features/User-Stories of your Backlog (everything was set and 
ready since Thursday)
You should now configure your "Backlog Management" trackers.   There may 
exist some trackers already in your Chapter project in FusionForge.   I 
recommend to delete them all (I would also delete the forums if you are 
not using them)
Once the "Backlog Management" tracker is created and properly configured 
for your chapter (see tutorial on how to) you should start creating the 
tickets for each and every Theme/Epic/Feature/User-Story you uploaded to 
the Wiki 
Once we upload the "Product Vision" on the Wiki, you should upload 
information about the Assets selected as baseline for the implementation 
of FI-WARE GEs.   We will provide a template for this. 
  If you have any doubt, please ask.

  Best regards,

-- 
Juanjo Hierro
Chief Technologist on Software Technologies
Telefonica R&D Labs

email: jhierro at tid.es
phone: +34 91 48 32932
www.tid.es
twitter.com/JuanjoHierro

Oeste 1, Planta 5. Distrito C
Ronda de la Comunicacion s/n
Madrid 28050
Spain

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
_______________________________________________
Fiware-wpa mailing list
Fiware-wpa at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware-wpa

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20111003/58b5f3ab/attachment.html>