Create README.md

300/600/800/README.md

@@ -0,0 +1,7 @@
+# 800 - Stories should facilitate iteration
+
+Anyone who read a user story youʼve created should understand its aim and how it helps deliver the feature itʼs related too. But they should also see how it progresses, what the logical iteration is. Good stories are like a lego brick. Theyʼre independent but theyʼre also more useful as part of a group. Alone they form something okay, but when combined, they form something awesome!
+
+You can build this into your user stories by clearly calling out the individual part of a chain theyʼre doing. For example, a user with items in my basket, I need to pay for them ```[using my debit card]```, so that I can purchase my products.
+
+Itʼs simple, distinct, itʼs useful. But by inserting ʻdebit cardʼ weʼve left the space open other payment methods at later iterations. The description focusing on the userʼs scenario allows us to space to iterate the process further, i.e. yes they need to pay to receive the items, but what other things could they do now there are products in their basket? Use this iterative mindset as you create and review user stories in your maps and individuals and youʼll encourage more innovation.