Work Package Controls Inception Phase Review February 5th, 2010 Johannes Gutleber PR-100203-a-JGU, February 5th, 2010 J. Gutleber 1 R. Gutleber.

Slides:



Advertisements
Similar presentations
Directions for this Template  Use the Slide Master to make universal changes to the presentation, including inserting your organization’s logo –“View”
Advertisements

Roadmap for Sourcing Decision Review Board (DRB)
Chapter 4: Inception is Not the Requirements Phase
WP CO Status and Progress December 8th, 2010 Johannes Gutleber PR a-JGU, December 8th, 2010 J. Gutleber 1 R. Gutleber.
Development of ISO standards for AD syringes SIGN Meeting Cambodia, October 2002 Injection technologies G Gerald Verollet.
Rational Unified Process
1 Test Planning CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 9, 2007.
VRVS, Jan. 2006CERN AB-ATB1 Safety Review Solenoid & Cryogenics CERN AB-ATB VRVS session, Jan
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
1 DOE Annual Review -June 15,2005 An Overview of Conventional Facilities (Civil Construction) U. S. ILC Civil studies and cost issues for Snowmass Fred.
TSB–88 For Public Safety LTE.  Proposal: release documents in phases ◦ First release:  Basic LTE coverage modeling and verification concepts such as.
PSU CS 106 Computing Fundamentals II Product Life Cycle & SW Product Life Cycle HM 9/3/2007.
Work Package Controls MACS Week June 2010 June 24th, 2010 Johannes Gutleber PR a-JGU, June 24th, 2010 J. Gutleber 1 R. Gutleber.
IS&T Project Management: How to Engage the Customer September 27, 2005.
Development plan and quality plan for your Project
Project Management Body of Knowledge PMBOK
Optimism R&D to be resumed! Three beam tests planned at Kek, –Hybrid target (KEKB Linac) –Liquid target (ATF Linac) –Boron-Nitride Window (KEKB) –(Starting.
Project Management – The Project Charter
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
RUP Fundamentals - Instructor Notes
System Planning- Preliminary investigation
OSF/ISD Project Portfolio Management Framework January 17, 2011.
Safety concept and scope for WP Controls Fabian Moser February 5, 2010.
Matthias Mekschrat h_DA WS 2011Logistical applications and optimizationsSlide 1 Logistical applications and optimizations.
PPMT CE-408T Engr. Faisal ur Rehman CED N-W.F.P UET P.
The Software Quality Assurance System By Jonathon Gibbs Jonathon Gibbs (jxg16u) 26 th November 2009.
ACS 560 – SOFTWARE ENGINEERING Course Accomplishment Summary Shilpashree K.S Fall 2010 Purdue University – Fort Wayne Instructor – Dr. John Tanik.
Project Management Workshop Overview By Tarek Lahdhiri Region 4 PACE Chair IEEE Region 4 Meeting January 30/31, 2004.
WP CO Column Status and Progress October 7th, 2010 Johannes Gutleber PR a-JGU, October 7th, 2010 J. Gutleber 1 R. Gutleber.
Project Life Cycle.
Contract Training Class I
HLRF DRAFT Global Design Effort 1 Defining EDR* Work Packages [Engineering Design Report] Ray Larsen SLAC ILC Division for HLRF Team DRAFT April.
QA Methodology By Rajib Roy Independent Consultant Qcon.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Develop Project Charter
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Initiation and Planning for Success Sridhar Seshagiri Rao, PMP Innova Solutions Inc. Santa Clara, CA. April 9 th 2004.
Development through partnership Infrastructure Delivery Management Toolkit: 2010 Edition Delivery Process 2: Project Management 1.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Integration integration of all the information flowing through a company – financial and accounting, human resource information, supply chain information,
OFFICE OF SCIENCE 1 Closeout Report on the DOE/SC CD-3b Review of the Utilities Upgrade Project (UUP) Fermi National Accelerator Laboratory August 11-12,
P r o j e c t : from INITIATING to CLOSING ( 1 ).
Directions for this Template  Use the Slide Master to make universal changes to the presentation, including inserting your organization’s logo –“View”
Competency-Development Project 08-December MDIC 2 What is the Competency-Development Project? ‏ Purpose: The purpose of this project is to improve.
IAEA International Atomic Energy Agency Technical Meeting on Regulatory Oversight of Human and Organizational Factors Vienna, Austria | December.
WP5– Flagship Deployment Phil Evans - CGI This document produced by Members of the Helix Nebula consortium is licensed under a Creative Commons Attribution.
Conventional Facilities integration: Approach and Issues Daniel Piso Fernández WP Leader (WP13 Conventional Facilities Integration Support) November 5,
Rob Connatser NSS Instrument Work Packages and XLPM.
Project Management PTM721S
Risk Management DIA Working Group 22 May 2017.
Background D/HSO Announcement of Opportunity (July 2011) in coordination with D/EOP soliciting scientific experiments for the International Space Station.
Project Management (x470)
Software Configuration Management
WORK BREAKDOWN STRUCTURE
Campus Master Plan.
Project Management Lifecycle Phases
ILC PROJECT ENGINEERING DESIGN REPORT CFS Europe – KICK OFF MEETING
Project Management.
IBR Documentation Review
Phase 3 Tollgate Review Discussion Template
Outcome TFCS-11// February Washington DC
Overview of Project Management
Project Scope Management
ICD-10 and Clinical Documentation
Insert subhead here Project Status.
Project Scope Management
Basics of Project Planning
CoDR Scope Definition, Objectives & Agenda Jodrell Bank
Overview of Project Management
Risk Management NDS Forum June 23rd 2010.
Presentation transcript:

Work Package Controls Inception Phase Review February 5th, 2010 Johannes Gutleber PR a-JGU, February 5th, 2010 J. Gutleber 1 R. Gutleber

INTRODUCTION AND REVIEW SCOPE DEFINITION PR a-JGU, February 5th, 2010 J. Gutleber 2

Review Schedule 09:00 – 09:10Welcome (MBE) 09:10 – 09:20Introduction and scope definition (JGU) 09:20 – 10:10WP controls high-level goals (JGU) 10:20 – 11:10Development process presentation (JGU) 11:10 – 11:35Configuration management environment (RMO) 11:45 – 12:20Safety concept and scope (FMO) 12:20 – 12:45Safety system outlook: interlock system (MMA) Lunch Break 14:30 – 17:00 Closed review session PR a-JGU, February 5th, 2010 J. Gutleber 3

Goals of the Review Achieving agreement on scope of work package “controls” Achieving agreement on development process Acknowledging identified risks and achieving agreement on proper identification of major risks Achieving agreement on high-level functions of system to be developed Acknowledging and achieving agreement of work organization and work to achieve the goals PR a-JGU, February 5th, 2010 J. Gutleber 4

WP Controls Contributions Project documentation Summary presentations Q & A style additional information Review report distributed after review PR a-JGU, February 5th, 2010 J. Gutleber 5

Contributions from Reviewers Identify open issues that would prevent advancement to the next project phase (elaboration phase). Propose mitigation actions on the risks identified. Help to refine scope of the work package Assess realism of current project development setup Give recommendations Point out corrective measures on the next steps PR a-JGU, February 5th, 2010 J. Gutleber 6

Expected for Milestone Defined work package scope Agreement with other work packages on scope Cost and schedule estimated Project risk management process defined Major risks identified and acknowledged by top management Parameters from existing processes and designs identified Project environment defined Initial requirements defined Project plan defined Project plan aligned with top management Development process defined and accepted Medical device safety concept/scope completed PR a-JGU, February 5th, 2010 J. Gutleber 7

Achieved at Milestone Defined work package scope Agreement with other work packages on scope Cost and schedule estimated Project risk management process defined Major risks identified and acknowledged by top management Parameters from existing processes and designs identified Project environment defined Initial requirements defined Project plan defined Project plan aligned with top management Development process defined and accepted Medical device safety concept/scope completed PR a-JGU, February 5th, 2010 J. Gutleber 8