Hi All, as agreed in the call yesterday, here I forward you some remarks derived from a mail exchange with Thomas, about Sprints, Releases etc. Please have a look and provide further comments and/or clarifications if necessary. General remarks: * First of all: please read again the page on methodology at https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology to gather more confidence with it and maybe discover further interesting details. * A sprint lasts for one month, a release lasts between two and four sprints (i.e. two to four months). * The correct release/sprint numbering can be found at link https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering If an EPIC/feature/user story/work item is 'under execution' (that means you are working on it), the following applies: * A user story is expected to be worked out in one sprint, so we should be able to assign easily the sprint ID (and consequently also the release ID). Typically a sprint ID is assigned at the beginning of the sprint (not earlier) in which we assume we'll complete that user story. * A Feature should be worked out in the period of a release, so release ID should be clear. We can leave the sprint ID open for features (in the case that the feature is further structured into user stories, the different user stories should be linked to sprints, and this should be sufficient). * For EPICs or work items, we should set the release ID, in which we expect that the EPIC is fully worked out. sprint ID should be left open. * If you see that related work is not finished within the originally assigned sprint/release, then increment the sprint ID or the release ID (this should be decided at the periodic meetings among the development team, at end of a sprint/beginning of next one - ) Ifan EPIC/feature/user story/work item is 'open' (that means that it is already defined, but currently nobody is working on it), the following applies: * If we already know when the EPIC/feature/user story/work item is intended to be worked out, we can set the release ID to the expected value for completion (to give an estimation when it might be available). If no distinct timeframe is envisaged yet in your time plan, the release ID should be left open. * The sprint ID should be left open in any case. In any case it would be good for the visibility of our activities in the task if we all spent some (small) time per month to update the sprint and release IDs (e.g. setting it to the next value if time is exceeded and work is still going on) or update the work status (if item is completed), because tracker activites are monitored by the project lead and used for reporting. Furthermore, the backlog tracker is also a reporting tool inside our WP, so we can see more easily what's going on. Please also don't forget to define new Features (and also user stories where appropriate) when proceeding in your work, and to define them both in the backlog tracker and in the 'materializing' WIKI pages. Thanks to Thomas for putting all in a more structured manner :) BR Pier Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [cid:00000000000000000000000000000003 at TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120706/78a11b8c/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120706/78a11b8c/attachment.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy