OOI CI Release 2 LCO Review August 30, 2011. Contents Logistics and Protocol “The Situation” Charge Expectations.

Slides:



Advertisements
Similar presentations
How to Transfer from Waterfall to Iterative Te Bai, Ji Qi.
Advertisements

R2 LCO Review Outbrief Summary Thanks Very impressed with: – Amount of work – Comprehensive architecture and artifacts – Knowledge of staff.
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
Arlow and Neustadt ch.21 What is the unified process? People are more important than any process. Good people with a good process will outperform good.
NEES Project Management Workshop June 16 June 18 1 Segment 2.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 4: Phase Management - Elaboration.
Rational Unified Process
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Iterative development and The Unified process
By Saurabh Sardesai October 2014.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
PRESENTATION TEMPLATE. The Goal is… o To communicate the company’s story as clearly as possible o To create excitement for the opportunity to attract.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
S/W Project Management
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
RUP Fundamentals - Instructor Notes
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
2/5/20101 R-DCR ARB Preparation A Winsor Brown CS 577B Spring 2010.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Object Oriented Design and Analysis Rational Unified Process.
Iterative Project Management Chapter 3.2 – The Unified Process Modified considerably by Instructor Class Discussions / Presentations.
Chapter – 9 Checkpoints of the process
Executive Session Director’s CD-3b Review of the MicroBooNE Project January 18, 2012 Dean Hoffer.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Continuous Improvement Story Cover Page The cover page is the title page Rapid Process Improvement Story Template O Graphics are optional This CI Story.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative Construction Plan John Graybeal Life Cycle Architecture Review La Jolla, CA.
UNNExT Capacity Building Workshop on Single Window Planning and Implementation Module 1 – Introduction to the workshop UNNExT Capacity Building Workshop.
Fleming College Quality and Risk Management Review Summary November 10, 2005.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Core Banking Transformation: A Roadmap to a Successful Core Banking Product Implementation - PMI Virtual Library | | © 2008 Kannan S. Ramakrishnan.
Cyberinfrastructure R3 Life Cycle Objectives Review January 8-9, 2013 Ocean Observatories Initiative CI Release 3 Life Cycle Objectives Review Preliminary.
RUP Fundamentals Instructor Notes
Cyberinfrastructure Release 2 Production Readiness Review 12 December 2013.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Cyberinfrastructure R3 Life Cycle Objectives Review January 8-9, 2013 Ocean Observatories Initiative CI Release 3 Life Cycle Objectives Review Charge to.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
CI R1 LCO Review Panel Preliminary Report. General Comments –Provide clear definition of the goals of the phase (e.g. inception), the scope, etc. in order.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 Rational Unified Process – Part 2 Original slides modified.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
University of Southern California Center for Systems and Software Engineering RDCR ARB CS 577b Software Engineering II Supannika Koolmanojwong.
Project Reviews Providing Value to Stakeholders PMI Sacramento Valley Chapter PMO Forum – June 2007 Bob Cutler, PMP Hubbert Systems Consulting, Inc.
Principal Investigator ESTCP Selection Meeting
Iterative development and The Unified process
TK2023 Object-Oriented Software Engineering
DoD Template for Application of TLCSM and PBL
Class 12: Exam Review Client project
Session 2 Dr. Dan C. Surber, ESEP
Iterative, Evolutionary, and Agile Rational Unified Process
ISA 201 Intermediate Information Systems Acquisition
Principal Investigator ESTCP Selection Meeting
TechStambha PMP Certification Training
Global Social Venture Competition Pitch Deck
CS 577b Software Engineering II -- Introduction
CS577a Software Engineering ARB #2 Workshop
Employee engagement Delivery guide
Principal Investigator ESTCP Selection Meeting
Principal Investigator ESTCP Selection Meeting
Presentation transcript:

OOI CI Release 2 LCO Review August 30, 2011

Contents Logistics and Protocol “The Situation” Charge Expectations

Logistics and Protocol All sessions will begin sharply at time indicated or announced (10 minute beak is not 15-20) Need to stay on Schedule Please turn cell phones off Process: – CI presents according to agenda – Board refrains from questions during presentations unless critical – Board has floor for questions following each presentation – Audience is permitted questions AFTER Board is satisfied and if time permits Can contact Bill Bergen if more questions

The Situation Our thoughts are with our colleagues that could not join us due to Irene Not our normal review – Remote participants- not desirable but will make due – Not all of Board can participate – Major, Major Milestone Not “check the box” review R1 PRR should precede R2 LCO – R1 requirements and use cases met/demonstrated R2 – all about the marine IOs – Need strong presence – Need concurrence – Need to be demonstrably integrated with CI

Review Board Charge (three big items) A.Are Release 2 LCO Review Entry Criteria Met? (convince Board should be here) B.Are Release 2 LCO Review Exit Criteria Satisfactorily Met? (convince Board that it is OK to leave) C.Provide Guidance to OOI leadership and CI in terms of: Findings, Recommendations and Suggestions

Are Release 2 LCO Review Entry Criteria Met? 1.Is Release 1 sufficiently mature to support R2 Inception Phase? a.Are IOC and PRR artifacts for R1 provided and adequate to support R2 Inception Phase? b.Most of this question should be answered by the Release 1 PRR 2.Are Release 2 LCO artifacts provided and adequate? Artifact SetContent ManagementSystem Life Cycle Plan Risk Register Elaboration Execution Plan RequirementsUse cases (mature) User workflows (candidate) System and subsystem requirements (candidate) DesignArchitecture Specification (candidate) Technology List (baselined) Prototype Reports ImplementationNone DeploymentNone

Are Release 2 LCO Review Exit Criteria Satisfactorily Met? 1.Are the use cases understood by the stakeholders, and do they provide a complete description of the release scope? 2.Are the core user workflows understood and agreed to by the stakeholders? 3.Are the candidate requirements understood by the stakeholders, and do they cover the critical use cases? 4.Are the critical risks identified, and have they been mitigated through exploratory prototypes? 5.Are the candidate architectures viable as demonstrated through analysis and prototyping? 6.Is the Elaboration phase plan credible? (are requirements, use cases, architecture and plans linked and traceable?)

Are Release 2 LCO Review Exit Criteria Satisfactorily Met? Additionally, the LCO panel will consider the following specific questions related to a successful Release 2 completion: Is this a viable User Interface strategy, team and approach? Have all of the applicable interfaces been identified? Have these interfaces been appropriately characterized for this stage? Have R1 interfaces been adequately proven to support L2 start?

Actions from R1 LCA Findings, Recommendations and Suggestions Were items satisfactorily addressed from Release 1 reviews, especially Release 1 LCA? – Some of the items could have a major impact on CI’s ability to proceed if they have not been addressed

Review Board Guidance to CI Delivered as both verbal out brief and written report Guidance categories to CI: – Findings, recommendations, suggestions Summary Conclusions will be one of these: 1.Proceed to R2 LCA 2.Proceed to R2 LCA with actions/liens and work off schedule 3.Delay R2 identified activities until key findings resolved May require delta LCO 4.Repeat LCO

LCO Board Summary Stay focused on topic Observe protocol We will persevere “We are here to help” Let’s go