docs(drafts): add agile stories and test automation drafts

- Added agile-stories.md with explanations on story components and estimation
- Added uses-and-abuses.md outlining test automation uses, abuses, and pitfalls

drafts/agile-stories.md

@@ -0,0 +1,41 @@
+# Agile Stories
+
+## What Is The Story?
+
+Three Questions:
+
+* Who is asking for something?
+* What are they asking for?
+* WHY do they want it?
+
+This covers off the three aspects of business value:
+
+* To whom are we providing value?
+* With what are we providing value?
+* What value is being provided?
+
+There are three categories of thought this can be grouped into:
+
+* Actors
+* Objects
+* Purposes
+
+An actor is anyone we interact with, who intends to derive something of value from us.
+
+An object is any “thing” we intend to use, to provide value
+
+A purpose is the value we intend to provide.
+
+All good stories must answer all three questions.
+
+## How Big Is The Story?
+
+This is  where estimating comes in. Estimation involves:
+
+* Effort - The degree of difficulty or amount of work expected during the development process. This should include testing.
+* Complexity - The number of elements, their relationships, their interdependencies, and the amount of research needed, to complete the story.
+* Risk - The scope of the “unknowns” of the story; external dependencies; potential problem areas;   amount of experience with the technologies involved; etc.
+
+These factors constitute a relative measure of story size, not an objective one (like height, weight, or volume).
+
+

drafts/uses-and-abuses.md

@@ -0,0 +1,11 @@
+# The Uses and Abuses of Test Automation
+
+What Is Test Automation?
+
+What Is It Good For?
+
+What ISN’T It Good For?
+
+What are some common pitfalls?
+
+