You can code it, I can help!

Using SmartView - Part II

In my last post I explained the basics of using SmartView to create a new project and add User Stories to a Story Map.

Now that we have stories in our Story Map, we are going to learn how to create releases and prioritize our work.

Planning Releases

In my last post, I copied over the User Activities and User Tasks into Groups and Subgroups to create the Story Map.

After signing in into the application we can see the project index, which shows we have some stories in the Planning section.

Now is the time to create and assign releases.

The Ice Box

When we look at the Story Map we can see all the stories have been assigned by default to the Ice Box release.

The Ice Box is the release to use when you are unsure where to put a User Story. By default it is the only release created for a project. You can tell it is selected because it is highlighted in orange.

You can also tell that a story is assigned to a release by looking at the top right corner of the story. In this case you will see the cute ice cube and the code to identify the release: ICE.

Now we’ll learn how to change the release of a story.

Release management

By using the menu in the top left corner we can access the Releases page.

The Releases page shows all the releases created for the project that are in progress or completed. So far we have only one release in progress(the default one) and zero completed.

I will create two more releases so I can assign User Stories and start working on them.

Each release has a Tag to identify it when looking at User Stories or working with the Story Map.

I choose the code MIN for the first minimal release and FCY for the second, fancier release. (I personally prefer to use meaningful codes but if you find R1, R2, etc. clearer feel free to use them.)

Assigning releases to stories

Going back to the Story Map view, we can tell the that the releases have been added because in the top right corner the release toolbar now shows three releases: ICE, MIN and FCY.

Before we start with the release assignment I want to make sure we are not filtering using the current release (I will explain why in a bit). To do so, I will turn on the filter to Show all releases.

To assign a Release to a User Story we just need to drag the release to the story and drop it.

You can see that the release changed because, instead of showing ICE, the story shows MIN or FCY in the top right corner beside the Release icon.

Now you see me, now you don’t

Though looking at all the releases at once can be useful, most of the time you will probably want to work with just one release at a time.

The Releases toolbar not only lets us assign releases to stories but also works as a filter to select which release is showing in the Story Map.

Unless the Show all releases filter is selected (you can tell because the icon is highlighted) the selected release dictates which stories are displayed on the Story Map.

Using the MIN release filter, the Story Map view changes to show only those stories.

For the FCY release we get similar results.

Take note that the Organize Email Group folder changes to show the amount of stories in each release.

What’s next?

In the next post in the series we will explore how to start working with the stories, assign them to the Backlog and use the Kanban Board to manage workflow.

In the meantime feel free to take advantage of the interactive guides that come with SmartView to learn, in a series of steps, all the other functionalities that the application has to offer.

To access the Guides just move your mouse to the bottom left corner and click the icon inside the orange speech bubble.