August 2 and 3, 2010 KOSMOS Project Management Jay Elias.

Slides:



Advertisements
Similar presentations
CP Chapter 4 Schedule Planning.
Advertisements

PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
US CMS DOE/NSF Review: May 8-10, US CMS Cost & Schedule Mark Reichanadter US CMS Project Engineer DOE/NSF Review 8 May 2001.
HIGH PERFORMANCE MANAGEMENT CONFERENCE PROJECT MANAGEMENT
August 2 and 3, 2010 ReSTAR: The Origins of KOSMOS David Sprayberry.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
CSE 308 Project Management. SWE Communication Skills Management: Run a team meeting Presentation: Present aspects of your project during its development.
CLOSE PM Insight  Doing More of What Works, and Less of What Doesn’t Through Best Practices Measurement and Application.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Project Workshops Project Planning 1. Project planning proper management is essential the responsibility of the student with the advice of supervisor.
ICS Management Poor management is the downfall of many software projects Software project management is different from other engineering management.
Software project management Module 1 -Introduction to process management Teaching unit 1 – Introduction Ernesto Damiani Free University of Bozen-Bolzano.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
NGAO Team Meeting Management Peter Wizinowich May 26, 2009.
1 Project Management CIS 375 Bruce R. Maxim UM-Dearborn.
Implementation. We we came from… Planning Analysis Design Implementation Identify Problem/Value. Feasibility Analysis. Project Management. Understand.
Projmgmt-1/22 DePaul University Project Management I - Realistic Scheduling Instructor: David A. Lash.
Readiness Index – Is your application ready for Production? Jeff Tatelman SQuAD October 2008.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
LSU 07/24/2004Defining Project Tasks1 Defining the Project Tasks Project Management Unit, Lecture 4.
CHAPTER 19 Building Software.
Earned Value Management
Frustrated with your sales numbers? Learn best in class sales practices.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
Typical Software Documents with an emphasis on writing proposals.
Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.
August 2 and 3, 2010 KOSMOS Design Considerations Jay Elias.
August 2 and 3, 2010 Project Cost, Schedule, Risk and Contingency Jay Elias.
Getting Involved in the Research Data Alliance Stefanie Kethers
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Prof. Aiken CS 169 Lecture 61 Project Planning CS169 Lecture 6.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Project Post-Mortem University of California Berkeley Extension Copyright © 2008 Patrick McDermott From an AutoContent Wizard 10/27/2007.
Copyright 2008 Introduction to Project Management, Second Edition 2  Many people have heard the following sayings: ◦ If you fail to plan, you plan to.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
Project monitoring and Control
(A radical interpretation) Tomo Lennox Bow Tie computer services Why Agile Works.
Review: Cohesion and Coupling, Mutable, Inheritance Screen Layouts Software methodologies – Extreme Programming Object-Oriented Design – CRC Cards - UML.
6.3 Your Budget Worksheet. Section 6.3 Your Budget Worksheet  Goals: Identify steps you should take to create a budget worksheet. Explain common problems.
College FIRST Matthew Leese Rochester Institute of Technology Teams 340, 1567.
1 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
Project Management (and Software). Who Does What, and When? Project Management is concerned with the allocation of resources to complete a project. Project.
3.1.1 Optics, Optical Corrector, Mechanical Systems M. Johns, C. Claver.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
Advanced S/w Eng - s/w productivity issues 1 Software Productivity Issues Why do software projects fail? Advanced Software Engineering COM360 University.
SCRUM.
Evaluating EVM January 13, EVM Issues and Opportunities ▪ EVM Basics ▪ EVM Issues ▪ EVM ETC and EAC Calculations ▪ EVM Cost and Schedule Value Calculations.
Goal Setting. Goals Something that you want and are willing to work for. Something that you want and are willing to work for. Why set goals? Why set goals?
Not for Distribution Outside of MBP1 April 11, 2012.
Background Research Group and Advisor Group’s overall research goals Technology to: –Build On –Integrate –Advance.
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
IT-301 Project Management I: Unit 4: Cost Management.
What is a WBS? A Work Breakdown Structure is not a list of tasks, a schedule or an organization chart. Rather it provides the basis on which a task.
SCT Project Management Issues
Earned Value - What is it
[Project Name] Post-Mortem
S4 will be a “big” Collaboration:
COSMOS Status David Sprayberry, Sean Points & Jay Elias
KOSMOS Design Considerations
PROJECT NAME POST-MORTEM
WP1 INERTIA Framework Requirements, Specifications and Architecture
How to keep your Enterprise GIS Project on Track
[Project Name] Post-Mortem Presentation Template
Project Name Post-Mortem
X-DIS/XBRL Phase 2 Kick-Off
NSS Instrument Project Tollgate Coordinator
Agile Project Management and Quantitative Risk Analysis
Information system analysis and design
Presentation transcript:

August 2 and 3, 2010 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