New projects are very exciting. Developers want to be able to start delivering value to stakeholders immediately and stakeholders want to be able to see results as quick as possible. However, if teams rush to implement features in their first sprint they can run into trouble quickly. Teams that don't have a good roadmap in place realize they've been going down the wrong path a few months too late, resulting in rework, frustration, and loss of trust.

In order to be successful, you must:
• Master fundamental architecture and engineering fundamentals
• Understand web app architecture
• Think reactively

Router-first architecture is designed to encourage teams to ask the hard questions early, build a roadmap and then iterate over a solution.

Router-first:
• Enforces high-level thinking,
• Ensures consensus on features, before coding starts,
• Accounts for source code and team growth,
• Keeps engineering overhead low.

In addition, the router-first approach to Single Page Application (SPA) architecture enables developers to start small, with a decoupled and lazy-loaded architecture, giving them the option to stay small or scale while achieving sub-second first meaningful paints.

I will share real-world statistics about how this methodology helped my team.

These concepts are demonstrated through my Lemon Mart app on GitHub and in my book: Angular for Enterprise-Ready Web Applications, Packt Publishing.