Articles tagged Agile product development

Guest Post by Howard M. Wiener (first posted on CERM ® RISK INSIGHTS – reposted here with permission)

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.

Guest Post by Howard M. Wiener (first posted on CERM ® RISK INSIGHTS – reposted here with permission)

In the previous articles in this series, we discussed the role that agile digital delivery capabilities plays in your company’s competitiveness and why rapid delivery is so important.  In this article, we will look at the many reasons that Agile adoptions frequently fail to deliver what companies expect and suggest some things that you should do to address them.

Guest Post by Howard Wiener (first posted on CERM ® RISK INSIGHTS – reposted here with permission)

In the previous article in this series, we discussed the difference between Agile and business agility and how Agile 2 addresses some of the omissions and failings of traditional Agile.  Both Agile and Agile 2 focus on accelerating digital development; however, the benefits of any Agile approach can be obviated if it is not implemented within an agile management structure.  Addressing execution issues, as Agile 2 does, will not be sufficient by itself to get you where you need to go.