15 lines
1.1 KiB
Markdown
15 lines
1.1 KiB
Markdown
---
|
|
title: Alignment
|
|
---
|
|
## Alignment
|
|
|
|
Historically, software development followed a waterfall process which starkly contrasts the agile methodologies that are becoming increasingly used by IT organizations. This contrast has created issues within organizations as teams move to align more closely with agile principles.
|
|
|
|
In waterfall style delivery, requirements are defined in full and upfront prior to beginning development work. An agile team needs to align with changing business requirements to enable the organization to meet changing market demands. Instead of completing all planning up front, the planning remains continuous so that the team remains aligned with the overall business vision.
|
|
|
|
Teams must also measure alignment with agile principles within themselves. This is typically accomplished through the sprint retrospective, where team members identify what went well during the previous sprint as well as areas of improvement.
|
|
|
|
#### More Information:
|
|
<a href="https://www.scrumalliance.org/community/articles/2014/january/measuring-alignment-with-the-principles-of-agile">Measuring Agile Alignment</a>
|
|
|