Case study How StoriesOnBoard allowed GlobeRanger to be far more effective with time and resource management and became the ultimate reporting tool for senior management as well.

1. CASE STUDY
StoriesOnBoard drives success
to an IoT enablement business
transformation platform
How StoriesOnBoard allowed
GlobeRanger to be far more effective
with time and resource management
and became the ultimate reporting
tool for senior management as well
A success story:
Decreased project
planning time
Decreased documentation
time of individuals
Decreased down time for
team members
Decreased costs by enabling
more effective planning
More effective time and
resource management
Extensive backend
integration with Jira
Senior Management reporting
tool with all information
www.StoriesOnBoard.com
Visit us for more information
June 2022

2. ABOUT OUT CLIENT
GlobeRanger was founded in 1999 to help organizations improve the visibility of their
business operations. Using a combination of its technology platform and years of
specialist experience, it simplifies the development, and management of IoT
technology and sensor-based solutions.
Today, GlobeRanger is widely recognized as an industry leader in IoT enablement and
AIT based Radio Frequency Identification based asset tracking solutions. As an end-
to-end solutions provider, they work with their customers across a broad range of
industries to deliver the most reliable, scalable, and flexible enterprise edge solutions,
at the lowest cost of ownership.
Their solution includes
→ GlobeRanger iMotion™ IoT enablement platform
-> GlobeRanger asset tracking solutions
-> Improve workplace safety with GlobeRanger AIT Personnel Tracking
-> GlobeRanger Edge Data Orchestration
IoT & Asset Tracking Solutions
Real-time information management that drives business transformation
www.globeranger.com | info@globeranger.com Page 1

3. MAJOR CHALLENGE
We have come a long way with Steve Whitley from GlobeRanger over the years.
Steve leads the software services and solutions delivery team in the creation and
deployment, GlobeRanger's customer facing software products and solutions.
When we got to know Steve at StoriesOnBoard, he was actively looking for a solution
to replace their original user story mapping process, which involved the traditional
sticky notes on a large wall. Their story mapping activities were beneficial to get things
organized, prioritized, and refined quickly for the team.
Story mapping already helped Steve and his team to map out the work to be done, and
prioritize it. However, there was still quite a bit of work transcribing the details of the
user stories while the team was working through the process. Stories still had to be
transcribed capturing details of each sticky either during the story mapping process or
afterwards. Then everything had to be entered into Jira for the team’s backlog - or into
future sprints - so as to be able to work on or refine.
Steve knew if they could find a better solution to enhance their workflow, they could
save a massive amount of time that should allow them to do the story mapping and
import it into Jira all in one fluid motion. They wanted to find a story mapping software
which can replicate the ease and comfort of a room, where everyone could write on
sticky notes, and place them on a wall. So they discussed what needs to be done, from
goals to tasks, details, priorities etc. Finally they found a solution which an allow all
those details to be seamlessly imported into Jira, while they can simply get on with
what they need to do. At that pont StoriesOnBoard came into play.
www.StoriesOnBoard.com | sales@storiesonboard.com Page 2
Roadmap
Feedback Management
User Story Map

4. SOLUTION
www.StoriesOnBoard.com | sales@storiesonboard.com Page 3
Activities
Steve continuously keeps his eyes on essential key activities range from pre-sales
meetings and demonstrations to creating software roadmaps, architectural designs.
He also participates in daily stand-ups, code reviews, and pulls requests to huddling
with the team on various implementation discussions. No surprise that he is always
busy to keep everything on track.
Story mapping has become a vital part of the product teams’ daily routine. Most of
their internal products and customer facing solutions begin with the story mapping
process at GlobeRanger. Independently from project size, the user story creation
process usually starts with a collaborative story mapping session with the whole or
part of the team.
Sprint planning and refinement take place around the story map as well. Steve told us
that having one or more story boards for ideas to be recorded, re-arranged, pointed,
and broken down into categories - epics - and their estimation is key to a well-
organized project from development perspective. He is absolutely right. This approach
allows the team to get a sense of the essence of each project and prioritize MVP
(Minimum Viable Product) features required to deliver on time.
The first part of their workflow differs depending on whether the project is internal or
external but it usually involves gathering some architectural requirements by the
product owner. Next, the team collaborates around a roadmap of the product or
solution that will be built to get a high-level overview of the general features required
to be developed. They map out the high-level features and prioritize which items must
be done in which order and start mapping out each area and features as a team until
they've reasonably "completed" the project.
IoT & Asset Tracking Solutions

5. Process
When Steve started to use StoriesOnBoard he immediately knew that StoriesOnBoard
can help his organization replace their traditional story mapping process and unite
people around the story mapping activities to accomplish their goals.
According to Steve’s experiences over the years, when teams are consistently
participating collaboratively in their user story creation process, the team is more
engaged in what they’re doing, which will lead to a higher empowerment and
productivity in the work they do. The collaborative story mapping processes begins
with the cycle of team ownership for the project that they’re working on and leads to a
higher degree of care throughout the sprint and the entire project. It helps provide the
macro-level view that sometimes gets lost when focusing only on the micro-level user
stories. StoriesOnBoard can greatly help to find the right balance.
The team at GlobeRanger do their sprint planning and refinement in StoriesOnBoard as
well. It is allowing them to see everything all on one screen; epics, stories, releases,
etc. so this makes everything much easier to control. Steve even uses StoriesOnBoard
as a project planning tool and they all collaborate on the project. They have planned
long-term and short-term projects and executed them with the help of StoriesOnBaord
to keep track of everything and break their plans down into actionable items.
At the time of the creation of this study, Steve and his team were coming off a three-
week workshop session around the re-design of an internal platform. In these sessions
the teams were able to take a deep dive in various aspects of their systems, then map
those areas out in StoriesOnBoard. The team established shared understanding over
StoriesOnBoard and developed a big picture view to simply oversee their upcoming
tasks.
The team quickly figured out that StoriesOnBoard can be utilized as a reporting tool as
well. For larger projects that involve multiple work streams (Web, API, Mobile etc.), they
create multiple story boards for each sub-item to keep the sub-project small and easy
to look at on a story map. This allows them to oversee the context of their projects
quickly and easily. Then the product owner can log in to each story map, since they
map-and-point using StoriesOnBoard. Each Epic - they use blue cards as epics - rolls
up story points from the cards below. Furthermore, as the project progresses,
StoriesOnBoard shows the set status. StoriesOnBoard can display the connection
between Jira tickets and user stories with the ability to edit them on either platforms
and it will be still synchronized. Story cards on the story map can use and display the
original Jira tickets’ ID. Thus, the product owner will track project completion directly in
StoriesOnBoard for customer and internal reporting on a weekly basis.
www.StoriesOnBoard.com | sales@storiesonboard.com Page 4
A success story:
IoT & Asset Tracking Solutions
Real-time information management that drives
business transformation

6. When Steve started to look for a story mapping software, his main goal was to find
something that replicated the ease and comfort of a room. He wanted a platform
where everyone could write on sticky notes and place them on a wall and discuss
everything such as goals, tasks, details, priorities etc. They found all these critical
areas in StoriesOnBoard.
Steve and the team were able to use StoriesOnBoard as a road mapping tool for
planning their upcoming year, as well as their next few sprints. StoriesOnBoard helped
them to spend more time with critical issues and allow them to be more agile.
The whole team participates in a multi-threaded activity by mapping out objectives,
goals, stories, and tasks in StoriesOnBoard. This practice becomes a far more
simplified task when all join in. Changing story priorities, releases, and even moving
stories from one objective, goal, or epic to another is a simple drag-and-drop
operation.
Trying to accomplish all that with their previous process, writing on paper then typing
into Jira, or entering data directly into Jira was a long, arduous and time consuming
process and often single threaded. That usually blocked quite numerous people
waiting for a single person to finish the task of transcribing or editing stories in Jira.
Even though, we do have the more expensive
monthly subscription but even then, the financial
impact of going without the integrated story
mapping system brings with it increased project
planning time, increased documentation time on
individual members, and increased down times for
more members of the team, all of which end up
costing more of those down members can’t be
used elsewhere.
www.StoriesOnBoard.com | sales@storiesonboard.com Page 5
RESULT
“StoriesOnBoard is not a product or
service I would ever like to be without.
“
Steve Whitley
Technical lead

7. StoriesOnBoard has all desired requirements that GlobeRanger’s team has always
wanted. It is a collaborative portal where the entire team can remotely log into and
access at the same time. It has a sticky note design surface that simulates the original
paper wall user experience and above all, StoriesOnBoard has an extensive backend
integration with Jira that allows the team to push stories to Jira and continue their
work.
Beyond story mapping, GlobeRanger previously used Aha! as a reporting tool.
However, Steve’s team had to double enter their epics from Jira into Aha! to track
progress of where their development was on an ongoing process. Steve joined to
StoriesOnBaord’s private Roadmap Beta program and started to experiment with the
new functionality. The senior management of GlobeRanger visited Steve in the US from
the UK. He was able to put some of their effort into roadmaps in StoriesOnBoard, as
internal tooling were part of their topics for discussion. Based on what the senior
management saw, they agree to shift from Aha! to StoriesOnBoard for senior level
reporting since they are already using StoriesOnBoard, and all the desired information
is already there.
Steve is confident that the investment they made, using StoriesOnBoard was worth it,
and it delivers great value to GlobeRanger every day.
Learn more about how StoriesOnBoard can make your workflow even more effective
and ensure success to your organization as well.
“A key advantage of StoriesOnBoard is that it allows us
to be far more effective with our time and resources than
we would be without it.”
Steve Whitley | Technical lead
Visit us for more information:
www.storiesonboard.com
Contact us:
sales@storiesonbaord.com
End-to-end product management platform
User Story Map | Feedback Management | Roadmap