[Fiware-wpa] Meeting in Rome

[Leidig, Torsten]

Hi Junajo and others,

Unfortunately I cannot attend the meeting due to other critical business. Thorsten Sandfuchs will replace me in Rome. However, he has to leave on Wednesday.
So it would be great if you can arrange the agenda in a way that all topics requiring SAP are handled until Wednesday afternoon.

We spend some thoughts on things, which might be important to discuss during the meeting. Our hope is that we can come up with an agenda before the meeting.
Here are some topics, which might be relevant from our perspective:
We should identify an owner & driver for every session.

-       Preplanning of next Review (June 2013) (1h+2h)
o       What will be the major messages (technical & organizational) for the next review?
o       Preparation: every work package collects and presents ONE sentence what to position on the next review (June 2013)
o       Further discussion on Demo scenario - what is missing and should be presentable in the next review?
o       Which GEs will have new functionalities, which ones will be presented in the next demo-run?

-       Architecture (series of break-out sessions with small groups and on Wednesday one session with everybody)
o       Instead of using one architecture diagram per chapter, introduce one diagram for all
o       Optionally a first draft could be prepared prior to the week
o       How to proceed with Checkpoint 1 "Whitepaper"
o       Goal: Firm plan on how to deliver the architecture deliverable content and administrative wise
-
-       Knowledge sharing session: Retrospective use cases 2011/2012 (2h)
o       What went good, what went bad?
o       What should be proceed with?
o       Preparation: Every WP to gather points for this session and present them
o       Goal: cross WP understanding on how to

-       Internal availability and roadmap alignment (1h+x)
o       How will the oAUTH/security/IDM topic be adoptable and be adopted within the different GEs?
o       ... further cross WP alignments
o       Timing and effort assumptions

-       Major events (1h)
o       Preparation of upcoming events and roadshows
o       Preplanning of Next FI-WARE general assembly
o       Will there be "Architecture weeks" with the new use cases?
*       Or: which events can be leveraged to distribute information to them?
o       Preparation: Administrative information needs to be gathered from respective work package owner and presented in the beginning of the session
o       Goal: have a plan for Cebit 2013
*       What to show? Whom to address? Where will go?

-       FI-WARE strategy (2h + more if needed)
o       Open discussion on what was discussed & communicated to the commission & what will change in 2013
o       Aspects: community building, concrete (short-term) exploitation activities towards phase in of external parties
o       Goal-setting for 2013 (measurable goals)
o       Preparation: WP11 to present current version of strategy as shown on the review
o       Goal: Discuss and sign-off messaging towards external parties

-       Open Innovation Labs session (2h)
o       What is the plan?
o       What is missing?
o       Who is doing what?
o       Goal: Transparency towards FI-WARE - document this in fi-ware-private wiki

-       Operational aspect session (2h)
o       Who does edit what & where
*       Which wiki for which deliverable, ...
o       Decide & document all upcoming major deadlines & do deliverable planning
o       Goal: wiki page with major milestones for FI-WARE members to read in the fi-ware-private wiki
*       External events (call-ends)
*       Rough time line

-       Enablement material session (again in small groups) (4h)
o       Come up with a set of slides, paper-drafts and other enablement material which helps others to understand/consume or build upon FI-WARE
*        "FI-WARE in 5 minutes" - on chapter-level and/or across-chapter
*       1-2 (Running) examples from the use cases
o       Goal: draft of (mainly technical) Presentation of FI-WARE

More optional sessions, if there is still time left:
-       Use case phase in planning & execution
o       Gather every possible information who might be the new use case projects and make this transparent within the WPL/WPA group
o       What to do with the new use cases - rough timeplanning, alignment, ...
-       Use case phase out planning & execution
o       What do we expect from the (existing) use cases  (e.g. validation questionnaire) and how can/should we further support them?
-       WWW and wiki changes
o       Do we need minor or major changes in the current set of "channels"?
o       Probably depending on the previous sessions, concrete plans on how to change wiki, www, twitter and more


Best,
Torsten


Dr. Torsten Leidig
SAP Next Business and Technology
SAP AG
Vincenz-Priessnitz-Strasse 1
76131 Karlsruhe, Germany
T +49 6227-7525-35
F +49 6227 78-52535

www.sap.com<http://www.sap.com/>

Please consider the impact on the environment before printing this e-mail.


Pflichtangaben/Mandatory Disclosure Statements:
http://www.sap.com/company/legal/impressum.epx

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20130111/61a1fd66/attachment.html>