Project Performance International founder and principal Mr. Robert Halligan often performs speaking engagements in the fields of project performance and process improvement. A menu of short tutorials intended for evening delivery is also available. The tutorials include:

Functional Analysis - Why and How - Applications in the Problem and Solution Domains

Design Iteration Using Effectiveness Analysis

Principles of the Engineering of Systems

Ten Don'ts in Engineering Decision Making

Systems Engineering - the Next Ten Years

Twelve Issues in Systems Engineering

This presentation was delivered at the 2007 International Symposium of the International Council on Systems Engineering (INCOSE) in San Diego by PPI Managing Director and systems engineering guru Robert Halligan. The full text of this presentation, which challenges some conventional wisdoms, is not publicly available; this download contains the supporting graphics.

Getting the Most out of "Work" Breakdown Structure

Work Breakdown Structure (WBS) can be a powerful aid in effectively managing projects. But WBS (or as Robert prefers to call it, "Project Breakdown Structure - PBS", is also easily misunderstood and misapplied. Robert's coverage of the subject, in an interactive style, will incude:
  • why WBS must not be just a breakdown of work
  • essential principles in adopting WBS as a management tool
  • failsafe rules for constructing effective WBS
  • relationships to other structures useful in project/engineering

Management: System Breakdown Structure (SBS, Cost Breakdown Structure (CBS), Organissational Breakdown Structure (OBS), Specification Breakdown Structure (Specification Tree)

  • application of WBS to costing, scheduling, definition, risk  analysis, measurement, reporting, organisational design, and control.

Is it beneficial to apply the "classic" systems engineering approach in the commercial/industrial systems engineering world?

Getting the Most from Integrated Product Teams

A Schema for Types of Requirements

Robert will describe a schema for the types of requirements (states and modes, functional, performance, external interface, environmental, resource, physical, other qualities, and design), that he has used for many years, with considerable success. He will precisely define each type, and describe the significance of each type to each of the three roles of requirements analyst, requirements specification writer, and designer. Differences for physical systems, software and services will be discussed. Robert will then illustrate a proven-effective strategy for the automation of requirements specification production based on a six part classification scheme per requirement (actor ? primary and secondary, and for each actor, primary and secondary requirements types). He will then illustrate the unambiguous mapping into specification structure that is available.

How can we measure requirements quality, and why would we want to?

In this tutorial, Robert will explain why a requirements quality metric is one of the most valuable metrics in controlling and improving the outcomes of technical projects. He will go on to explain how to measure the quality of a set of specified requirements. The tutorial includes an interactive workshop in which you will exercise an effective method of measuring requirements quality. You are invited to bring your own requirements! Or you may select from Robert?s offerings.

Knowing What Needs to be Done is Only a Small Start! - Systems Engineering Process Improvement

SysML - Warts and All

OCD and CONOPS - Two Very Different Beasts

How to Prepare Great Requirements Specifications

Requirements are Design

A Systems Approach to Software Engineering

Twenty Million Systems Engineers; Twenty Thousand Who Know They Are

 

Click Here to Contact Robert Halligan