Silver Stories Features

Click on any of the images below to view them in full size


This is the workspace home page that is displayed immediately after you log in. The home page is designed so you get a quick overview of the entire workspace at once.

  • The current status of each story map is shown in a widget.
  • You can also see widgets relating to Silver Catalyst project boards in the workspace. Learn more about Silver Catalyst

Story Maps

Silver Stories allows you to create user story maps which visualise the whole score in the story map format.

A story map allows you to have 3 levels of requirements, with yellow cards representing the top level, red cards representing the mid level and blue cards representing the bottom level. Silver Stories does not attach any meaning to these levels - they can be interpreted according to any requirement hierarchy that you use.

Some common hierarchies are:

  • Goal -> User Activity -> User Task (Commonly used with user story mapping)
  • Theme -> Epic -> User Story (A common hierarchy in Scrum)
  • Goal -> Minimal Marketable Feature (MMF) -> User Story (Popular with Kanban teams)
  • Silver Stories allows you to create quite huge and complex story maps, like this one.

    Cross-Team Integrated Flow

    Silver Stories integrates with Silver Catalyst to provide an end to end, integrated, multi-board, multi-map flow. With this feature, you can create high level goals, break them down into user stories, distribute user stories to be developed by different teams, and visualise the whole flow on a story map. Here is how:

    Once you create a story map, you can then allocate different stories to different boards in the workspace. In the image above, some stories have been send to the board of the Offshore Team and some to the Onshore Team. When you do this, the stories are copied to the backlog of the respective team board in Silver Catalyst.

    Each of the teams pulls the allocated stories from their backlog onto the Silver Catalyst board and work on it as usual. Teams can use either the Scrum board or the Kanban board.

    As teams move cards on their boards, the status is updated on the story map. At any time, you can visually see which stories are not started, which are in progress and which stories are done. Overlaying the progress on the story map enables stakeholders to visualise progress much better compared to the usual reports provided by other tools.

    Single team, Multiple sources

    You can also have single teams which work on stories from multiple story maps. Stories are tagged with the name of the story map so that teams know which stories are related to which projects.

    For example, a Linux platform team might work on more than one project on the linux platform. Each project is defined as a different story map, and some stories from each story map are allocated to the Linux platform team's board.

    By tagging the stories, the team knows which stories are related to which story map

    The team can then apply filters on this property in Silver Catalyst just like any other custom field. In the image above, a filter has been applied to highlight the stories that are from the Intranet Enhancement story map. Learn more about Silver Catalyst

    Custom Fields

    That's not all. Stakeholders can define custom fields for story map cards. This is useful for tagging metadata on cards.

    In the image above, some of the story map cards have been marked "Must"

    This metadata is copied along with the story when a story is allocated to a team. Besides that, the metadata allows the stakeholder to quickly understand progress along several axis.