In today’s project management paradigms, cost and schedule tracking tools can measure the amount of:

  1. money that has actually been spent, and
  2. work that has actually has been done.

However, cost and schedule tracking tools cannot:

  1. answer “How much of my project has been completed?” (Kasser, 1997), or
  2. identify potential technical problems in near real-time to be able to mitigate them.

This blog improves project management and systems engineering by providing a way to measure technical progress of a project and identify potential problems in near real-time to mitigate problems before they occur as shown in the accompanying video at

Simplistic approaches to tracking the technical progress of realizing the requirements or features of a new product through the design and construction stages of the System Development Process (SDP) such as Feature Driven Development (FDD) (Palmer and Felsing, 2002) can inform about the state of the realization activities. However they cannot be used to estimate the degree of completion of the project since each requirement or feature has a different level of complexity and takes a different amount of effort to realize. The need exists for a measurement approach that can:

  • summarize detailed information for display in one or two charts, and
  • readily relate this information to the existing cost and schedule.

The Categorized Requirements in Process (CRIP) approach (Kasser, 1999) presented in the video [] meets the need by looking at the change in the state of a summary of the realization activities which convert requirements into systems during the SDP from several perspectives. Further explanations can be found in my book “Perceptions of Systems Engineering” (Kasser, 2015), Chapter 19.