Hi Jarkko The definition of the terms is here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology A Feature is functionality implemented within 1 release (max 3 month). A user story is functionality implemented within 1 sprint (1 month). typically part of a feature. If a feature is implemented within 1 sprint you can also schedule it for a specific sprint. Work items are all jobs you do not involving programming and are usually scheduled for a specific sprint 3.3.1, 3.3.2, 3.3.3: - writing documentation, architecture - editing catalog, ... - preparing tutorials - etc. (see my link in yesterdays minutes about the names schema for work items. With work items you document and justify all the other work. See also specific answers to your questions inline. Christof Am 23.01.2014 um 08:36 schrieb Jarkko Vatjus-Anttila <jarkko at cyberlightning.com>: > Hello all, > > I am still a little bit confused with the terminology here, especially with "work item" and "user story", so maybe a few clarifying (perhaps stupid :)) questions are needed: > > - Now that we are a number of features for each GE, do we need to create user story for each GE, or for each feature? You can add user stories to document the work done within one sprint on a feature. > - What exactly is "user story"? Is it kind of a use-case description, i.e. it describes steps how the GE are used, or is it more a general overview what is happening in the GE. In principle it is a specific concrete implementation of a part of a feature. ( > - We need to add work items for documentation, updating sw arch, etc. Do we simply add those for each GE individually? Yes. the naming schema contains the specific GE. See the link to the naming schema in yesterdays minutes > - Does there need to be a link between work items and features? work on features and work items is completely different type of work (coding versus „all the other stuff“) So no link is needed. > - Do we need to assign features also to sprints, since at the moment they are not. If a feature is implemented within 1 sprint you can also schedule it for a sprint. > - Do we need to link user stories and work items somehow? or are they individual entries? See above as for features. Different type of work. No link. > > Thanks a lot! > > > On Wed, Jan 22, 2014 at 2:40 PM, Christof Marti <mach at zhaw.ch> wrote: > Yes. Thanks for pointing this out. > The link for the architecture dashboard is: https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=20 > (its the same document, but different tab). > > Christof > > Am 22.01.2014 um 13:37 schrieb Jarkko Vatjus-Anttila <jarkko at cyberlightning.com>: > >> Christof, >> >> This link: >> >> >> Fri 24.01.2014 [GE owner]: updated and reviewed architecture for your GE in private wiki (mark "updated" in dashboard) >> https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=21 >> Points to M36 page, surely you meant M33 arch update page? >> >> >> - j >> >> >> >> On Wed, Jan 22, 2014 at 1:29 PM, Marti Christof (mach) <mach at zhaw.ch> wrote: >> Hi >> >> Following a short summary of all the action points open from this weeks meeting. >> For details please check the minutes on https://docs.google.com/document/d/1156-Sl1KrlIjNXWzfh9vcc2KsrPK8vhmf9tg9A2IXz8/edit# >> >> Thu 23.01.2014 EOB [GEi owner]: fix orange/red marked Install&Admin-, User&Developer-Guides & unit-testing plans. >> https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=17 >> Thu 23.01.2014 EOB [GEi owner]: fix historic entries in tracker (close or ri 24.01.2014 EOB [GEi owner]: add sprint entries for last, current (3.3.1) and next sprint (split release in user stories and add work items for non code work) >> Fri 24.01.2014 [GE owner]: updated and reviewed architecture for your GE in private wiki (mark "updated" in dashboard) >> https://docs.google.com/spreadsheet/ccc?key=0Auieh_fs3EUxdFVvY19ab1lFRDRUaTBrUXlpYzBVRlE#gid=21 >> Sun 26.01.2014 [GE owner]: Integration Plan for your GEi (GEi dependency chain & Testcase for each chain) >> please use attached template. >> Wed 29.01.2014 [GEi owner]: deliver binary package/zip to FI-WARE files section (mandatory) >> >> Please keep the deadlines and let me know if you have problems/questions for any topic. >> >> Best regards >> Christof >> ---- >> InIT Clou 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 >> >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> >> >> >> >> -- >> Jarkko Vatjus-Anttila >> VP, Technology >> Cyberlightning Ltd. >> >> mobile. +358 405245142 >> email. jarkko at cyberlightning.com >> >> Go to www.cybersli.de and enrich your presentations! >> >> www.cyberlightning.com > > > > > -- > Jarkko Vatjus-Anttila > VP, Technology > Cyberlightning Ltd. > > mobile. +358 405245142 > email. jarkko at cyberlightning.com > > Go to www.cybersli.de and enrich your presentations! > > www.cyberlightning.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140123/f1eb22ea/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy