From b583acf6ff5565b4a1b0f2aa33f33b3121a12b6a Mon Sep 17 00:00:00 2001 From: lizcamp Date: Thu, 1 Nov 2018 12:29:45 -0400 Subject: [PATCH] Created the first draft (#33113) created the beginning of a draft to an article on agile alignment --- guide/english/agile/alignment/index.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/guide/english/agile/alignment/index.md b/guide/english/agile/alignment/index.md index 178887f1bb..2f1f32232c 100644 --- a/guide/english/agile/alignment/index.md +++ b/guide/english/agile/alignment/index.md @@ -3,13 +3,12 @@ title: Alignment --- ## Alignment -This is a stub. Help our community expand it. +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. -This quick style guide will help ensure your pull request gets accepted. +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: - - +Measuring Agile Alignment