Traditional IT projects tend to take a “big bang” approach, in which the software is not released to users until it is finished. This means that it’s hard to tell whether the team building the system is on the right track until the end of the project. In contrast, an agile approach, which is at the heart of sense and respond, would address this problem by releasing small pieces of the system frequently and would do so from the earliest days of the project. This reduces the risk that the software team is off course, because it creates transparency. It becomes easy to see what the team is doing,
...more
