- 
                Notifications
    
You must be signed in to change notification settings  - Fork 30
 
Scrum Weekly Telco
        Cecile Braunstein edited this page Feb 4, 2015 
        ·
        147 revisions
      
    Planning of Scrum telco meeting every Tuesdays and Thursdays
- 05.02.2015
 
- High priority Tasks for the ITEA review
 
| Tuesday 11:30-12:00 | Thursday 9:30-10:30 | 
|---|---|
| Meeting ID: 393-207-557 | Meeting ID: 298-471-213 | 
| https://global.gotomeeting.com/join/393207557 | https://global.gotomeeting.com/join/298471213 | 
| Germany: +49 (0) 811 8899 6976 | Germany: +49 (0) 811 8899 6902 | 
| Belgium: +32 (0) 38 08 1855 | Belgium: +32 (0) 38 08 1856 | 
| France: +33 (0) 182 880 455 | France: +33 (0) 182 880 459 | 
| Italy: +39 0 699 36 98 80 | Italy: +39 0 553 98 95 67 | 
| Netherlands: +31 (0) 708 912 514 | Netherlands: +31 (0) 208 080 381 | 
| Spain: +34 931 81 6668 | Spain: +34 931 81 6669 | 
- 29.01.2015
 
- US-Subset-openETCS-Translation: How inter-requirement links should be handled and what other metadata may be useful to us.
 
- 22.01.2015
 
- Constraints Plan : Modeling rules https://github.com/openETCS/modeling/tree/master/ModelingRules/SysML_Constraints, SysML constraints to be added
 - US-TestPlan:
- Requirement lists, status ?
 - Documentation status In progress
 - (Parallel to 1/2) Unit tests for each feature status ?
 
 
-> We need to start a document "OpenETCS ToolChain Description" containing links to all documents and implementation we have
- 20.01.2015
 
- SysML/SCADE link vie @astante + constraints
 - Are we migrating to Luna: Yes @MatthieuPERIN in charge
 - @MatthieuPERIN check traceability
 - US-TestPlan:
- Requirement lists :@cecilebraun
 - Have a traceability mechanism
 - (Parallel to 1/2) Unit tests for each feature
 
 
- 13.01.2015
 
- WP7 priorities discussion
 - US-TestPlan:
- Requirement lists
 - Have a traceability mechanism
 - (Parallel to 1/2) Unit tests for each feature
 
 - US-Traceability feedback : I need feedback
 
- 08.01.2015
 
- US DataDictionaryWP7 position discussion: What do we do ? -> WP3 is only using SCADE, WP4 needs the data used by WP3. We need a discussion with WP3 about their process to see if we can be any help.
 - US TraceabilityArchitecture: Presentation of the WP7 architecture + discussion #471 Need More feedback
 - US TestPlan :
- Build the test task force -> need More people present at the telco
 - Tool chain requirement traceability -> we need a list of requirements We also need Unit tests for each plugin
 
 
- 18.12.2014 CANCELED
 
- US DataDictionary
 - US-Traceability-Architecture: Moritz status
 
- 16.12.2014
 
- US grooming session
 
- 11.12.2014 CANCELED
 
- US story grooming
 - US-Test-plan : Need a test team
 - US-Traceability-Architecture: Moritz status
 
- 
09.12.2014
- US-Test-Plan
- the selection of a test team -> delayed
 - take a decisions regarding to the traceability between the tests and the toolchain requirements or/and documentation -> for the test team
 - take a decision with the people involved in the tests regarding to the tool to be used to specify the tests cases
 
 
 - US-Test-Plan
 - 
04.12.2014
- Backlog process -> scrum of scrum presentation
 - Align the Backlog-product to the WP7 backlog -> todo
 - Word to Req-IF -> hierarchy refinement
 
 - 
02.12.2014 CANCELED
 
- New Build platform ?
 - ReqCycle evaluation
 
- 27.11.2014
 
- Data dictionary status -> Need explicit intend to use the data dictionary between WP3 and WP4
 - Marielle Feedback -> Too much Documentation missing, Papyrus weakness
 
- 25.11.2014
 
- Scrum of scrum status -> In progress, some new sessions are coming
 - (US-Traceability) Req-IF import status -> In progress -> WP3 neeeds some manual change of the requirements : Where to store the requirements data base ?
 - (US-Traceability) ReqCycle evaluation -> New branch wwith reqcycle will be available sson. Marielle and Cecile will experiments the use.
 
- 20.11.2014
 
- (US-Traceability) Import Subset-026 into Req-IF form -> first proposition sent
 - (US-Traceability) Status on the PROR-Papyrus Proxy -> included in the new release
 - (US-Luna-Migration) Matthieu will propose a release plan -> Luna migration estimated for February
 
- 18.11.14
 
- (US-DataDictionary) WP3 Data dictionary Process Support
-> Lukasz  will clean the documentation and propose a clean process
- Status
 - What is missing ?
 - Documentation Status
 
 - (US-Luna-Migation)
-> Matthieu will propose a luna release process
->  Major show-stoppers:
- Are we sure that Scade system will not come back
 - We need a clear status on the Scade API
 
 
13.11.14 CANCELED
- (US-Traceability) Import Subset-026 into Req-IF form
 - (US-DataDictionary) WP3 Data dictionary Process
 - (US-SysMLTraceability) Status on the PROR-Papyrus Proxy
 
- 06.11.2014
 
- Groom US-DataDictionary -> Need WP3 to explicit their process / Need some checks
 - Status on Defining requirements ID -> To be Included into the documentation/ Need a Req-IF format
 
- 04.11.2014
 
- Status US-Luna-Migration -> still problem with the API
 - Status Scade API -> we need an official statement from Esterel
 - Groom US-Latex-Traceability -> wait for stable ID's
 
- 23.10.2014
 
- Groom US-Luna-Migration
 - Groom Scade API
 - Groom US-Traceability
 - Overview Diagram
 
- 09.10.2014
 
- SysML2ScadeSuite plugin status
 
- 02.10.2014 Q1 sprint 19
 
- SysML2B plugin demonstration
 - SysML2ScadeSuite plugin
 - Data dictionary
 
- 25.09.2014 Beginning of Sprint 19 (@MatthieuPERIN)
 
- SysML2B integration -> TBD for Sprint 19 (CEA working on it)
 - SysML2ScadeSuite -> on going work, structure diagrams translated only for I/O, link still missing between operators (next action on the list), after that have to be tested by WP3. Next major update : launch transformation without re-writing the complete model, but no by-direction brifge (no scade to SysML translation)
 - Data dictionary -> on going common work from CEA and LAAS, User profile definition have to be used with SysML ? WP3 have to position them self about the user profile.
 
- 18.09.2014 End of Sprint 18
 
- SysML2B integration
 - Test plan
 
- 07.08.2014 End of Sprint 16
 
- Export Scade suite plug-in
 - Data dictionary
 
- 31.07.2014
 
- Data dictionary
 
- 24.07.2014
 
- Data dictionary
 
- 22.07.2014 Beginning of Sprint 16
 
- grooming session with all participants
 - Data dictionary grooming
 
- 17.07.2014 End Sprint 15
 
- Close sprint
 - Data Dictionary Session with WP3, WP4 and WP7
 
- 10.07.14
 
- Qualification plan
 - Papyrus/Pro-R
 
- 08.07.2014 Beginning of Sprint 15
 
- grooming session with all participants
 
- 03.07.2014 End Sprint 14
 
- Close sprint
 - Qualification Plan
 
- 01.07.2014
 
- Luna issues
 
- 26.06.2014
 
- Qualification plan
 
- 24.06.2014 Beginning of Sprint 14
 
- grooming session with all participants
 
- 19.06.2014 End of Sprint 13 CANCELED
 
- Documentation plugin
 - Traceability status
 
- 17.06.2014
 
- Documentation plugin CANCELED
 
- 10.06.2014 Beginning of Sprint 13
 
- Documentation plugin
 
- 
05.06.2014   End of Sprint 12 CANCELLED
- Close the sprint
 - Decide on priority for next sprint
 
 - 03.06.2014
 
- Documentation Plug-in
 - New use case with data dictionary
 
- 
22.05.2014  End of Sprint 11
- Luna status
 - Close the sprint
 - Decide on priority for next sprint
 
 - 20.05.2014
 
- Grooming Documentation
 
- 15.05.2014
 
- Product Backlog
 - Data dictionary
 
- 14.05.2014 Beginning of Sprint 11
 
- Data dictionary
 
- 8.05.2014 End of Sprint 10
 
- Close the sprint
 - Decide on priority for next sprint
 
- 29.04.2014 Beginning of Sprint 10
 
- Sprint organization
 - Traceability status
 
- 24.04.2014 End of Sprint 9
 
- Close the sprint
 - Decide on priority for next sprint
 
- 22.04.2014
 
- Documentation status
 - Papyrus status ?
 
- 17.04.2014
 
- Data Dictionary
 
- 15.04.2014 Beginning of Sprint 9
 
- Data dictionary
 - Test lab point
 
- 10.04.2014 End of Sprint 8
 
- Close the sprint
 - Decide on priority for next sprint
 
- 03.04.14
 
- Papyrus Status
 - Constraints checker for SysML
 
- 01.04.14 Beginning of Sprint 7
 
- Documentation
 - WP3 Needs
 
- 27.03.14 End of Sprint 7
 
- Data dictionary
 - Close the sprint
 - Decide on priority for next sprint
 
- 25.03.14
 
- Documentation
 
- 20.03.14
 
- Data Dictionary #310
 - Traceability
 
- 18.03.14 Beginning of Sprint 7
 
- Sprint 7 organization
 - Tasks grooming
 
- 
11.03.14 Canceled
 - 
13.03.14 Canceled
 - 
06.03.14
 
- 
04.03.14
 - 
27.02.14 End of Sprint 6
 - 
11.03.14
 - 
20.02.14 09:30
 - 
18.02.14 9:30
- ProR traceability #274
 - Model versionning
 - Documentation
 
 - 
13.02.14 End of Sprint 5
- Tracebility
 - Bitwlker data dictionnary point