It all begins with a product. Scrum started as an outgrowth of Agile software development, but it can be used for products (or projects) of many types.

Add a Product

In AgilePress, we ask you for a few pieces of information about your product:

  1. Enter a product name in the first field;
  2. Use the “Excerpt” area to enter a brief description of your product;
  3. Decide whether or not you’d like to allow comments (we recommend that you do);
  4. Finally, you can specify the current version of your product and the version where you’ll be after the sprint (both of these are optional).

After you’ve added your product, add a story or two.

Add a Story

In Scrum, we find out what our end-users need through stories. Although there are multiple methods for formatting user stories, perhaps the most common is “As a [role], I want to have/see/be able to do [something] so that I can have [desired outcome].”

For example, a story might be “As a pilot, I want to be alerted to changes in weather conditions along the path of my flight,” or “as a guitar player I would like to be notified if a string becomes slightly out-of-tune.”

User stories stay out of the solution and focus on who wants what and why.

The best way to use stories in AgilePress is to allow your end-users access to create their own. For now, though, create at least one story using the form below, based on your knowledge of what your users might want from your product.

  1. Enter a story title in the first field;
  2. As with your product, use the “Excerpt” area to enter the text of your question, and decide whether or not you’d like to allow comments;
  3. Last, use the dropdown to associate this story with a product. (If you have more than one product in your dropdown, please choose the one your created in “Step One: Create a Product”)

After you’ve added your product, you can optionally create some tasks if you’re ready.

Add Tasks

Tasks come out of stories. Sometimes a story becomes a single task; other times, one story might result in many tasks. Tasks are our to-do items.

For example, if a story states that “as a forest ranger, I would like to get topographical maps of my beat on my phone,” you might have tasks to find maps, another to digitize them, a third to load them into your app, etc.

Click here to open the add-task screen in a new window, and then create a task based on your user story from the previous step. Remember that a task is a specific work item that can be done in a short period of time (usually two weeks or less).

  1. As with your product and story, enter your task’s name in the first field;
  2. Use the “Excerpt” area to enter a short description of your task;
  3. Again, use the dropdown to associate this task with a product. There’s no sprint yet, so leave the second dropdown unset. Finally, set you task status to “Project Backlog Items”.

On to “Step Four: Schedule a Sprint” (using the navigation tabs at the top of the page).

Add a Sprint

A sprint is a finite period (usually two weeks but never more than four or less than one) in which you or your team plans to accomplish a set number of tasks.

Go to the add-sprint screen in a new window, and define a sprint.

  1. Your sprint name can be as simple as “Sprint One” or you can use it to describe the intended outcome (such as “First Release Target Sprint”);
  2. The “Excerpt” area can be used for any notes that you might want to include to convey the point of the sprint;
  3. Again, pick a product from the dropdown to which your sprint will be connected. Select a start and end date (preferably for a duration of two weeks). Finally, choose whether or not this sprint is a backlog target (say “yes” and we’ll explain later!)

Adding Tasks to a Sprint

The obvious way to add tasks to a sprint is to select the appropriate sprint when you’re editing the task: However, this can also be done in two ways from the boards themselves. The first way is when working from a backlog board.  Logically, you’ve added stories (the “what” we need to do) to your backlog board, and you will choose from those to build your sprint.  Let’s look at this process with the following example of a band who wants to record their next album. In this example, we know that we need to write some songs and then record them.  These would be epics, because they’re big things that will need to be broken down: Here we can see what this might look like on our backlog board: Some steps for recording the album might be “schedule recording studio” and “hire a producer” … those would be stories with “record songs” as the parent: Notice how we set the “Parent Epic” field in the above story to “Record Songs”; this is optional but good for organizational purposes. We decide that, during our next two-week sprint, we can get both of those stories done, so we’re going to add them to our target sprint.  We want to make sure that our upcoming sprint is set as the backlog target: As long as we have a backlog target, you can just drag stories into the “Send to Sprint” column and they’ll move to your sprint: Notice that there is a new button (“+”) on the Sprint Backlog story notes.  This allows you to add tasks that automatically have the story from which you clicked the “+” as a parent. From here, we can start dragging our tasks through the board as normal.

Copyright 2017-2019, KMD Enterprises, LLC