Premium
8.3.1 How to Achieve the Most Important Requirement
Author(s) -
Malotaux Niels
Publication year - 2009
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2009.tb01016.x
Subject(s) - computer science , risk analysis (engineering) , requirements management , work (physics) , product (mathematics) , requirements engineering , project management , process management , systems engineering , engineering , business , software , mathematics , mechanical engineering , geometry , programming language
The most important requirement for most projects is time ‐ time for completion . Still, most projects are late. Isn't it weird that projects apparently judge all other requirements more important than the requirement of time while time is one of the most important requirements? Both Project Management (responsible for the project) and Systems Engineering (responsible for the product) are responsible for the consequences of ignoring this important requirement. This paper describes why it is important to be on time, what measures we can take to make sure we are on time (and which often applied intuitive measures don't work!), and how we can use Evolutionary Planning techniques to make sure that we will be on time, or, if that is simply impossible, to take the consequence. These techniques allow us in the early stages of our project to predict and to optimize what will be ready at a certain time.