Misalignment will occur when the requirements gathering process results in misunderstandings of the business needs.  The commonly cited reasons are that the requirements gathering participants lacked proper domain knowledge, or key SME resources don't have sufficient time to work with the team responsible for documenting the scoping deliverables.  Applying the proper scoping methodology and proper utilization of key resources are key ingredients for ensuring stakeholders are properly aligned with the project scope.

A common challenge occurs when stakeholders assume their expectations are covered by the project scope and then realize their needs aren't completely met so push to expand the previously agreed upon scope.  Expanding scope can negatively impact quality of work when the team must cut corners to accommodate additional unplanned work.  Another ailment is when prioritization of needs shift.  Strategies for avoiding scope creep can help your organization avoid project churn and lower development costs.

You can’t achieve operational excellence if your systems have become navigational hairballs.  Agility and complexity are not synonymous.  To thrive, businesses require open ecosystems. Convoluted systems with customized quirks become increasingly hard to maintain as the system adapts to new requirements.  Many times bad processes aren't weeded out with new enhancements.  It's essential as systems change to keep the processes that you like and eliminate those you don't and to develop the simplest solution that meets the business need.