= Agile/UserStory =
 * Should be short, simple and focussed.
 * https://www.betteruserstories.com/courses/better-user-stories/videos?video_id=1


== The user story template ==
 * Simply follow this format: {{{

As < an end user: WHO >,

I want to < perform a specific action or goal: WHAT > 

so that I can < derive specific value or benefit: WHY >

}}}


== User story conversations and time negotiations ==

 * Detail
   * Break down into tasks
 * Acceptance criteria
   * High level test
   * Confirms the story is complete
 * Story points - size/scale effort
 * Assignee, Epic Link, Sprint, Status


== Check for great user story INVEST ==
 * [I] Independent - not depend on success of another story
 * [N] Negotiable - adjust AC, clear, ideas around implementation, fit more needs
 * [V] Valuable - business value , background
 * [E] Estimable - clear enough to understand scope and quantify
 * [S] Small - one sprint
 * [T] Testable - AC indicate when done

== Story maps ==
Start with the objective and ask:

 * What problem are you trying to solve?
 * What product do you want to create?
 * Are there any features you want to add?
 * What will a user most likely want to do at each point?
 * What mistakes could a user make at any point?
 * What could confuse a user at any point?
 * What additional information might a user need?
 * How will giving users each aspect add value to the bottom line?

 * Layout sequence and alternative's at each step, split int mvp , need soon, nice to have


== Quotes ==
 * "Stories aren’t the requirements; they’re discussions about solving problems for our organisation, our customers and our users that lead to agreements on what to build."
   * Jeff Patton, Agile Evangelist