Have you ever been at the portion of the project where all your profit disappears and you’re wondering how you got there? You are not alone. Who should you blame – the client or the developers?
In this session, Chris will help us isolate the problem and offer solutions to prevent this in the future.
Most developers make changes to code without having clarity about how that change will impact the rest of their code. This becomes a bigger deal when working on longer or larger projects. The fine art of Impact Analysis is often the unspoken cousin of debugging. Just like debugging requires a systematic mind, Impact Analysis benefits from a disciplined approach.