1. Steps towards effective eTRIKS dvt Emmanuel Van der Stuyft & Peter Rice 4-dec-2013 Agenda ◦ eTRIKS devt setup explored ◦ Proposed modular team setup and process ◦ Proposed organization and action items 1

2. eTRIKS devt setup explored Available infrastructure frame to fit things in ◦ eTRIKS reqs wiki with development topicsdevelopment topics  Based on entries from Sep 2013 resource team meeting  Description; Benefits; Stakeholders + links to requests; priority  Development -> link to Pivotal epics ◦ eTRIKS Pivotal Tracker eTRIKS Pivotal Tracker  Helpful tutorials: Concepts video; Getting StartedConcepts videoGetting Started Reflection on review: Bypass obstacles in streamlining work ◦ Overlapping, redundant interdependencies between URS and development  How to break op URS into modular functions that fit into distinct functional domains?  => Provides clear divide/interfacing line between complementary teams with manageable scope ◦ Clear articulation of what exactly is desired  Fuzzy unclearly articulated reqs  Both at the source and on transmission -> how to avoid ‘the broken telephone’?  Need clear ownership by business analysts at different levels (URS and functional feature module) 2

3. Proposed modular team setup and process ◦ 4(+2) teams focusing on distinct functional domains  Modelling of diverse data types of interest in tranSMART  Data curation and upload into tranSMART  Data browsing and querying (or bringing the right data together intelligently)  Data analysis and visualization  Core tranSMART work (maintenance, tM1.2, Oracle/PG, performance…)  More long-term oriented work (semantic space, project workspace, etc...) ◦ Steps and roles in regular iterations within each team  Getting requirements (user rep) -> Owned by the requestor  Story breakdown (user and devt rep) -> see synergy betw what & how?  Story estimation (devt rep) -> Owned by the provider  Prioritization (user rep) –> Owned by the requestor  Build software (devt rep) -> Owned by the provider  Acceptance (user rep and devt rep) -> final sync point  Also needed -> release deployment & info/training (devt/hosting/user rep) 3

4. Proposed organization and action items ◦ ‘Functional domain’ team organization  Dedicated eTRIKS-WP6 key user representative (~0.25 FTE)  To streamline user-related tasks in iterations in close collaboration with developers  To help frame the team’s way of working  With openness to drawing in resources with added value from the tranSMART open source community  See eg link between data modelling group and ‘tranSMART NGS data working group’tranSMART NGS data working group  Dedicated eTRIKS-WP2 software developers (1-2 FTE)  To streamline devt-related tasks in iterations in close collaboration with key user rep ◦ Communication mechanisms  Functional domain team decides on internal communication modus  Key user rep manages URS to functional feature modules and prioritization  Higher level communication -> Synthesis at which WP6 platform and regularity?  More tactical level and syncing between functional teams -> weekly WP2/WP6 mtgs ◦ Action items  Do we agree to this approach in general?  Identify WP6 key user reps as well as WP2 developers of each funct domain team  Agree on impact of this on focus of WP2/WP6 meetings  See ongoing pilot framing exercise in ‘browsing/querying’ functional domain 4