Effectiveness of Meeting Work Flow in Geographically Distributed Team

Effectiveness of Meeting Work Flow in Geographically Distributed Team
Slide Note
Embed
Share

Resolving issues efficiently in a geographically distributed team requires strategic use of working meetings. Onsite meetings facilitate rapid collaboration, while virtual meetings leverage time zone differences. Streamlining meeting processes and aligning status reporting formats with regular workflow are vital for optimized team productivity.

  • Team Collaboration
  • Meeting Efficiency
  • Geographically Distributed Teams
  • Workflow Optimization
  • Virtual Meetings

Uploaded on Mar 03, 2025 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. Ocean Observatories Initiative 2015 May OOI Construction Review Homework

  2. Effectiveness of Meeting Work Flow In a geographically distributed team, working meetings are essential to resolving issues in a timely manner During intense integration activities, onsite meetings held at Rutgers for rapid response and collaboration Virtual meetings are usually arranged by Uncabled vs Cabled sensors Leverage time zone difference: Uncabled Eastern, Cabled - Pacific Minimize waiting time of team members 2 weekly meetings can be characterized as overhead as they directly relate to progress reporting to the entire OOI team Need to streamline this process and minimize special reporting formats Formats for status reporting should be products of our normal work flow 1

  3. CI Testing Flow See Excel spreadsheet 2

  4. Integrated Build Plan September May August July June Commissioning Conditional Acceptance Events Globals Papa/Surface Moorings/ Endurance//Cabled CSPP Alpha/Beta Alpha Test Beta Test UserTest NSF Review Load Test Load Test Initial Capability (Build 4.1) Clustered Cassandra servers Clustered Cassandra server Hardware/ Network Build 6 (Not in Plan) Final/datacenter Build 3 Build 4 Build 5 CI Build Integration Integration V&V V&V V&V 3 4.1 5 V & V 6 Test Procedures Test Procedures 3 4 5 uFrame UI uFrame uFrame uFrame/UI uFrame/UI CI Tasking 4.5 4.1 5 6 5 Bench Array Live UI C2 Full Array Full Array Cal Cabled Array Data & Test Uncabled Data Calibration/Ingest/metadata Plug-ins Sensors & Algorithms Redmine 6 V & V

  5. Instrument and Data Delivery See spreadsheet 4

  6. Capabilities by Build Capability Build 1 Build 2 Build 3 Build 4 Build 5 Build 6 X X X X X X X X X X X X X X TBD uFrame Web Services interface Asset Management: Mooring Data Web Service: Query & Data Retrieval UI: Query Telemetered Data UI: Landing Page Asset Management: Lifecycle Management UI: Manage User Accounts UI: Trouble Ticket Integration UI: User based Data Annotation Algorithm: Quality Control & Calibration Alert Services Asset Management: temporal, geographic, Asset ID UI: Alerts & Alarms UI: Help, Glossary, & How-to UI: Command & Control UI: Complex Plots Asset Management Schema Updates Non Time Series Plotting Data Annotation Telemetry Status Asset Management: Full Metadata access/retrieval Multi Tier Data Storage Capability Machine Interface: further standards, gridded data Web Service & UI: Interface for bulk data changes Data "Push" capability (i.e. NODC) X X X X X X X X X X X X X X X X X X X X X X X X X X X X X 5

  7. Ability to Deliver to Extended Schedule Team has demonstrated ability to resolve emerging problems Still work to resolve to resolve on Casandra performance The majority of instrument drivers have been coded, tested and integrated to uFrame This week achieved a fully integrated system from User Interface to data repository, remaining work incremental additions of instruments, data streams, and software capability Need to make integrated system available to Data Management Team for completing Science Review Assessment at end of Build 5 V&V, Load and Beta Test 6

More Related Content