In our industry, applications and services are often rebuilt. Companies frequently find themselves in large, long-lasting migration projects, sometimes because management decides to switch technologies, engineers declare systems end-of-life, or the scope has evolved so much that a rebuild becomes necessary.
While these are all valid reasons to begin such a project, rebuilds often take longer than expected. As timelines slip, the business grows impatient, eager to release new features and see progress.
With well-defined goals, a clear scope, prioritized work, and managed expectations across all stakeholders, a rebuild can succeed. Clarifying the trade-offs between gains, costs, and risks is essential. Whether you're starting, continuing, or even deciding to stop a rebuild.
In this talk, I’ll share key insights, do’s and don’ts, and lessons from multiple rebuild projects, offering practical guidance for tackling your next rebuild challenge