Hi Toni You have to distinguish between Features and User Stories. Features contain broader functionality to be implemented within 1 Minor release cycle (3.1, 3.2, 3.3,...) which is typically 3 month (3 sprints). User Stories are more specific functionalities to be implemented within 1 month (1 sprint). So the basic idea is to split up features in several User Stories and schedule them in sprints. The Features for Minor Release 3.3 (January to March) should already be defined and in the roadmap. It is important to have them asap. The User Stories/Work Items for February (3.3.2) or March (3.3.3) should be available at the begin of the related sprint (or earlier). In your case the Features should already be available (if not please add before Thursday), They have to be in the Report going to the EC. (Features have to be in the tracker and the wiki.) The User Stories (Code) & Work Items (all the rest) for the current Sprint (3.3.1) should also be in the tracker already. Would be nice if the ones for February/March (3.3.2/3.3.3) would be available in the tracker end of this week. Best regards Christof Am 27.01.2014 um 15:51 schrieb Toni Alatalo <toni at playsign.net>: > Thank you for this Christof, I edited the pages and the tracker now to match reality. > > A question: how urgent is it to define the features for the 3.3 release? We have one planned already last year to that and it was in the tracker & wiki all, the RecommendedAssetPipeline — it just didn’t show due to how the sprint was assigned I think .. now it shows in the queries. We have plans and have now began programming others too but if it’s OK we’d like to focus on shipping the current release first (on/by Wed) and then fill in more of the plans for the March release (on Thu & Fri etc). > > ~Toni > > On 27 Jan 2014, at 16:33, Christof Marti <mach at zhaw.ch> wrote: > >> Hi Torsten, Hi Toni >> >> Regarding the roadmap wiki-page, we need some more work to have separate entries for the two versions. >> >> I copied the 3D-UI feature description in the first part of the document and the 3D-UI row in the table and created an entry for the XML3D- and the WebTundra-version. >> Can you please update your parts of the document to reflect the features/descriptions and roadmap of your implementation. >> >> Thanks >> Christof >> >> Am 27.01.2014 um 15:11 schrieb Torsten Spieldenner <torsten.spieldenner at dfki.de>: >> >>> Hello, >>> >>>> And last but not least. Please verify the Features you have in the tracker with the Features you have on the „Technical Roadmap“ wiki page. >>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI >>>> Are they all available (in tracker and wiki) and are they in the correct release (3.1, 3.2 or 3.3). >>> Thanks for pointing this out, I corrected the Release in the tracker, but actually forgot to adapt the entries in the Roadmap page. The entries for 3D-UI and DaaS should now appear under the correct Release in both. >>> >>> Best regards, >>> Torsten >>> >>> >>> >>> >>>> The „Technical Roadmap“ page contains some GEi’s which have no Features planned for R3.3 (3D-UI, Display as a Service, GIS data provider, POI data provider, Augmented Reality). >>>> There is still missing the plain text short description of the features in the first part of the document for Interface Designer. >>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Roadmap_of_Advanced_Middleware_and_Web_UI#Advanced_Web_User_Interfaces_-_Application-oriented_Services >>>> >>>> Thanks for fixing the current errors and keeping the tracker up to date. >>>> >>>> Best regards >>>> Christof >>>> >>>> >>>> Am 24.01.2014 um 11:48 schrieb MANUEL ESCRICHE VICENTE <mev at tid.es>: >>>> >>>>> Please, let me a note on this sentence: >>>>> "All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned" >>>>> ->Features hold only as time frame Release >>>>> ->Stories, Bugs and WorkItems hold both Release and Sprint >>>>> ->Epics don't hold any timeframe >>>>> >>>>> -----Original Message----- >>>>> From: Christof Marti [mailto:mach at zhaw.ch] >>>>> Sent: viernes, 24 de enero de 2014 11:26 >>>>> To: FI-WARE, MiWi >>>>> Cc: MANUEL ESCRICHE VICENTE >>>>> Subject: historic open items in tracker and naming conventions >>>>> >>>>> Dear WP13 GE owners >>>>> >>>>> I was checking the tracker and still found some errors and naming inconistencies. >>>>> >>>>> There are still some historic entries, which are not closed or „Finished but not released“. >>>>> Historic means belong to Release 3.2 (which ended in December). >>>>> https://forge.fi-ware.eu/tracker/?atid=234&group_id=36&func=browse >>>>> I created a specific advanced query for these entries named "All historic open“. >>>>> >>>>> All entries which are executed in Sprint 3.3.x should also have Release 3.3 assigned. >>>>> If you are writing documentation for Release 3.2 (in Sprint 3.3.1) then this should be expressed in the description. >>>>> (e.g. with the line „Deliverable = D.13.3.3“) >>>>> >>>>> List of actual deliverables: >>>>> D.13.1.2 GE Open Specificatoin (M30) >>>>> D.13.1.3 GE Open Specification (M33 or M36) >>>>> D.13.2.3 GE SW Release (M33) >>>>> D.13.3.3 GE Installation and Administration Guide (M33) >>>>> D.13.4.3 GE User and Programmer Guide (M33) >>>>> D.13.5.3 GE Unit Testing Plan & Report (M33) >>>>> D.2.3.3 FI-WARE Architecture V3 (M33) >>>>> D.2.4.3 FI-WARE Technical Roadmap V3 (M33) >>>>> >>>>> Please also check the naming patterns: >>>>> https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Backlog_items_patterns#Patterns_in_use >>>>> Specially also add the „action“ extension at the end. >>>>> >>>>> The name (Summary) for creation of the Installation and Administration Guide for 3D-UI WebTundra GEi should be for example: >>>>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Documentation.InstAndAdminGuide.Create (description: Deliverable = D.13.3.3) >>>>> >>>>> or for update of the Architecture of the 3D-UI GE: >>>>> FIWARE.WorkItem.MiWi.3D-UI.Documentation.Architecture.Update (description:D.2.3.3) >>>>> >>>>> or for creating the SW package: >>>>> FIWARE.WorkItem.MiWi.3D-UI-WebTundra.Software.Deliver >>>>> >>>>> Watch also the difference between the GE naming „3D-UI“ and the GEi naming „3D-UI-WebTundra“ resp. "3D-UI-XML3D (only required if more then one implementation is available). >>>>> >>>>> Naming conventions for Features, UserStories etc can be found here: >>>>> http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_(convention_to_follow) >>>>> >>>>> Cheers >>>>> Christof >>>>> ---- >>>>> InIT Cloud Computing Lab - ICCLab http://cloudcomp.ch Institut of Applied Information Technology - InIT Zurich University of Applied Sciences - ZHAW School of Engineering >>>>> Phone: +41 58 934 70 63 >>>>> Skype: christof-marti >>>>> >>>>> ________________________________ >>>>> >>>>> 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-miwi mailing list >>>> Fiware-miwi at lists.fi-ware.eu >>>> https://lists.fi-ware.eu/listinfo/fiware-miwi >>> >>> _______________________________________________ >>> Fiware-miwi mailing list >>> Fiware-miwi at lists.fi-ware.eu >>> https://lists.fi-ware.eu/listinfo/fiware-miwi > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140127/57fea103/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy