One of the touted benefits of agile development is better early information on project problems and issues. This early detection enables management — project and otherwise — to take adaptive actions. However, early problem detection comes with its own problem — discomfort with early information. In waterfall projects management and staff are used to getting information about problems late. This leads to a perception that projects are typically on-track until late in the lifecycle. In fact, the lack of working software until late in the project provides a false sense of progress. Because coding and testing come late in waterfall projects, they “appear” to be in good shape — until the end when the project …
Daily Archives: Aug 4, 2009
A primary function of IT architecture is managing change. This change happens at varying rates in and between levels of abstraction (think of wind moving at different speeds at different altitudes). So we can think of “horizontal” change — change in time within a particular level — as well as “vertical change” — the relationship between one level and another. A robust IT architecture maximizes the potential for improvements in all levels while minimizing the negative impact of change between levels. Sometimes IT architecture emerges through acquisition. In the old days, vendors imposed architecture that was bundled with their software development products. (Why would anyone have otherwise considered something like systems application architecture [SAA]?) As …


Recent Comments