In the Beginning . . .

In days of yore, systems development projects were front ended with laborious requirements engineering and design tasks.  This made sense then because development was labor-intensive, time-consuming and expensive.  Changes to the scope or design of a solution mid-development increased the likelihood of errors and incremental time and expense.  In recognition of this, traditional Waterfall project management was applied, which created impediments to modifying the product definition once its development had begun.  Changes were strenuously resisted. Continue reading →