NOTE: For this meeting and future dates we are conducting the meeting on Blue Jeans (use web browser or below):

Web Browser:

https://bluejeans.com/293724745/

> Connecting directly from a room system?

> 1) Dial: 199.48.152.152 or bjn.vc
> 2) Enter Meeting ID: 293724745 -or- use the pairing code

 > 
> Just want to dial in? (all numbers)
> 1) Direct-dial with my iPhone or 
> +1 408 740 7256+1 408 740 7256 
> +1 888 240 2560+1 888 240 2560 (US Toll Free)
> +1 408 317 9253+1 408 317 9253 (Alternate Number)
> 
> 2) Enter Meeting ID: 293724745

Date

Attendees

(sorry if I missed anyone)


Goals
  • Monthly meeting to discuss and resolve specific management processes, etc.

Discussion items


Item
Who
Notes

Gregory Dubois-Felsmann

Existing risks were created to establish overall risk management process, support contingency. They are high-level and not easily retired. There should be risks which are more detailed and discrete.

Kian-Tat Lim

Need to retain contingency purpose, suggest 2 levels with higher level in register "owned by" DM System Architecture Team (including Monthly Reviews) and lower level owned by T/CAMs, S/TLs, possibly in a different tool.



Jeff Kantor


NSF requires all baseline changes and contingency allocations cross-referenced to risks in register. Higher level risks in register will serve this purpose and should be retained. Could improve retire-ability of these.


Frossie Economou
Need simple, editable list of risks associated with a planning cycle. Not in register.

Jacek Becla
Register is black box, not clear how to use. Most risks are known to others (e.g. hybrid focal plane).

John Swinbank

Pulled in multiple directions. Not clear if our charter is to improve existing tool/process, satisfy NSF, create another tool for our use, etc. It is natural to consider risks with cycles.


Unknown User (xiuqin)

Agree with above, register is too high-level, generic for cycle planning.


Simon Krughoff
Agree with above, register tool is "clunky".



 Action items

  • Develop approach to having risk list with cycle planning and means for "bubbling up" risks from it to higher level register as needed.  (KTL handed over to Tim Jenness, who is working on implementing something in JIRA)