70 likes | 80 Views
Explore the effectiveness of onsite, virtual, and weekly meetings in a geographically distributed team setting. Learn how to leverage time zones, minimize waiting time, and streamline progress reporting to enhance work flow. This review discusses the integration activities, CI testing flow, and the transition from Build 5 to V&V, Load, and Beta Test phases.
E N D
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
CI Testing Flow See Excel spreadsheet
Integrated Build Plan September July August May 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 Build5 4.1 CI Build Integration 5 3 6 V & V Integration V&V V&VV&V Test Procedures 3 4 5 Test Procedures uFrame UI uFrame uFrame uFrame/UI uFrame/UI CI Tasking 6 4.5 4.1 5 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
Instrument and Data Delivery See spreadsheet
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