Skip to content

Latest commit

 

History

History
50 lines (31 loc) · 2.65 KB

03-user-stories.md

File metadata and controls

50 lines (31 loc) · 2.65 KB
Raw

A Scrum-ified (Scrum-ish?) J-term

Aggregate responses

  • Do you think that you will use code or data analysis in your future work?

User Research

Since the class is our product, and we're going to run it using agile, lets do some user research.

  1. Lets split into pairs and for 5 minutes you have a free-form interview of your partner. Ask questions, take notes, try and understand what it is that they're looking to get out of this class.
  2. Now switch roles for another 5 minutes.

Writing Good User Stories

As a _____<role>_____________

I want _____<feature>_________

So that _____<value>__________

User Stories ought to be

  • Independant - stories can be worked on in any order
  • Negotiable - A story is not a contract. A story IS an invitation to a conversation.
  • Valuable - If a story does not have discernable value it should not be done.
  • Estimable - What happens if a story can’t be estimated? You can split the story and perhaps gain more clarity. Or do more research to estimate it.
  • Small - Suggested 3-4 days of work max. For our class lets say 1 day of work MAX.
  • Testable - How do you know when you're done?

Definition of Done

User stories ought to have a definition of done. Generally there is one generic definition of done that applies to every story in the project, but aslo specific acceptance critera for each story.

Source: http://agileforall.com/new-to-agile-invest-in-good-user-stories/

Further reading from the Agile Alliance

➡️ Try It

Since we're running a scrummy class, and this class is our product. Lets write good user stories for the class! Lets do this one in pairs.

  1. Write user stories from your interview of your partner
  2. Brainstorm stakeholders in the class
    • 2 as yourselvef
    • 1 as other "users" (in our case stakeholders)
  3. Pick the 3 most important stories, for each story make sure you have a definiton of "done" as well as a checkbox for I-N-V-E-S-T. Be honest about which part of I-N-V-E-S-T it meeets and which part it does not meet.

Lets share and workshop them together. Present one and put the rest up on the board. I will look through them after class and see how they can inform the development of the course.