Here are the RHO deliverables, for Design Phase Closure. As you have all done many times with me, I'm looking for a summary view on each section. RMO will be shared by Sophie and Lisa.
I'll post the spreadsheet to the database (Links and Migrations tab https://sites.google.com/a/seagate.com/crawford-rho-nrm/links ) for any of you that want to use the spreadsheet as your checkoff list. The 2nd tab is cleaned up for presentation use. My current suspicion is that drive will push this date due to lack of TVM closure. We should also consider general phase issues to note in a list.
For each section:
1 - Summary page noting the item status (hopefully all closed). Include open or incomplete items with single bullet on actions to address.
2 - Backup pages for open items. What is status, what is plan to close, key dates....
3 - Backup pages (even much simpler) to demonstrate the closed items. Simple proof of closure (i.e., Proof of YIP would be a picture of the YIP...)
4 - A summary of ongoing work and open activities and quals is a good single slide to have for info only.
Our goal is always to NOT conduct a full design review. If management wants a design review, that can be requested. Rather, to have the shortest and simplest phase reviews possible. If all items are closed, I expect our reviews to be a total of 5 minutes. If any items are open, those are the only topics of discussion. Our internal team review prior will be where we agree that items are closed - that's where we get to work those backup slides. With management, I hope the summaries suffice.
I think this results in the clearest communications, and the least amount of unnecessary work for this team.
Facilitators for each section noted here (we'll talk to it in the core team meeting tomorrow): Gather up your input and send to me. (I'll be out next week, so would help for me to get your input before Friday so I can set it aside at least and not lose it in the Google pit of despair).
Note our Design and qual config does look to be the Q5R/CT9 reader/writer - so maturity requirements would be relative to that config.