Doing more with Story Maps

Posted on November 4th, 2011 in Agile, Story Mapping by siddharta || 1 Comment

This is a three part video series that shows how you can do more with story maps. Story Maps are a really powerful method to both a) create the product vision in a collaborative manner and b) visualise the scope. Here at ToolsForAgile.com we are huge fans of visualisation, and with our electronic story maps, you can do a whole lot of cool things.

The series has three parts

  1. Creating the story map
  2. Release planning
  3. Tracking progress against the vision

Creating a story map

Creating a story map is not simply a matter of entering data into the system, but a process of collaborative exploration. Our tool is expressly design to support this exploration. This video shows a typical session of creating a story map. Notice how cards get moved around, some cards get grouped together while others get split. And the tool never gets in the way throughout the process.

Release Planning

Release planning is where development team meets business strategy. Therefore, before you do a release plan, it is important to understand the business strategy. Which features are our differentiators? Which parts of the system are risky? Do we need early feedback on specific features? Are there some features which we are not sure the market will accept? Only when we answer these question can we make a truly effective release plan.

Unfortunately, release planning is often considered only in terms of selecting some stories and calling it a release. Most electronic tools do not allow you to effectively do a business visualisation prior to creating the release plan. The result? Product development is not aligned to business strategy!

In this video, we show you how our tool supports creating release plans through visualising the application in business terms

Execution Tracking

Once you have your vision laid out and the release plans done, then its time to execute stories. You will usually take your stories from the story map, and go elsewhere and put them in another tool or physical board to execute them. And what happens there will not be reflected back onto the story map.

But things are different with toolsforagile.com. In this video we show how to you move stories between the story map and team boards (scrum/kanban boards), and have the result overlaid on the story map.

You can now answer questions like

  1. How many of our differentiators are remaining?
  2. Have we implemented our risky features?
  3. What level of enhancement is a specific feature?

Doing Distributed Agile?

Share and collaborate with distributed teams with our electronic agile board tools. Get all the benefits of electronic tools without sacrificing the benefits of physical boards. Supports Scrum taskboards, Kanban boards and user story maps. Check it out!

One Response to “Doing more with Story Maps”

  1. klinika stomatologiczna mokotów Says:

    You actually make it appear really easy together with your
    presentation but I in finding this topic to be actually one
    thing which I believe I’d by no means understand.
    It seems too complicated and very wide for me.
    I’m taking a look forward to your subsequent put up, I will attempt to get the cling of it!

Leave a Reply