What is the difference between Scrum and traditional project management?

Short answer: Aspect Scrum Traditional (Waterfall) Process Style Iterative and incremental Sequential and linear Requirements Evolve over time Defined upfront Follow On: Team Involvement Cross-functional, collaborative Role-specific, hierarchical Flexibility to Change High — welcomes changes Low — changes can be costly Delivery Frequent, every Sprint At the end of the project Example: In traditional construction, everything is…

Explain a bit more

planned before a brick is laid. In Scrum, like in software development, teams build part of the system, get feedback, and adapt — like adding a new feature based on early user testing.

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.