This paper evaluates the impact of nonessential
minimum marketable features modules (NMMF) and
nonessential architectural elements (NAEs) on software
projects; shows that the value-creation path of these selfcontained
software units may be quite different from that
of essential software units; and discusses the impact of early
NMMF and NAE identification on the value of software
projects to business and the deployment of business strategy.
Moreover, the paper demonstrates that the existence of
flexible precedence relations among MMFs and AEs may
also be exploited to further increase the value of software
development initiatives