Hi Ricardo, Inline. Br, Lorant ________________________________ From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Friday, November 04, 2011 9:40 AM To: Farkas, Lorant (NSN - HU/Budapest) Cc: Bisztray, Denes (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] EPICs and Features HI Lorant, I think that the critical difference is how is your level of decomposition of a EPIC to be tackled in a release, I mean, if the 'element' can't be included in a unique release, it is a EPIC. Yes, and even more, if the element can't be included in a sprint, already then it is an epic. This EPIC needs additional decomposition in order to be included in a release (3 months), so then you have 'Features' with a deep level of detail that allows you to be developed in a release (3 months). True. So I think the difference is not only a temporal point of view, True. So when we "relabel", we should somehow make sure no feature exceeds 3 months. R. Farkas, Lorant (NSN - HU/Budapest) wrote: Dear Ricardo, The workflow could be: 1. we make sure all epics are in order, by EOB today. I will take a look at 16:00 PM and continue tomorrow morning to make the sync with the tracker 2. we start agreeing which epics could be part of the first release. If you have feature proposals for RM, then that can be already relabelled from "EPIC" to "Feature". But it is essential that no epic/feature should be in a "placeholder" status, that is when I click on it, it should not open the edit window, but it should be in a state where each field is filled 3. we start creating user stories for the identified features I recommend to take a look at cloud hosting, they are following exactly this pattern as I see. Realistically, if I look at all tasks, we might finalize the epics today but I don't see good chances that we have features defined for all tasks by the end of the day. Thanks & Br, Lorant ________________________________ From: ext Ricardo de las Heras [mailto:rheras at tid.es] Sent: Friday, November 04, 2011 8:51 AM To: Farkas, Lorant (NSN - HU/Budapest) Cc: Bisztray, Denes (NSN - HU/Budapest); fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] EPICs and Features Thank you Lorant for your clarifications, 1 release of the IoT chapter = set of features => Yes, it's OK for me but regarding 1 epic = 1 feature, in FI-WARE. Feature is different from epic only in that the feature is planned in the next release of FI-WARE. following it, at this time we should only have to detail all as EPICs? as Features only would go the a first set of EPICs planned for going included in the first release? thanks again, Ricardo. Farkas, Lorant (NSN - HU/Budapest) wrote: Hi Ricardo, Please see my comments inline. Br, Lorant ________________________________ From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of ext Ricardo de las Heras Sent: Thursday, November 03, 2011 8:10 PM To: Bisztray, Denes (NSN - HU/Budapest) Cc: fiware-iot at lists.fi-ware.eu Subject: Re: [Fiware-iot] EPICs and Features Hi Denes, I would like to check with you the idea I have with this decomposition, for me a spring in Fiware will be = 1 month. OK. So, 1 Sprint = includes 1 or more User stories (depends on the size of the team) = 1 month (covering always a COMPLETE FUNCTIONALITY=> a complete loop of Definitio + Developement + Tests) OK. A release = 1 Feature = 3 User stories = 3 months approx. Not OK. 1 release of the IoT chapter = set of features. Approx 3 month - this is true a EPIC = Several sprints = 1 or more Features Not OK. 1 epic = 1 feature, in FI-WARE. Feature is different from epic only in that the feature is planned in the next release of FI-WARE. finally in the high level, a Theme = it should describe a generic enabler. There will be most likely one theme per GE. OK In this way, as a basic example, if you define: Feature=Directory of resources Not OK. Feature = epic, as said earlier User story 1 = To register a new resource => Sprint 1 month including (Definition + Develpment + Testing) User story 2 = To register a new Thing => Sprint 1 month including (Definition + Develpment + Testing) User story 3 = To get information about a resource => Sprint 2 month including (Definition + Develpment + Testing) User story 3 = To get information about a Thing => Sprint 2 month including (Definition + Develpment + Testing) etc. User stories are the right level, I think So pay attention I have not defined an User Story for defining a component, it is supposed to be included as part of every spring, and as long as you advance with new springs you can define new User Stories, but there is not any explicitly for the definition process. I don't know if this is right or not for you, but this is the idea I've based my T5.2 decomposition, br, Ricardo. Bisztray, Denes (NSN - HU/Budapest) wrote: Dear All, (especially Ricardo, Sabrina, Gian Piero and Thierry) A short follow-up from today's IoT weekly meeting on the EPICs and Features. 1. EPICs Currently one component within a GE is one EPIC. For example in the Devices Frontend GE: Connection Protocol Adapter - FIWARE.EPIC.IoT.DevicesFrontEnd.ConnectionProtocolAdapter Communication Protocol Abstraction Definition - FIWARE.EPIC.IoT.DevicesFrontEnd.CommunicationProtocolAbstractionDefinition This is the bare minimum. Although a Theme is a GE, a component within a GE should be described by multiple EPICs. As an example take a look at the attached xls from Ricardo <<BacklogFiware-T5.2-v0.2.xls>> and the IoT Process Automation/Exposure GE (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE#IoT_Process_Automation.2FExposure <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_%28IoT%29_Services_Enablement_in_FI-WARE#IoT_Process_Automation.2FExposure> ) in the wiki. Obviously there can be tiny components, where the single feature of that component can be described by a single EPIC, but in most cases at least 3-5 EPICs should be created per component. 2. Features As per Juanjo's email (Monday, October 24, 2011 2:30 AM) Features are those Epics you expect to address in the first minor release. When you created the EPICs, move the ones to the Features you expect to finish in the first minor release. Best, Dénes -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: <mailto:rheras at tid.es> rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telefónica I+D <http://www.tid.es> ------------------------------------- ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: <mailto:rheras at tid.es> rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telefónica I+D <http://www.tid.es> ------------------------------------- ________________________________ 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 -- ------------------------------------- Ricardo de las Heras M2M Research Project Manager E-mail: <mailto:rheras at tid.es> rheras at tid.es Phone1: (+34) 983 367625 Phone2 OCS: (+34) 91 31 29511 Telefónica I+D <http://www.tid.es> ------------------------------------- ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111104/574d5dfd/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy