SoS Process, Acquisition, Management Critical Success Factors Workshop Jo Ann Lane, Richard Turner, USC.

Slides:



Advertisements
Similar presentations
PROJECT RISK MANAGEMENT
Advertisements

State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Course: e-Governance Project Lifecycle Day 1
W5HH Principle As applied to Software Projects
Systems Engineering in a System of Systems Context
1 Independent Verification and Validation Current Status, Challenges, and Research Opportunities Dan McCaugherty IV&V Program Manager Titan Systems Corporation.
IT Governance Navigating for Value Michael Vitale 6 May 2003 CIO Conference Steering the Enterprise Through Stormy Seas Image source: Access2000.
The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.
University of Southern California Center for Systems and Software Engineering USC CSSE Research Overview Barry Boehm Sue Koolmanojwong Jo Ann Lane Nupul.
University of Southern California Center for Systems and Software Engineering Issues and Recommendations Emanating from the Management Issues Group of.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
University of Southern California Center for Systems and Software Engineering Integrating Systems and Software Engineering (IS&SE) with the Incremental.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Process Synchronization Workshop Summary Report Jo Ann Lane University of Southern California Center for Software Engineering.
Remedy, a BMC Software company Change Management Maximize Speed and Minimize Risk in the Change Process.
Stoimen Stoimenov QA Engineer QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Introduction to Project Management The Basics for Sustainability Management Students.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
CSR Project, 3 cr. Corporate Responsibility, C-module (15 cr.) or free-choise studies Introduction to Corporate responsibility, 1,5-3 cr. (depending on.
What is Business Analysis Planning & Monitoring?
CMMI Course Summary CMMI course Module 9..
PRM 702 Project Risk Management Lecture #28
PMI Knowledge Areas Risk Management.
CPTE 209 Software Engineering Summary and Review.
Software Project Management Introduction to Project Management.
© 2001 by Carnegie Mellon University PSM-1 OCTAVE SM : Senior Management Briefing Software Engineering Institute Carnegie Mellon University Pittsburgh,
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
Quick Recap Monitoring and Controlling. Phases of Quality Assurance Acceptance sampling Process control Continuous improvement Inspection before/after.
1 Project Risk Management Project Risk Management Dr. Said Abu Jalala.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
IT Requirements Management Balancing Needs and Expectations.
Software Project Management
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.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Develop Project Charter
Accounts Chamber of the Russian Federation Approaches to comprehensive project and program audit in the Accounts Chamber of the Russian Federation.
1 | 2010 Lecture 3: Project processes. Covered in this lecture Project processes Project Planning (PP) Project Assessment & Control (PAC) Risk Management.
Project Portfolio Management Business Priorities Presentation.
Introducing Project Management Update December 2011.
SOFTWARE PROJECT MANAGEMENT
Project Risk Management Planning Stage
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
1 IT Project Management, Project Failure and Success  Introduction  Projects operate in a broad organizational environment.  Project managers need to.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Stand Up Comedy Project/Product Management
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
1 Text Layout Introduction (1-4) Team Skill 1 – Analyzing the problem (5-7) Team Skill 2 – Understanding User and Stakeholder Needs (8-13) Team Skill 3.
Technology Needs Assessments under GEF Enabling Activities “Top Ups” UNFCCC/UNDP Expert Meeting on Methodologies for Technology Needs Assessments
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
1 Project Management C13PM Session 2 Project Initiation & Definition Russell Taylor Business Department Staff Workroom
University of Southern California Center for Systems and Software Engineering Aug. 26, 2010 © USC-CSE Page 1 A Winsor Brown CS 577a Lecture Fall.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Advanced Software Engineering Dr. Cheng
Software Risk Management
Fundamentals of Information Systems, Sixth Edition
By Jeff Burklo, Director
CIS12-3 IT Project Management
Chapter 8 Software Evolution.
Presentation transcript:

SoS Process, Acquisition, Management Critical Success Factors Workshop Jo Ann Lane, Richard Turner, USC Center for Systems & Software Engineering October 26, 2006

2 Workshop Guidelines  Product: briefing, preferably with notes  Topics should include: –Most critical success factors in each area –Current best practices for addressing them –Areas for further research  Rated 0-10 on value and difficulty of research

3 SoS Process Critical Success Factors: Technical  Technical –Complexity management – including adequate and appropriate recording for ver/val methods –Scope as a variable and negotiable  Identify “good enough” early –Design for graceful degradation (architecture...move) –Plan and budget for evolution –Engineering processes that focus on capabilities/outcomes rather than requirements (research opportunity) –Avoidance of “False precision” - honesty about variance –Ensure that decisions support SoS, not just component system –Effective/efficient baseline management of SoS

4 SoS Process Critical Success Factors: Technical (continued)  Technical –Limit negative impact of changes to baselines out of locus of control (architecture)  Standards, guidelines, conventions – prevent lack of compatability –Budget and Plan for Continuous integration and degrees of continuous V&V –Proactive future interface management (goes along with requirements management) –C3ISR approach  Recon at boundaries  Awareness of environmental changes  Technical ISR of competition

5 SoS Process Critical Success Factors: Management  Management –Plan for evolution –Deliver capability quickly (plan for) –Continuous course correction  Steering verses plan-and-track leadership style –Managing velocity and acceleration of technical work  Rather than position (tracks instead of dots) –Identify “good enough” early –Avoidance of “False precision” - honesty about variance –Continuously “Right size” governance model –Effective/efficient baseline management of SoS –How to identify impact of proposed changes  Understanding business process re-engineering  Initial and revised/future

6 SoS Process Critical Success Factors: Management (continued)  Management –Ability to plan for unintended consequences  How to handle contingency  Add margin/empty spiral development cycles  Accept that not everything can be pre-planned and not fill schedule with known-knowns –Business ISR of competition –Metrics and measurement processes that support SoS objectives  Avoid too much detail or sub-optimization –Progress measured by operational capabilities –Managing compound risks  Compound risk management and mitigation  A “Risk of Risks”

7 SoS Process Critical Success Factors: People/Organizational  People –SoS Stakeholder processes that  Actively Balance Stakeholders  Maintain Stakeholder Involvement and Consensus  Identify, establish, and involve community  Identify the right stakeholders for each decision –How to do without CRACK representatives from all systems and stakeholders (use surrogate ones?)  Processes that still operate with lacking or inadequate levels of representation –Communicating and coordinating up and down supplier chain (robust and speedy) –Incentive structures

8 SoS Process Critical Success Factors: Acquisition and Point of View  Acquisition –Continuously “Right size” governance model –Scope as a variable and negotiable –Plan for evolution –Appropriate contracting vehicles  Point of View –Need to differentiate issues/process needs between a system of systems and addressing a collection of component systems –In SoS context, software properties may need to be recognized as more important than the hardware components –Acknowledge that process is a learning process (goes with scoping, governance models)

9 Best Practices  Technical –Architecture reviews of trade space results –WinWin to prioritize requirements –Spiral incremental commitment model to plan and budget for evolution [Two types of evolution(forseeable evolution, unanticipated changes)] –GQM or PSM –Baseline management automation –Continuous Integration

10 Best Practices (continued)  Management –Incremental Planning –Independent expert reviews –Add margin/empty spiral development cycles –C3ISR approach  Recon at boundaries  Awareness of environmental changes  ISR of competition  Test Driven Development / Scenario Based Testing –Risk identification templates  People –IPPD –Use surrogate representatives –Intranet portal technology –Collaboration tools –Incentive templates  Acquisition –Re-evaluation at the end of each “increment” (include in retrospective)

11 SoS Process Critical Success Factors: Areas for further research A.Engineering processes that focus on capabilities/outcomes rather than requirements B.How to fix acquisition process – current process not used right C.Risk identification templates that can succeed in a SoS context D.How to do without CRACK representatives from all systems and stakeholders E.Meta analysis of acquisition literature F.Methods for managing steering based approach G.Incentive structures H.Rapid change management techniques (acquisition and technical POV) I.Tools for impact analysis J.Fault tree /FEMA analysis to determine probability of success for complex programs K.Modelling and simulation for SoS programs L.Cost and schedule estimation tools M.Identification and evaluation in complex SoS of best practices in this environment Rate 0-10 on value and difficulty of research…

12 Research Priorities

Backup Charts/Additional Information

Success-Related Factors from Presentations  Boehm: Challenges of SoS –Complexity –Dynamism –Emergence –Build-to-spec processes, contracts infeasible  Dalrymple: Success Critical Factors for SoS –Baseline Management (processes) –Organizational Efficiency –Concurrency Management (processes) –Feasibility Assessment  Latimer: –Need case studies to support theory and process dev.

Success-Related Factors from Presentations (continued)  Nielsen: SoS Issues –Constituents (a.k.a. stakeholders) –Purpose –Control –Requirements –Ownership –Boundaries –Visibility  Pyster: Critical Success Factors –Team organization (integrated single team) –Communications –Standards Compliance –Simulation and Layered Architectures

Success-Related Factors from Presentations (continued)  Royce: Critical Success Factors (four patterns of success) –Scope management –Process management –Progress management –Quality management  Turner: Taglines –“Pay me now or pay me later” –“What’s my line?” –“Who’s on first?” –“Truth or Consequences?” –“What, me worry?”

17 Definitions  SoS Process –Risk management  Identify risks process is different?  Mitigation –Needs to deal with emergent stuff –SOS process needs to look like process we preach; ability to change is important –Don't know requirements of emergent systems  Acquisition  Management