Differences

This shows you the differences between two versions of the page.

--- how_does_the_agile_approach_allow_us_to_deliver_early [2016/06/08 12:45] – hpsamios
+++ how_does_the_agile_approach_allow_us_to_deliver_early [2016/06/21 12:48] – [Premise] hpsamios
@@ Line 9: / Line 9: @@
 ====== Premise ======
-When you move to an agile approach, a lot of people worry about how we delivery to scope. We are very used to planning all our work upfront and then working to meet that plan. An agile approach seems very strange (and concerning) because we change the plan based on feedback.
+When you move to an agile approach, a lot of people worry about how we deliver to scope. We are very used to planning all our work upfront and then working to meet that plan. An agile approach seems very strange (and concerning) because we change the plan based on feedback.
 The fallacy with the traditional approach is that we expect able to get the plan correct in the first instance. As most work we do is "new" (in others words we are doing it the first time) and we are not making 1000 copies of the same thing, then we also know that this planned approach may not make the most sense - we are only pretending that we can know everything at the beginning of the work.