►
From YouTube: Gitlab Verify:Testing Roadmaps walkthrough
Description
How we use GitLab to display our roadmap to different stakeholders internal and external in the Verify:Testing team.
All the team category direction pages can be found on our team page: https://about.gitlab.com/handbook/engineering/development/ops/verify/testing/#mission
The Quarterly View: https://gitlab.com/groups/gitlab-org/-/boards/2350419?scope=all&label_name[]=group%3A%3Atesting¬[label_name][]=priority%3A%3A1
Epic Roadmap: https://gitlab.com/groups/gitlab-org/-/roadmap?state=opened&sort=end_date_asc&layout=MONTHS&timeframe_range_type=CURRENT_YEAR&label_name%5B%5D=group%3A%3Atesting
All the refinement kickoff and milestone kickoff videos are posted on the Verity:Testing team's playlist: https://www.youtube.com/playlist?list=PL05JrBw4t0Kq53VUOvTk3VdXN79PA0SXT
A
Hi,
I'm
james
heimbach,
the
product
manager
for
the
verified
testing
group
at
gitlab,
and
someone
asked
me
the
other
day
how
I
present
my
roadmap
to
various
stakeholders,
both
internal
and
external.
So
I
wanted
to
put
together
a
quick
walkthrough
of
how
I
present
at
least
the
testing,
we're
mapped
to
different
stakeholders
and
how
we
use
gitlab
at
gitlab.
To
do
that,
I
will
note
that
any
data
presented
here
as
an
informational
is
for
informational
purposes.
Only.
A
The
content,
like
the
problem,
statements
or
opportunities
ethics
issues
is
very
very
likely
to
change
over
time,
since
this
is
just
a
snapshot
in
time.
So,
first
I'm
going
to
start
with
a
very,
very
high
level
and
don't
actually
use
gitlab
for
this.
But
this
is
what
I
call
our
now
next
and
later
view.
So
this
is
usually
stated
as
problem
statements,
things
that
we
want
to
solve
things
that
we
want
to
do
for
our
customer
and
it's
really
big
themes.
A
A
Next
things
are
likely
things
that
we
have
validated
a
problem.
We
think
that
that's
the
best
problem
for
us
to
go
solve
and
as
the
most
reach
it
has
the
best
impact
for
customers.
We
know
customers
want
it
because
we
validated
it
and
we're
into
solution,
validation
on
it
or
even
completed
solution.
Validation
for
that,
and
then
our
later
is
here's
the
maybe
even
a
problem
that
we
validated.
A
So
this
roadmap
is
great
for
external
audiences.
It's
great
for
field
teams,
especially
when
you
have
a
small
amount
of
time
to
talk
about
what's
on
the
roadmap,
and
you
can't
really
dig
into
35
issues,
but
it
really
speaks
to
the
value
drivers
that
we
have
the
gitlab
and
the
personas
and
the
problems
that
they
have
as
they're.
A
Often,
making
those
buying
decisions,
this
also
goes
hand
in
hand
with
our
category
direction
pages
and
really
the
top
vision
items
there
or
something
that's
out
in
the
later
will
probably
be
pulled
from
this
vision
section,
and
so
we
update
these
often
to
reflect
our
current
thinking
of
where
we
want
the
category
to
go,
issues
that
we
think
are
tied
to
that,
and
this
is
always
up
to
date
and
always
publicly
accessible.
So
it's
a
great
place
to
point
customers
at
to
start
to
think
about
that
high
level.
A
What's
the
roadmap
look
like
for
this
category,
so
then
getting
down
a
little
bit
in
altitude,
we
have
in
verify
we
use
this
view,
one
of
the
job
views
or
one
of
the
the
board
views
broken
up
by
quarter
of
big
things
that
we
want
to
work
on.
So
these
are
key
deliverables.
Often
it's
a
key
piece
of
a
larger
epic
kind
of
the
last
thing
that
we
might
deliver
or
a
couple
of
points
of
key
customer
functionality
that
we
want
to
deliver
an
outcome
that
we
want
to
deliver.
A
A
It
gets
a
little
bit
less
and
less
as
we
go
out
further
and
further
and
the
descriptions
get
fuzzier
and
fuzzier,
and
sometimes
in
these
maybe
we
haven't
even
defined
a
problem
statement,
so
these
might
fall
out
if
we
find
that
the
problem
isn't
great.
So
this
view
is
great
again
for
the
field
teams
to
just
kind
of
validate
that
problems
that
we're
thinking
about
or
opportunities
that
we're
thinking
about
match
up
with
what
customers
are
focused
on
they
care
about.
A
This
view
is
also
great
for
the
trio
of
me,
the
product
manager
or
product
designer
and
our
engineering
manager,
as
we're
looking
a
quarter
or
two
out
and
starting
to
think
about.
What's
going
to
be
designed,
how
does
this
fit
in
with
other
features?
Where
are
there
cross-stage
opportunities?
What
kind
of
technical
investigation
do
we
need
to
do
or
across
team
collaboration?
A
I
use
this
view
an
epic
road
map
just
to
keep
track
of
how
we're
progressing
through
those
really.
This
is
an
internal
view
for
me,
an
engineering
manager
product
designer,
sometimes
to
see
how
are
things
going?
Are
we
stretching
something
out?
Do
we
need
to
scope
down
to
try
to
get
this
delivered
and
just
to
keep
that
scope
creep
down,
how
to
keep
things
tight
and
and
moving?
A
So
as
we
get
closer
or
git
lab,
we
released
each
month
on
the
22nd
and
in
testing
we
plan
for
those
milestones
using
one
of
these
planning
issues.
So
right
now,
currently,
as
of
september
28th
2021,
the
team
is
currently
working
on
or
doing
development
in
the
14-4
milestone,
and
so
I'm
wrapping
up
my
planning
on
fourteen
five.
I've
already
recorded
a
refinement,
kickoff
or
will
be
soon
maybe
to
walk
through
this
planning
issue
with
the
team,
and
so
what
we
have
here
is
always
the
theme
of
our
milestone.
A
These
always
roll
up
where
I
try
to
get
them
to
roll
up
to
one
of
our
larger
product
investment
themes
for
the
year
and
the
top
deliverables
of
how
they
deliver
towards
those
things
that
contribute
to
it.
We
also
have
research
anything
that's
happening
as
part
of
our
research
problem,
validation
or
solution,
validation
during
this
time
or
technical
research
that
we
need
to
do,
and
then
our
designer
will
add
design
issues
in
here.
A
We
have
a
couple
that
will
be
coming
up
for
14.5
and
you
get
the
complaining
issue,
but
that's
a
good
time
for
us
to
talk
to
the
team
about
here's.
What
we're
designing!
What
questions
do
you
have
about
implementation?
Do
we
have
the
data
that
we
need
to
present
this
view
if
it's
something
of
an
interface
questions
like
that,
also
like
to
show
them
active
research
projects
or
problem
validation,
solution,
validation
that
we're
doing
and
how
that
maps
back
to
our
quarterly
plan
and
how
we're
progressing
towards
that?
A
So
once
this
gets
kicked
off
or
the
milestone
gets
kicked
off,
then
we
go
down
to
really
our
issue
board.
I
like
it
in
this
board
view
sorted
by
our
different
columns.
Some
people
like
it
in
just
the
list
view
of
the
issues
I
like
to
look
at
it
this
way
so
that
we
can
see
you
know
where
things
blocked,
not
just
in
our
blocked
category
but
maybe
what's
been
sitting
in
review
for
a
while.
How
can
we
help
move
things
along
or
what's
been
sitting
in
deb
for
a
while?
A
Maybe
it's
not
quite
really
ready
for
development,
or
even
still
in
planning
breakdown.
This
is
for
the
current
milestone,
so
we
have
a
couple
of
things
that
we
need
to
get
moving
forward
and
this
really
becomes
our
single
source
of
truth.
Once
a
milestone
kicks
off,
and
I
like
to
have
it
really
be
the
source
of
truth
even
before
that,
if
possible,
so
we're
not
looking
in
multiple
places
to
figure
out
what
we're
working
on
today.