[Fiware-cloud] Detailed comments on the Cloud Backlog information available on the Wiki/Tracker

[David Breitgand]

Dear Juanjo, 

You require multiple changes to be made in a very short period of time.

As you might know Alex is on the leave till Thursday.

I would like to help, but I won't be able to lead this activity today and 
I cannot commit to completing it by the end of the day today.

Does anybody of the task leaders wish to step in and lead this activity?

Best.

-- david 

=======================================
David Breitgand, Ph. D.
Research Staff Member

System/Service Performance Management
IBM Research Laboratory in Haifa

Tel: 972-3-7689-465
Fax: 972-3-768-9545



From:   Juanjo Hierro <jhierro at tid.es>
To:     Alex Glikson/Haifa/IBM at IBMIL, "fiware-cloud at lists.fi-ware.eu" 
<fiware-cloud at lists.fi-ware.eu>
Cc:     "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:   14/11/2011 08:54 PM
Subject:        [Fiware-cloud] Detailed comments on the Cloud Backlog 
information available on the Wiki/Tracker
Sent by:        fiware-cloud-bounces at lists.fi-ware.eu



Dear Alex and rest of the Cloud Hosting team,

  Here it is a list of issues I have identified in a more detailed 
revision of backlog entries, both on the Wiki and the tracker, linked to 
your chapter.  You have to review them and take the necessary corrective 
measure.   Despite I have marked the most critical ones in red, all of 
them are relevant and shall be addressed.  Many of the issues are rather 
easy to address.  With the exception of those market in blue, the rest of 
them might be solved before EOB tomorrow (none of them affect the Wiki 
contents so that they won't affect generation of the .pdf book linked to 
second release of the FI-WARE Product Vision Deliverable).   Despite the 
short time I'm giving you to react, I believe this is feasible because 
they are rather few and responsibility to fix them can be properly 
distributed so that changes are implemented in parallel.   I remind you 
that sections on the Wiki should be edited in parallel (never clicking on 
the edit tab at the top of the page but clicking on the edit link at the 
right side of each section).

  I copy the rest of WPLs and WPAs so that they can monitor comments to 
the different WPs.

  Best regards,

-- Juanjo


Cloud Hosting:
General comments: 
Despite the language used for describing goals in the template defined in 
August for backlog entries has not been followed for some entries, it's 
true that Goals linked to Cloud Hosting GEs do not adapt so well to that 
formula, so we will keep things as they are.   Some people may argue that 
description of goals doesn't follow the standard Agile conventions but 
we'll see. 
You have defined FIWARE.WorkItem.Cloud.General.Architecture and 
FIWARE.WorkItem.Cloud.General.GapAnalysis as two WorkItems that you will 
carry out in order to refine the General Architecture and conduct a gap 
analysis.   Both being linked to all GEs.   That's pretty fine (and good 
practice).   However ... Do you plan to carry out these WorkItems during 
Sprint 1.1.1 ?   If so, you should assign the "FIWARE.Sprint.1.1.1" value 
to the "FI-WARE Sprint Id" field in the corresponding ticket.
Resource Manager: 
You haven't followed the defined convention for values of the "FI-WARE 
Release Id" and "FI-WARE Sprint Id" field 
You have identified a WorkItem named as 
FIWARE.WorkItem.Cloud.ResourceManager.SvcMgrIntegration.InitialDesign ... 
Are you going to carry out this item during Sprint 1.1.1 ?  The WorkItem 
may have been just identified but be still pending of planning ... that 
would be fine but wanted to double-check) 
There are some Stories that have been assigned a value of 1.1.2 to the 
Sprint Id.   However, you should not plan Stories or Work Items in Sprints 
after the current/about-to-start sprint.   This would be against Agile 
Principles.   While we will try to "plan" Features linked to releases, 
this "planning" will not apply to User Story and Work Items.   This is a 
simple change because you just need to delete value of the "FI-WARE Sprint 
Id" field for those User Stories or Work Items that won't fit in 
FI-WARE.Sprint.1.1.1 
There are several Stories that are not assigned to Sprint 1.1.1.   This is 
fine (you have identified the Stories but you have decided not to address 
them in Sprint 1.1.1).   However, I want to double-check that you didn't 
simply forget to assign a value to the FI-WARE Sprint Id field.
Service Manager: 
It has no sense to assign a User Story or a Work Item to another Sprint 
different that the current/about-to-start Sprint, as mentioned for the 
Resource Manager GE. 
There are Epics and Features listed in the User Stories section on the 
Wiki.   Just place the entries in the right section. 
I see Epics that are assigned to a Sprint (e.g., 
FIWARE.Epic.Cloud.ServiceManager.AggregateAPI.OCCIClient) ... this doesn't 
make sense (only User-Stories or WorkItems are carried out in a Sprint). 
Please fix ... 
I see Features that are assigned to a Sprint (e.g., 
FIWARE.Feature.Cloud.ServiceManager.ServiceAutoScalling.ElastRules). 
Features are just assigned to releases. 
Do you plan only to carry out the 
FIWARE.WorkItem.Cloud.General.Architecture and 
FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ?
PaaS Management: 
Work Items do not need to be declared linked to a minor release.   What is 
relevant to declare linked to releases are Features.   On the other hand 
... Shouldn't the ones being identified be linked to sprint 1.1.1 ? 
Object Storage: 
What type of entry is FIWARE.Epic.Cloud.ObjectStorage.Security.SSO. 
Apparently an Epic but has not been labeled as such on the tracker.
Wouldn't any of the identified Features be linked to the 1st minor release 
?  Couldn't you plan them ? 
Do you plan only to carry out the 
FIWARE.WorkItem.Cloud.General.Architecture and 
FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? 

Cloud Edge: 
Don't see the ticket on the tracker that should be linked to the 
FIWARE.Feature.Cloud.CloudProxy.APIFirstRelease entry. 
Do you plan only to carry out the 
FIWARE.WorkItem.Cloud.General.Architecture and 
FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? 

Monitoring: 
Do you plan only to carry out the 
FIWARE.WorkItem.Cloud.General.Architecture and 
FIWARE.WorkItem.Cloud.General.GapAnalysis Work Items during sprint 1.1.1 ? 

Wouldn't any of the identified Features be linked to the 1st minor release 
?  Couldn't you plan them ?
Self-Service Interface: 
Tickets linked to entries declared on the Wiki haven't been created !

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[attachment "ATT00001..txt" 
deleted by David Breitgand/Haifa/IBM] 
_______________________________________________
Fiware-cloud mailing list
Fiware-cloud at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware-cloud

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20111115/0d984627/attachment.html>