Presentation is loading. Please wait.

Presentation is loading. Please wait.

New ‘Functional Domain Team approach’ to streamline requirements to delivery Annual Meeting 2014 Portafira Hotel, Barcelona January 29 th and 30 th 1.

Similar presentations


Presentation on theme: "New ‘Functional Domain Team approach’ to streamline requirements to delivery Annual Meeting 2014 Portafira Hotel, Barcelona January 29 th and 30 th 1."— Presentation transcript:

1 New ‘Functional Domain Team approach’ to streamline requirements to delivery Annual Meeting 2014 Portafira Hotel, Barcelona January 29 th and 30 th 1

2 – Introducing the ‘Functional Domain Team approach’ Problem assessment Proposed solution – Modularity to avoid fragmentation/redundancy – Key roles to streamline work » Functional Domain Team Leads – Levers to influence priorities and progress – Q&A – Review of individual Functional Domain Teams Agenda 2

3 – Reality check User reps/DPOs voiced their needs 4x in 2013 Match with what has been accomplished? – Unresolved questions How can users (WP6) and devs (WP2) interact effectively? How to translate high level URS into bitable chuncks? How to avoid fragmented/redundant functionality? How to orient focus, to result in agile delivery? Can we draw extra resources in to match the workload?... Problem assessment 3

4 Modularity to avoid fragmentation/redundancy 4 IMI projects to support in eTRIKS Functional need space Data Modelling Distinct Functional domains Data curation and Loading Analysis and Visualization Browsing and Querying Core Development Long-Term Development UBIOPRED ONCOTRACK OTHER PROJECTS... ABIRISK Complexity divided into modular non-overlapping domains, manageable by 1 team across projects

5 – Functional Domain Team Leads User rep, to facilitate with adequate partners – URS breakdown into manageable user stories – Close interaction with dev team for basic insight » No ‘throwing over wall’ » Build sufficient insight in the technical space – Agile priority setting (no analysis-paralysis) – User acceptance – Drawing in other potentially valuable contributors (see later) Developer rep, to facilitate with adequate partners – Build sufficient insight in the functional space – Architecture/design choices – Estim devt workload of small user stories for prioritization – Coordinate prioritized agile development with developers across eTRIKS devt team – Critical role for Peter Rice across FDTs to promote interconnected developer team dynamics to ensure FDTs get a fair share in eTRIKS developer bandwidth (may vary) Key roles to streamline work 5

6 Functional Domain Team Leads 6 Functional DomainFDT-User RepFDT-Devt Rep Data modelling (DM-FDT)Anthony RoweAxel Oehmichen Data Curation & Loading (DCF-FDT) Fabien RichardDavid Johnson Browsing & Querying (BQ-FDT) Emmanuel Van der StuyftMay Yong Data Analysis and Visualization (DAV-FDT) Mansoor SaqiPeter Rice Core Development (CD-FDT)Jay BergeronFlorian Guitton Long-Term Development (LTD-FDT) Chris MarshallIbrahim Emam

7 – FDT-UsR priority-related responsibilities: Set and drive ‘base priorities’ – Taking into account base eTRIKS resources limitations – Wat’s tackled must fill a key need for most projects – Drive delivery of small increments in short cycles – In this way, avoid analysis-paralysis Look to leverage – Existing relevant functionality » Eg help branch into TM 1.X, and be best placed to move forward – Non-eTRIKS resources, by getting them interested to collaborate – DPOs can obtain priority to project-specific needs By bringing in devt resources and/or budget to operate within FDT-framework – Eg 1.2 FTE/IMI project would double resources » See potential impact on delivery » See how this cost would compare to each project on its own... Levers to influence priorities and progress 7

8 – Open weekly cross-FDTs-sync meeting on Mondays from 1-2 PM (CET) – start Feb 10th First part: focus on interaction between FDTs – Awareness on each team’s progress and challenges – Joint problem solving – Sync on beyond eTRIKS collaboration options –... Second part: focus on interaction with IMI project user reps – Sync on priority setting for IMI project-dedicated devt resources – User requirement/user scenario/user story review and functional breakdown for backlog – Demo of newly developed functionality for feedback Will be invited to these meetings Required: FDT-UsR, Peter Rice Optional: IMI project user reps (=DPOs); FDT-DevR Anyone flagging up interest and willing to contribute Agenda Agenda items will be posted a few days before each meeting Please suggest agenda items well ahead of time to Emmanuel Van der StuyftEmmanuel Van der Stuyft Resources to interact with the Functional Domains teams 8

9 An ‘eTRIKS Requirements Streamlining’-wiki to support the FDT-process‘eTRIKS Requirements Streamlining’-wiki Resources to interact with the Functional Domains teams (continued) 9 Deliv Package(s) owned by DPO Functional ref doc (see example)example List of Functional Feature Modules (FFM) for X-FDT (see example)example Breakdown, estimate, prioritize Develop Send for release by CD-FDT Accept URS to FFM map owned by DPO (see example)example User scenario owned by DPO (see example)example DPO+ FDT- user reps break up user scenario in high level functions and associate each with spec FDT DPO- managed Backlog managed by FDT-user rep Managed within FDTs Regular interaction FDT-leads Regular interaction DPOs – FDT-user reps Regular interaction betw FDTs and ‘world’ Governance (Resource Team Meeting) Actively look for resourcing extension (cmmty, IMI project spec priorities,..) User story-based short iteration cycles

10 – Introducing the ‘Functional Domain Team approach’ Problem assessment Proposed solution – Modularity to avoid fragmentation/redundancy – Key roles to streamline work » Functional Domain Team Leads – Levers to influence priorities and progress – Q&A – Review of individual Functional Domain Teams Agenda 10

11 – Agenda Functional Domain delineation Proposed base priority areas and related approach Breaking down user scenarios into user stories Capturing a vision of the broader context Proposed next steps Review of Querying & Browsing FDT 11

12 – Focus on bringing right data together intelligently To support their usage for investigation and analysis (DAV-FDT) in the following scenarios – Provide data selection as input to analyses interfaced with tranSMART – Export data selection for use by native analyses outside of tranSMART – Hand over selected files (lv3-data) directly to file viewing/analysis applics By leveraging 2 key resources for that – Dynamic querying, bridging the full landscape » Subject types; phenotypical data (lv1); difft molec profiling data (lv2); drill down to files (lv3) – Static list management » To provide composite synthesis of cascaded sequence of queries/analyses » To provide output from query/analysis as input to next query/analysis step IN: API-based back end functions OUT: key GUI functions (see DAV-FDT) BQ-FDT Functional domain delineation 12

13 – Translational research looks for relationships betw Patterns in phenotypical characteristics -OK Patterns in molecular profiling characteristics -NOK => Strengthen molecular profiling-based cohort selection capabilities – Static list mgt capabilities missing To provide output from query/analysis as input to next step To provide composite synthesis of sequence of Q&A For flexible export of this rich information – as input to next query/analysis step => Extend static list mgt capabilities – Progressive modular wrapping of functionality built For interoperable re-use Proposed base priority areas and related approach 13

14 Analysis function needs to be able to call query functionality modularly Query capabilities to implement: (For given patient cohort), retreive values for a mix of multidimensional data types Support diverse list types, beyond grid view Support merging input and output variables from calculation function in grid view Breaking down user scenarios into user stories 14 User scenario: Categorize a selection of breast-cancer patients into high vs low risk Based on the Veridex Biomarker described in this Lancet articlethis Lancet article Make all the related data available in a static list and export for exploration Veridex Biomarker calculation function: Required input data for each patient: Estrogen receptor (ER) concentration (Proteomics data type) The expression values of 76 specific genes A static list with for each of the 76 genes, the corresponding Cox coefficient as provided in the article Output data from the calculation function List with per patient, the estimated risk category (high, low) Merge all data in grid view (static list) for export: PatientRaceGenderAge... ER conc (fmol) Name of gene i Expression of gene i Cox coeff for gene i.... Risk category 123 Cau- casianWoman53 11.02gene i23.57-3.83 High

15 Capturing a vision of the broader context 15

16 Proposed next steps 16 Iteratively build URS backlog Fill in generic view of key functions to eventually support (=backbone) Drill down into manageable user stories of interest Work towards making functionality available Identify ongoing work in this field Can we help integrate into TM 1.X and so gain expertise too? Meaningful to join forces? Identify sufficiently simple user stories with high added value to develop against in short agile cycles Broadcast activities/areas of interest with open invitation for contributors to join Eg potential ‘find Omics files of interest’ contribution from JNJ?

17 – Fill Fill 17


Download ppt "New ‘Functional Domain Team approach’ to streamline requirements to delivery Annual Meeting 2014 Portafira Hotel, Barcelona January 29 th and 30 th 1."

Similar presentations


Ads by Google