IV&V Program NASA IV&V for the New York City E911 Program Michael Facemire, NASA Shirley Savarino, TASC Hendrik Strydom, OCEC.

Slides:



Advertisements
Similar presentations
Abstract To provide efficient and effective access to enterprise information that meets stakeholder needs and supports mission success, NASA is implementing.
Advertisements

12 August 2004 Strategic Alignment By Maria Rojas.
Page 1 Capability Business Benefit Business Risk KEYBA Capabilities: Benefits V Risks Facilitation of Decision making Getting the right people together.
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Course: e-Governance Project Lifecycle Day 1
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Continuous Value Enhancement Process
Program Management Overview (An Introduction)
Object-oriented Analysis and Design
Information Systems In The Enterprise
Alliance for Strategic Technology (AST) SUNY Business Intelligence Initiative January 8, 2009.
COMP 350: Object Oriented Analysis and Design Lecture 2
B&O Committee May 2015 iTRAK - Change Management An Agency Adapting to Change.
Project Management Methodology (PMM)
Sylnovie Merchant, Ph.D MIS 210 Fall 2004 Lecture 1: The Systems Analyst Project Management MIS 210 Information Systems I.
project management office(PMO)
Basel Accord IITRANSITIONSERVICES Business Integration Support FCM Management Limited Paris New York Toronto.
The Evergreen, Background, Methodology and IT Service Management Model
You will be responsible for professional and technical work related to network and telecommunications solutions (Local Area Network/ Wireless, Wide Area.
Object-Oriented Analysis and Design Iterative Development and the Unified Process.
THE REGIONAL MUNICIPALITY OF YORK Information Technology Strategy & 5 Year Plan.
Twelfth Lecture Hour 10:30 – 11:20 am, Saturday, September 15 Software Management Disciplines Project Organization and Responsibilities (from Part III,
Introduction PMBOK® © Whizlabs.
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
Best Systems Engineering Products Drive CMMI NDIA 6th Annual Systems Engineering Supportability & Interoperability Conference October 21, 2003 Dr. Tom.
VALUE BASED SYSTEMS ENGINEERING THE VALUE ADDED PATH FORWARD Joseph Maley October 8, 2015.
December 14, 2011/Office of the NIH CIO Operational Analysis – What Does It Mean To The Project Manager? NIH Project Management Community of Excellence.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Eighth Hour Lecture 7:30 – 8:20 pm, Thursday, September 13 Workflows of the Process (from Chapter 8 of Royce’ book)
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Georgia Institute of Technology CS 4320 Fall 2003.
Enterprise Architecture, Enterprise Data Management, and Data Standardization Efforts at the U.S. Department of Education May 2006 Joe Rose, Chief Architect.
Project Management For the Non Project Manager 1.
Catawba County Board of Commissioners Retreat June 11, 2007 It is a great time to be an innovator 2007 Technology Strategic Plan *
Last Updated 1/17/02 1 Business Drivers Guiding Portal Evolution Portals Integrate web-based systems to increase productivity and reduce.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Strategies for Knowledge Management Success SCP Best Practices Showcase March 18, 2004.
1 Advanced Collaborative Environments Kris Brown Carmel Conaty Johnny Medina.
Going beyond business as usual the pci group Integrated Project & Portfolio Management Microsoft Project Server 2003 – ProSight Portfolios Interface Presented.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Statewide Radio Feasibility Study (SIRN) Presented by Tom Harris SIEC Chair Mike Ressler.
Operational and Postimplementation
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Introduction To Project Management Unit 1. What is a Project? temporary endeavor undertaken to create a unique product, service, or result.
Software Engineering (CSI 321) Software Process: A Generic View 1.
U.S. Department of Agriculture eGovernment Program Smart Choice Pre-Select Phase Transition September 2002.
The Software Engineering Process Discussion Slides.
July 2003 At A Glance The GMSEC provides efficient and enabling GSFC mission services and products for the next decade. Benefits Establishes a Single Strategic.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Managing Multiple Projects Steve Westerman California Department of Motor Vehicles Steve Young Mathtech, Inc.
Establishing (or Enhancing) PMO Effectiveness Nicolle Goldman, PMP March 28, 2007.
Plan for Application Consolidation. Successful application consolidation relies on assessment of the application portfolio to determine the best candidates.
IV&V Facility 7/28/20041 IV&V in NASA Pre-Solicitation Conference/ Industry Day NASA IV&V FACILITY July 28, 2004.
Project Office Effectiveness Educating the Organization on How to Use a PMO February 22 nd, 2006.
Phase-1: Prepare for the Change Why stepping back and preparing for the change is so important to successful adoption: Uniform and effective change adoption.
TK2023 Object-Oriented Software Engineering
Mgt Project Portfolio Management and the PMO Module 8 - Fundamentals of the Program Management Office Dr. Alan C. Maltz Howe School of Technology.
Identify the Risk of Not Doing BA
Software Engineering (CSI 321)
Harvard CRM Service Strategy
COMP 350: Object Oriented Analysis and Design Lecture 2
2018 Real Cisco Dumps IT-Dumps
Enterprise Architecture at Penn State
The Methodology for Business Transformation
Presentation transcript:

IV&V Program NASA IV&V for the New York City E911 Program Michael Facemire, NASA Shirley Savarino, TASC Hendrik Strydom, OCEC

IV&V Program New York City Emergency Communications Transformation Program (ECTP) Multi-billion dollar program to improve largest 911 system in the United States, handling approximately 11 million calls per year. –Advance public safety agency interoperability and coordination. –Reduce call-processing and 911 response time. –Increase system resiliency and technical redundancy. –Improve safety of the City’s first responders. ECTP Phase 1 delivered new Public Safety Answering Center (PSAC1) in Brooklyn January Primarily co-located operations and integrated new telephony system. NASA IV&V supporting ECTP Phase 2 (ECTP2). –Redundant PSAC in Bronx, PSAC2. Cut over planned for December –Major technology upgrades to networks, radios, computer aided dispatch (CAD), and Logging and Recording (L&R), including retrofit of selected subsystems in PSAC1. 2

IV&V Program NASA and the ECTP Program NASA ECTP IV&V is not typical NASA IV&V. –Large IV&V effort; 19 full-time personnel. –Reimbursable project with non-federal customer in very political environment. –Systems/System-of-Systems IV&V vs. software IV&V. Heavy COTS content, configured for application. –NASA IV&V started in middle of ECTP elaboration phase (aka., design). NASA IV&V is not typical New York City IV&V. Focus on technical aspects and success vs. contractual compliance of deliverables. ECTP IV&V is advancing NASA Mission and Vision and Program strategic goals. –Applying NASA achievements and lessons learned to overcome complex challenges to benefit humankind. –Driving advances in NASA IV&V and industry systems and software engineering disciplines. –Ensuring NASA IV&V Program capabilities and services are state-of-the- practice. 3

IV&V Program ECTP IV&V Contributions and Accomplishments NASA IV&V applies and promotes NASA engineering discipline and rigor on ECTP –Improved ECTP systems engineering plans and products which serve as a basis for system elaboration, construction, and transition. –Increased and improved emphasis on system and integration aspects. NASA IV&V continues to provide NYC with detailed engineering data and analysis allowing the City to better manage the program, increasing the likelihood of success. –Providing high-quality, evidence-based assurance findings enabling the City and System Integrator to achieve high quality standards in the delivered products. –NASA TIMs are being used as a tool by the City to better inform approval of vendor deliverables. –ECTP and City executives have acknowledged NASA’s valuable contributions. 4

IV&V Program Reflections on Our First Year Efficient and effective application of standard IV&V analyses processes resulted in quick contributions. Over the past year, our team has augmented core software/systems IV&V skill sets to address Emergency Management and program-level systems engineering, integration, and plans. Agility was/is very important. –Demanding schedule with staggered development across the subsystems. –Multiple stakeholders with diverse needs in a rapidly advancing technology environment. –Short City approval period for deliverables and need for timely City oversight of vendors. –Visibility across multiple City agencies and up to the Mayoral level. 5

IV&V Program ECTP Retrospective: What did we do well? 1.Significant Focus on Technical Quality. 2.Emphasis on Building Effective Relationships. 3.High Cadence of Reporting and Communication – No Surprises. 4.Right Skill Sets and Robust Management. 6

IV&V Program Things We are Glad We Did 1.Significant Focus on Technical Quality. –This was a priority by everyone (OCEC and NASA). –NASA IV&V Team added additional rigor and review to processes to ensure quality TIMs and risks. –Existing NASA processes provided solid basis for analysis methods and reporting of findings. Adaptation when needed to meet ECTP needs. –Emphasis on understanding user needs and use of strong technical reference. 2.Emphasis on Building Effective Relationships. –Became an agent for OCEC while remaining true to NASA IV&V Values – time invested by all parties to socialize NASA IV&V with OCEC/ECTP and with stakeholders including the Agencies, Systems Integrator, City Hall. –Onsite team and access to artifacts supported technical analysis. Workflows established early. –On-site team with Contractor Lead and OCEC staff enabled quick decisions. NASA PM made monthly trips and NASA management quarterly. –OCEC made available Technology and SME staff when requested, as well as access to System Integrator. 7

IV&V Program 3.High Cadence of Reporting and Communications – No Surprises. –Heavy use of metrics to transform data to information, as well as providing actionable recommendations facilitated issue/risk resolution. –Developed dashboard which reported status to executives. Biweekly tagups with set agenda established/maintained cadence at working level. –Managed expectations: NASA Team defined specific work instructions at start of task, communicated tasks and anticipated benefits. OCEC kept NASA informed of ongoing activities and decision points. 4.Right Skill Sets and Robust Management. –Used solid core of IV&V expertise augmented with needed domain skills. Domain skills in emergency management technologies (e.g., Radios, Networks, Computer Aided Dispatch) and Systems Architecture and Systems Test and Deployment. Used reach-back within both NASA and TASC as needed. –Selected “agile-like” techniques for team management. Utilized sub-teams that blended skill sets (domain, IV&V knowledge, experience) and location (onsite, offsite). Detailed work planning in cycles of 6-12 weeks. 8 Things We are Glad We Did, Continued…

IV&V Program 9 Questions and Discussion