►
From YouTube: Testing Team Think Big Process
Description
Walking through the process for how we create, curate and then debate (it had to rhyme) ThinkBig issues in Verify:Testing.
ThinkBig board: https://gitlab.com/gitlab-org/ci-cd/testing-group/-/issues?label_name%5B%5D=ThinkBIG%21
A
A
question
came
up
on
our
last
think
big
review
last
week
earlier
this
week
is
a
question
of
what
my
expectations
were
from
the
team
prior
to
having
our
think
big
meeting.
So
I
just
wanted
to
walk
through
my
process
a
little
bit
and
kind
of
how
the
think
banks
were
organized.
So
this
is
the
list
I'll
share
the
link
to
this
in
the
video
comments
and
in
our
slack
channel-
and
I
don't
want
to
be
the
only
one-
creating
these
think
big
issues.
A
So
please
go
ahead,
jump
in
there
and
create
one.
There
is
a
template
for
it.
It's
already
on
the
think,
big
template
here
with
a
checklist
that
walks
you
through
some
of
the
sections
that
I
like
to
get
filled
out
beforehand,
and
you
can
always
assign
that
to
me
for
any
further
refinement
or
bring
up
any
questions.
A
If
you
want
to
create
something
new,
so
then
please
review
the
list
anytime.
I
would
love
to
get
thumbs
on
these
thumbs
up
thumbs
down
even
comments.
Questions
happy
to
iterate
through
the
ideas
that
are
in
there
before
we
start
and
then
a
couple
of
days
before
our
next
thing,
big
about
a
week
before
I'll
ping.
The
team,
with
the
link
to
the
list,
ask
for
that
that
contribution
those
thumbs
are
those
comments
and
then,
a
couple
of
days
before
I
will
look
and
see
what
has
the
most
thumbs.
A
What
has
the
most
votes
or
the
most
comments?
And
if
everything
is
about
the
same
or
there
isn't
much
interaction
there
I'll
just
pick
something
myself.
Usually
it's
something
that
aligns
with
what
I'm
hearing
recently
from
customers
or
maybe
some
work
that
we
already
have
scheduled.
That's
coming
up,
so
that
we
can
better
refine
it
better,
crystallize,
our
mvc.
A
So
from
there
the
process
is
what
we've
been
doing.
We
have
our
two
discussions.
I
think
big
and,
I
think
small
I'll
add
links
to
those
into
the
closed
issues
as
well
as
any
follow-up
issues
that
maybe
we
created
from
that.
So
here's
a
case.
We
have
to
think
big
and
think
small,
some
of
the
related
issues
that
were
in
it
and
then
our
smallest
thing,
which
for
this
one
is
still
scheduled,
and
so
that
is
my
process
for
think
big
and
kind
of
the
expectations.