JWST PRDS Project Mangement Case Study Jesse Doggett Project Engineer, ITEB/OED.

Slides:

Advertisements

Similar presentations

Process and Product Quality Assurance (PPQA)

Advertisements

Configuration Management

Quick Recap. Quick Recap The Project Plan Plan Your Work, then Work Your Plan.

Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.

Coherent Web Sustaining Engineering Plan 1. The Coherent Web team will: Utilize two-week development “sprints” to plan and track implementation activities.

Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?

Project Scope Management

Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)

Transformations at GPO: An Update on the Government Printing Office's Future Digital System George Barnum Coalition for Networked Information December.

ACS 567: Software Project Management Spring 2009 Instructor: Dr. John Tanik.

SE 555 Software Requirements & Specification Requirements Management.

What is a project? Project Management Institute definition

CS Integration Management (Part 6) Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009 Dr.Çağatay ÜNDEĞER Instructor Bilkent University,

Project Management Session 7

Chapter 5: Project Scope Management

Chapter 5: Project Scope Management J. S. Chou, P.E., PhD.

Project Scope Management

Project Scope Management J. S. Chou, P.E., PhD.

Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.

Michael Solomon Tugboat Software Managing the Software Development Process.

Release & Deployment ITIL Version 3

Advanced Project Management Project Plan Templates

EMBA Project Scope Management J. S. Chou, P.E., PhD.

Effective Methods for Software and Systems Integration

3 Dec 2003Market Operations Standing Committee1 Market Rule and Change Management Consultation Process John MacKenzie / Darren Finkbeiner / Ella Kokotsis,

Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?

Project Management Process Overview

The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.

Server Virtualization: Navy Network Operations Centers

Project Management Development & developers

SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.

DMS Systems Design Review 3

Project Scope Management Process

Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?

Configuration Management (managing change). Starter Questions... Which is more important?  stability  progress Why is change potentially dangerous?

Chapter 5 Defining and Managing Project and Product Scope Copyright 2012 John Wiley & Sons, Inc. 5-1.

BSBPMG502A Manage Project Scope 5.3 Create Work Breakdown Structure The process of sub dividing project deliverables and project work into smaller, more.

Chapter 5: Project Scope Management Information Technology Project Management.

1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.

Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.

ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.

Apply Project Scope Management Techniques Project Scope Processes – Part 2 Certificate IV in Project Management Qualification Code BSB41507 Unit.

© Mahindra Satyam 2009 Configuration Management QMS Training.

University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.

Release Management Configuration management. Release Management Goal Coordinate the processes through the project development life cycle Ensure the.

1 Advanced Project Management Project Plan Templates Ghazala Amin.

CLIC Project breakdown structure: organization, documentation and cost estimate Beam Instrumentation Workshop, June 2-3, 2009 CLIC Project breakdown structure:

Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.

Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.

©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 29 Slide 1 Configuration management.

Project Scope Management 1. 2 Learning Objectives Understand the elements that make good project scope management important. Explain the scope planning.

Regulatory Streamlining Task Force Update Discussion Item December 6, 2011 Board of County Commissioners.

Configuration Management- Basic Concepts. Agenda  Configuration Management process Overview  Process Stages  Planning & Setup  Control  Audit  Case.

Software Configuration Management n Art of coordinating SW development to minimize confusion n Software quality assurance (umbrella) activity n Set of.

© 2012 Václav Rajlich Software Engineering: The Current Practice Ch Conclusion of software change The last phase of software change The activities.

Apply Project Scope Management Techniques Project Scope Processes – Part 2 Week 4 Certificate IV in Project Management Qualification Code BSB41507.

Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.

NEM201 Week 4 Project Plan Create and complete outstanding items. 01. Front Cover 02. Document details 03. Scope Document 04. Technical Design 05. Creative.

Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.

JRA1 Meeting – 09/02/ Software Configuration Management and Integration EGEE is proposed as a project funded by the European Union under contract.

Chapter 7: Delivery, Installation, and Documentation Ronald J. Leach Copyright Ronald J. Leach, 1997, 2009, 2014,

Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.

Development Project Management Jim Kowalkowski. Outline Planning and managing software development – Definitions – Organizing schedule and work (overall.

Prof. Shrikant M. Harle.  The Project Life Cycle refers to a logical sequence of activities to accomplish the project’s goals or objectives.  Regardless.

BSBPMG502A Manage Project Scope Manage Project Scope Project Scope Processes Part 2 Diploma of Project Management Qualification Code BSB51507 Unit.

Software Configuration Management

Software and System Delivery

Configuration Management (managing change)

Release 3 Update December 2018.

Release 3 Update 9th January 2019.

Presentation transcript:

JWST PRDS Project Mangement Case Study Jesse Doggett Project Engineer, ITEB/OED

PMJC December 1 st, 2008JWST PRDS Case Study2 Outline What is the JWST PRDS? Stakeholders & Communication PRDS Formal Documents Planning and Subprojects Managing Change Quality

PMJC December 1 st, 2008JWST PRDS Case Study3 JWST PRDS Project Reference Database  Data Used to Operate the Space Craft PRDS Functional Components  Data Editor  Version Control  Dependency Checking  Change Management

PMJC December 1 st, 2008JWST PRDS Case Study4 JWST WBS (Work Breakdown Structure)

PMJC December 1 st, 2008JWST PRDS Case Study5 Stakeholders / Communication Stakeholders  NASA, NGST, Instrument Teams, ISIM, WFS&C, OSS, S&OC, PRDS Team Communication  Working Group Meetings  Status, Requirements, Interfaces, Design  Formal Documents  NGIN - JWST Restricted Web Site

PMJC December 1 st, 2008JWST PRDS Case Study6 Formal Documents Planning Documents  Architecture, Operations Concept, Requirements, Design Acceptance Documents  Test Plan  Test Results  Release Notes Other  Interface Control Document

PMJC December 1 st, 2008JWST PRDS Case Study7 Planning and Subprojects Basic Plan  Project broken up into phases or sub-projects.  Initial phase, implement baseline set of requirements.  Subsequent phases, requirements and bug fix implementations tracked in the Problem Report System Delivery Procedures  Minor Releases (bug fixes)  Notification, Delivered via Download  Major Releases (new requirements)  Formal Documents, Government Witness for Acceptance, Contracting Officer Delivers CD and Hard Documents

PMJC December 1 st, 2008JWST PRDS Case Study8 Managing Change Requirements  Informally Discussed in Working Group Meeting  Formal Request to Change Is Negotiated  New Requirements Document Approved and Updated  Important to Agree with Government on the Set of Requirements Personnel  Unplanned Departures Between First 2 Phases  Worked with Division to Identify Other Available Personnel  Slipped Schedule a Few Weeks

PMJC December 1 st, 2008JWST PRDS Case Study9 Certification Requirements ~20 New Requirements / No New Funding  Initially, Informed NASA We Can’t Set Completion Date  “Rolling Wave Planning”  Create and Refine Schedule and Plan  Design-As-We Go  Acceptance Test Only at the End

PMJC December 1 st, 2008JWST PRDS Case Study10 Quality Planning Quality Assurance  Ensures that activities are being performed to verify requirements are met.  Not formally done for PRDS Quality Control  Software Testing for PRDS  Perform Regression and Problem Report Testing  Weekly Reports  Results Driver Future Action  Document Failures  Determine If Immediate Fixes Required to Release