Sunday, August 11, 2019

Stop Calling Your Tasks "User Stories"


There are a lot of things I hate about scrum, or at the very least, I hate how teams are implementing it, if you want to get really pedantic and tell me "that's not true scrum" in response.

The goal of a user story isn't to track your work, it's to elicit user requirements.

Stop calling your technical work user stories. They aren't. A big problem with scrum is that user stories often can't be completed in a two week sprint. This will either lead to wild point swings when measuring velocity or having stories split to fit them in. It's perfectly fine to split a user story, but much too often it's being done on technical grounds because you didn't finish some technical tasks necessary to implement it. Let me give an example of how a real user story can be split.

  • Story: I want to add a comment system to my blog

That might be a pretty big task. It's also pretty vague and high level. What we should do is sit down with the user and ask them to be more specific. This story might instead become an epic and get broken down into the following stories.

  • Story 1: Create a registration form that asks for username, password, and email address.
  • Story 2: Create a login form that asks for the username and password for someone to login after registering.
  • Story 3: Display a comment box at the bottom of each blog post.
  • Story 4: Display the posted comments below each post.
  • Story 5: Allow users to sort comments by oldest / newest.
  • Story 6: Allow some registered users to be marked as moderators by the blog owner.
  • Story 7: Allow moderators to see a "delete" button next to comments to remove offensive comments.

Notice anything about the above stories? They are all things the user can understand. Now, of course there are going to be applications within specific domains where a random person on the street isn't going to understand everything. I wouldn't expect a non-animator to know what a "keyframe" is, but if I'm writing software for animators, it's fine to use that term in the story.

They are called "user stories" because they are from the perspective of a user. The goal is to figure out what they want. Maybe they aren't sure yet and things will change with time (hint: That's what being agile is about), but they are all things the user can understand. The goal is to determine their requirements. You break down stories for two reasons; to get more information, or to define points of deliverability. If the user really wants comments on their blog ASAP and is okay with not having moderators for a little while, then you can push out a release between those stories.

Here is what typically happens instead. Someone starts on the user registration story. They don't get finished or don't think they can finish in two weeks and they split it like this.

  • Story 1: Add Angular FormBuilder to registration page.
  • Story 2: Send POST request to backend to make sure username is not already taken.
  • Story 3: Salt password and hash with SHA-256.

What the heck is an Angular? What is a POST request? I have high blood pressure, I don't need more salt. What's a SHA and why do I need 256 of them?

The problem with doing it this way is that now users have no idea what's going on in the project, the developers lose sight of the requirements, and it's hard to know when something is in a deliverable state.

Please, do track your tasks. It's important to know what they are. Add them as dependencies to your user stories, but don't call the tasks themselves stories because they aren't.

When you actually have proper user stories, you will find that sometimes even a very specific story still can't get done in two weeks. Stop trying to fit them into a two week window. Track tasks instead to measure your velocity. The tasks can be much smaller than the stories so you will get better estimates and you won't be constantly shuffling tickets around and obscuring your progress because your scrum master or overpaid consultant thinks being agile is about following arbitrary rules.