1 / 9

KOSMOS Project Management

KOSMOS Project Management. Jay Elias. Reference: “KDSD Management”. Basic Principles. Need to work together constructively Need to control costs, schedule, performance How do we do this?. KOSMOS management structure Note small number of key people Note parallel structures

wind
Download Presentation

KOSMOS Project Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. KOSMOS Project Management Jay Elias

  2. Reference: “KDSD Management”

  3. Basic Principles • Need to work together constructively • Need to control costs, schedule, performance • How do we do this?

  4. KOSMOS management structure • Note small number of key people • Note parallel structures • Won’t change very much with COSMOS added

  5. Reporting & Coordination • Weekly video meetings – • Usually 5 key people (Sprayberry/Elias/Trueblood/Pogge/Martini) • Plus project scientist once re-designated • Add technical people as needed for discussions • Will add CTIO person(s) now COSMOS is part of overall effort

  6. Reporting & Coordination • Monthly reports - • Expenditures and progress against schedule • OSU budgets & reports people monthly by program (usually) • NOAO people time card, can track performance metrics • Project is small enough that metrics don’t tell us anything we don’t already know

  7. Documentation • Early production of key documents (SRD & FPRD) • Document design issues and discuss promptly (mainly optics so far, some flexure discussions)

  8. Structure of Effort • Underlying contract with OSU • Keep low-level tasks concentrated in a single institution, e.g.: • Optics at OSU, detector system at NOAO, spectrograph mechanical at OSU, top-level software at NOAO • Obviously can’t do this 100%, need to manage interfaces between “things” and between tasks

  9. General Relationship • Not a “vendor/customer” model • Though project is structured with well-defined responsibilities and deliverables • Attempt to reach key decisions in collegial fashion • Institutional cultures fairly similar

More Related