Trying to connect WBSs with people and phases Relevant questions to my work: How the re 8 -planning will affect the work in progress? Priorities to capture.

Slides:

Advertisements

Similar presentations

Project Management 6e..

Advertisements

3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,

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

Write Your Project Title Here VU Logo Here Group Members Introduction Write your group members introduction here with names and VU Id.

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)

Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.

Science Group: Status, Plans, and Issues Claire Max Liz McGrath August 19, 2008.

© ABB AB, Corporate Research - 1 5/19/2015 abb Project Breakdown Structure Creation.

Defining the Project CHAPTER FOUR Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.

NGAO Controls Team Meeting August 29, 2008 Erik Johansson.

1 NGAO Instrumentation Studies Overview By Sean Adkins November 14, 2006.

Trying to connect WBSs with people and phases Relevant questions to my work: How the realistic NGAO strategies will/should affect the work in progress?

NGAO Control Systems Group Status, Plans & Issues NGAO Team Meeting August 19, 2008 Erik Johansson Jimmy Johnson, Doug Morrison, Ed Wetherell.

NGAO System Design: AO System (WBS 3.2) & Laser Facility (WBS 3.3) Design Inputs & Outputs Peter Wizinowich NGAO Team Meeting #9 August 24, 2007.

What is a project? Project Management Institute definition

Science Operations Update NGAO - Meeting 11 D. Le Mignant, E. McGrath & C. Max W. M. Keck Observatory 11/05/2007.

Planning “Science Operations” tasks for the PD phase NGAO PD Phase D. Le Mignant W. M. Keck Observatory 08/19/2008.

Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.

WBS & AO Controls Jason Chin, Don Gavel, Erik Johansson, Mark Reinig Design Meeting (Team meeting #10) Sept 17 th, 2007.

Science Operations Replan NGAO - Meeting 6 D. Le Mignant W. M. Keck Observatory 04/25/2007.

Information Systems Development Lecture 2: the idea of the Life Cycle.

Science Operations Plan NGAO - Meeting 10 D. Le Mignant W. M. Keck Observatory 09/17/2007.

NGAO interface control documents: Christopher Neyman W. M. Keck Observatory Keck NGAO PD phase Meeting #6 March 19, 2007 Videoconference.

Info1409 De Montfort University1 Requirements Modelling Systems Analysis & Design Academic Year 2008/9 Info 1409 Lecture 7.

NGAO Team Meeting Management Peter Wizinowich May 26, 2009.

Design Team Report: AO Operational Tools (aka Acquisition and Diagnostics) Christopher Neyman W. M. Keck Observatory (for the Operational tools team) Keck.

System Architecture WBS 3.1 Mid-Year Replan Richard Dekany NGAO Team Meeting #6 April 25-26, 2007 UCSC.

Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.

Software engineering Olli Alm Lecture 2: requirements, modelling & representation.

Design Team Report: AO Operational Tools (aka Acquisition and Diagnostics) Christopher Neyman W. M. Keck Observatory (for the Operational tools team) Keck.

This work is licensed under a Creative Commons Attribution 3.0 Unported LicenseCreative Commons Attribution 3.0 Unported License (CC-BY). Project Management.

Task Analysis is Part of Planning Once we have completed planning on the deliverables and contents of the deliverables, we need to plan out “how to accomplish”

Task Analysis is Part of Planning Once we have completed our plan on what to deliver and the contents of deliverables (via requirements), we need to: plan.

Object-Oriented Analysis and Design

What is Business Analysis Planning & Monitoring?

RUP Requirements RUP Artifacts and Deliverables

Software Engineering CS B Prof. George Heineman.

Chapter 4 Defining the Project.

Ivan Dontsov, Andy Phenix, Maureen Rottschaefer. Project Outline “The primary objective of this OMSE 2012 Practicum Project is to extend and refine the.

IIA_Tampa_ Beth Breier, City of Tallahassee1 IT Auditing in the Small Audit Shop Beth Breier, CPA, CISA City of Tallahassee

CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project Planning.

Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.

Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.

Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.

McGraw-Hill/IrwinCopyright © 2008 by The McGraw-Hill Companies, Inc. All Rights Reserved. Defining the Project Chapter 4.

Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.

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.

Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.

Rational Unified Process Fundamentals Module 3: Disciplines I.

11/24/2015Dr. SASTRY-PROJ SOFTWARE PROJECT MANAGEMENT By Dr. M V S PERI SASTRY. B.E,Ph.D.

T Project Review RoadRunners [IM1] Iteration

Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.

Project Task Planning 1 Concepts and Definitions Work Breakdown Structures.

Proposal: staged delivery of Scheduler and OpSim V1 (2016) meet most of the SRD requirements – Deliver a system that can be extended with an improved scheduler.

Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.

State of Georgia Release Management Training

Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.

Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.

1 1. Systems and Software Development 1.1 The Systems Life Cycle.

Monica Gloudemans Ekaterina Schwartz Gloudemans/Schwartz ACS 560 CMAP.

Paul Alexander1 DS3 Deliverable Status 4 th SKADS Workshop, Lisbon, 2-3 October 2008 DS3 Deliverables Review.

IT-301 Project Management I: Unit 4: Cost Management.

BSA 385 Week 3 Individual Assignment Frequent Shopper Program Part 2 Check this A+ tutorial guideline at

Scope Planning.

Architecture Concept Documents

Project Title Presented By Student1 name - Roll no

UML: Unified modeling language

Proposed Software Development Process

Asset Acquisition through Direct Capitalization

Web Service Security support in the SSE Toolbox

Presentation transcript:

Trying to connect WBSs with people and phases Relevant questions to my work: How the re 8 -planning will affect the work in progress? Priorities to capture observing scenarios? What are the complementarities between some of the deliverables? What are the overlap between some of the WBS? (see slides) Some expectations: -Agree on outlines & leads for main documents -Agree on leads for the WBS (focus on need for overlap/coordination) -Flow diagram of activities with identified leads

NGAO sequences definitions document OCR document: Observing scenarios Planning User Observatory Observing User Observatory Post-observing Uses cases planning tools acquisition sequences calibrations sequences observing sequences Observing support and technical operations operation procedures WBS 3.2 WBS 3.4.4: Science observing planning and execution User Interfaces design WBS WBS WBS (new?) science requirements WBS 3.1 Re-planning Phased approach? (New) performance budgets WBS users inputs documentactivityWBS name WBS 3.1.2

NGAO sequences definitions document OCR document: Observing scenarios Planning User Observatory Observing User Observatory Post-observing Uses cases planning tools acquisition sequences calibrations sequences observing sequences Observing support and technical operations operation procedures WBS 3.2 WBS 3.4.4: WBS 3.1.2: Science observing planning and execution MCS sequences WBS WBS WBS User Interfaces WBS WBS WBS documentactivityWBS name Where should we document the sequence definitions? What is the difference between OCR and the NGAO SDD?

NGAO sequences definitions document OCR document: Observing scenarios Planning User Observatory Observing User Observatory Post-observing Uses cases planning tools acquisition sequences calibrations sequences observing sequences Observing support and technical operations operation procedures WBS 3.2 WBS 3.4.4: MCS sequences WBS WBS WBS User Interfaces WBS WBS WBS NGAO software architecture document WBS External ICD WBS 3.5 Internal ICD WBS 3.6 ?? documentactivityWBS name

NGAO sequences definitions document WBS 3.4.4: MCS sequences WBS WBS WBS User Interfaces WBS WBS WBS NGAO software architecture document WBS External ICD WBS 3.5 Internal ICD WBS 3.6 documentactivityWBS name MCS infrastructure document WBS 6.1.1: UI infrastructure document WBS 6.2.1: Data server infrastructure WBS 6.4.1: Should some of these be captured in the ICD?