After using the Product Vision Board thanks to Roman Pichler because of using his model, I started modeling the Product Backlog in order to show the Epics,
Features and the first user stories for the first Sprint in a company that wants to adopt Agile in many test projects.
According to the books (or most of them) the whole team including the Product Owner should be located in the same office so every information radiator
would be visible for everyone.
Well, in that company the Product Owners were located in other buildings far away from the Scrum team so they need to have access on virtual Board and
Product Backlog in order to validate them without going to the office.
At that time, I always use a wall to post the Product Backlog but the client provided us small room where there was enough space to put it so I decided to look
for a software to support the diagram of the Product Backlog.
Reading Linkedin I found a great and simple software thanks to one Agile Coach that unfortunately I couldn’t remember his name. The software is www.storiesonboard.com
From this moment, I will use the marketing statements from its website that will impact more than my simple words.
Turn your flat Product Backlog into a User Story Map
Share your user story map online with StoriesOnBoard!
One of the biggest issues of working with remote teams is to have the same information radiator (the famous and well known physical board). I remembered
one experience working with a client (developers as well) located in San Francisco that we have two physical boards in order to provide visibility in each place.
However, you can take advantage of the software and using to do the Stand up (or Daily if you prefer) meeting with your remote Product Owner (that is another working
Agile scenario) showing him the Stories on the Board!!!
In addition, if you want you can implement an Impact Mapping with this software.
Last but not least, physical board are the best but we have to face with the fact of working with remote Scrum teams including the
Product Owner that is the worse Agile scenario.