| [open-measured-data-wg] Summary of Requirements Management workshop from 8.12.2014 |
Hi all before the holidays I at least want to send you some documentation info, attached to this email (unzip the zip file and click on the html file). I will also create an issue in bugzilla to implement a documentation repository, which the will host the the src of this (and other documentation) and deploys it on the eclipse web site. Short Summary: Canoo provided a suggestion of a requirements management process. The suggestion builds on an iterative approach, because we experienced the best success in delivering software by delivering small pieces early and often. A central point in the suggestion was the establishing of a so called product manager. This product manager should be independent, best somehow paid from the working group itself. This person would report to the Steering committee, and thus represent the Steering committee and have the competence and power to make certain decisions (of course in accordance to the goals of the steering committee) to provide a fast feedback cycle. However -this suggestion led to quite a long discussion of what this role should do: A. Only collect, evaluate the requirements/requerst from the community and prepare them to bundles/packages, which can be ordered by a sponsor. versus B: doing A., but also accompanying the implementation of this packages to make sure that they are in accordance with the goals of the steering committee. (more in the attached document - TODOS: I will provide adapted pictures after the holidays, which also visualize the different approaches regarding product management responsibilities and delivery blackboxes - til january 9th) Another important question was raised - what exactly is product? What does the community expect? A mere set of building blocks which then have to be put together to a system on own efforts or a set of building blocks with an executable system which covers the basic use cases (tbd). IMO these questions should be discussed and clarified in the steering committee as this is essential. Another discussion went around the tooling. Most of the service provider know and like JIRA and since JIRA provides a free license for open source projects, JIRA is a valid option against Bugzilla (which has a lot of shortcomings), provided it is hosted in a way that the content is publicly available. Alexander Nehmer (S+C) will follow this, also with regard to the offer of being a pilot of Tuleap (early january) That said, I wish all of you a merry christmas and a happy, successful and exciting 2015 Sibylle
Attachment:
RE_Process.pptx
Description: MS-Powerpoint 2007 presentation
Attachment:
ReqLifeCycleMgmt-2014-12-08.zip
Description: Zip archive
--- Sibylle Peter Head Customer Solutions Canoo Engineering AG Kirschgartenstrasse 5 4051 Basel +41 61 228 94 41 +41 76 315 25 63 sibylle.peter@xxxxxxxxx