Author: Arlene Minkiewicz

The conundrum around software estimation is that at the point at which initial estimates are expected, the information about the project is often incomplete, and software intensive which increases the estimate complexity, since software is hugely malleable. Being “agile” makes an estimate easy, if your team is actually agile.

Software project failures coupled with rapidly changing business needs are forcing organizations to revisit the way they go about building software. Agile development has emerged as one possible solution to the woes of the software industry.

The Internet of Things, the Network of Things, enabling technologies and implementations are changing the way people live and work.

Agile development requires a mind shift on the part of both the developers and consumers of software to accept the reality that things will change over the course of the project.

When employing agile development practices, an organization effectively embarks on a new software development project with every iteration. The tenets of agile require frequent releases and frequent customer reviews. These reviews often trigger re-prioritization and re-estimation.