►
From YouTube: Digital Experience Iteration Planning 2021-03-29
Description
Sprint Planning Doc: https://docs.google.com/document/d/1uFw2snKuBlt2VirP5mjMvCr66HD7hOAB6QrXaElBZQE/edit?usp=sharing
Digital Experience handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/
A
B
You
know:
do
some
hot
jar
heat
map,
clip
click,
map,
sort
of
analysis
of
pages
that
are
our
top
five
and
you
know
kind
of
see
where
we
go
from
there,
and
this
is
just
an
issue
that
was
created
as
a
follow-up
to
kind
of
filter
out
some
of
the
data
like
basically
remove
the
the
site,
navigation
and
the
footer
and
a
few
other
elements
from
that
data.
So
I'm
just
setting
up
those
tests
again
shouldn't
you
know
it's
just
a
quick
issue.
B
I
spent
a
lot
of
time
gathering
historical
data
from
things
we've
done
in
the
past,
because
when
you're
in
gitlab
all
the
data
is
there
it's
just
very
fragmented,
and
so
it
took
a
long
time
to
find-
and
you
know
each
issue
has
a
different
standard
as
to
what
data
is
contained
within
so
yeah,
just
basically
getting
that
all
finalized.
This
sprint
is
kind
of
what
I'm
going
to
be,
focusing
on
and
yeah.
That's
it
for
me.
It
looks
like
tina
is
up
next.
C
The
top
five
pages
that
funnel
traffic
to
the
free
trials
page
and
work
on
some
recommendations
and
improvements
and
I'll
just
be
sticking
to
those
two
priorities
which
should
leave
me
enough
bandwidth
to
support
the
team
on
in
other
areas,
maybe
the
blog
and
other
things
that
might
need
my
attention
and
that's
for
me.
Next
is
tyler.
D
Yeah
I'm
coming
back
from
a
week-long
vacation,
so
I've
got
two
points
of
catch-up
from
the
time
off.
I
anticipate
that'll
kind
of
go
through
this
afternoon
and
tomorrow
morning,
maybe
a
little
bit
of
tomorrow
afternoon,
if
I'm
unlucky,
but
I
think
it
should
be
fine.
It
sounds
like
we
shipped
slippers,
blog
posts,
which
is
awesome,
and
I
want
to
take
some
time
and
like
write
about
it.
I
think
that's
important
and
do
it
while
it's
fresh
and
I
think
it'll
be
yeah.
D
I
think
it'll
be
really
good,
so
I'm
gonna
carve
out
some
time
for
that
early
on
too
this
week,
and
then,
after
that
it
sounds
like
we
have
a
ton
of
work
for
the
commit
event,
template
and
slippers
work,
cms
integration,
stuff.
I
don't
know
specifics
because
I
haven't
gotten
around
to
looking
at
things,
but
I'm
basically
just
pledging
the
rest
of
my
availability
to
working
on
that,
because
I
know
that
that
is
a
priority.
So
that
is,
you
know
the
rest
of
my
iteration
work
and
up
next
is
laura.
A
Yeah
so
similar
to
what
tyler
was
saying
I'll,
be
helping
out
with
the
events
template
for
the
commit
event
building
out
a
few
of
these
blocks.
I
linked
the
wrong
issues
here.
These
are
more
for
actually
implementing
them
in
our
www,
but
I'll
be
making
issues
and
then
working
on
those
issues
to
build
out
different
blocks
and
slippers.
E
Thank
you.
So
this
week
I'm
gonna
be
joining
our
bus
on
working
with
sleepers,
because
we
have
some
blocks
and
some
components
that
are
not
checked
already
on
sleepers.
So
we
just
created
an
epic
right
now
that
I'm
gonna
be
using
to
work
on
the
cards
on
the
cards
that
we're
gonna
be
developing.
So
from
us
sleepers.
E
I
think
I
I
link
to
grandfather
on
our
feed
man.
We
already
have
all
the
cards
that
are
ready
that
tuna
developed,
but
now
we
need
to
make
sure
that
they
are
ready
on
on
our
slippers
ui
so
that
we
can
start
using
them.
So
that's
the
first
thing
that
I'm
going
to
be
committing
to
so
that
I
can
get
myself
up
to
speed
with
avi
and
laura,
and
we
can
all
collaborate
and
work
together
on
steampunks
to
get
up
to
speed,
because
we
have
a
lot
of
components
that
are
not
yet
ready.
E
F
So
for
this
iteration
we
have
a
bruce
error
on
the
blog
template,
so
I'll
be
patching
up
that
we
have
an
issue
where
netlify
cms
branches
are
not
getting
deleted
after
they
emerged
with
master
from
the
ui.
So
gonna
fix
that
I'm
going
to
also
verify
that
when
you
publish
from
the
netlify
admin
that
it
adds
it
to
the
merge
train
and
doesn't
skip
it
because
that
could
be
would
be
bad.
F
I'm
also
going
to
see
if
we
can
get
the
merge
request
and
the
review
app
to
link
from
a
netlify
cms
draft
directly.
So
we
can
free
up
our
content
team
from
having
to
navigate
back
and
forth
between
the
uis
we've
got.
Our
blog
filtering
on
the
netlify
ui
is
painfully
slow.
So,
let's
see,
if
there's
a
way,
we
can
patch
that
up
to
make
it
really
nice
to
edit
blog
posts
and
view
them
all
in
the
admin.
F
F
And
then
I
have
a
point
for
the
whole
team
at
10,
which
I
think
might
be
close
might
be
more
to
build
our
commit
event
template
in
slippers,
and
this
means
building
out
all
the
components
we
don't
already
have
and
then
building
the
template
in
slippers
and
just
our
storybook.
So
we'll
aim
to
to
get
that
done
by
this
one.
G
Hello,
I'm
working
on
an
mvc2
of
the
footer.
All
it
really
is
coming
down
to
is
just
like
little
things
that
I
missed
that
I
didn't
have
time
for
in
the
last
iteration,
so
I
decided
just
to
call
that
an
mbc2
I'm
working
on
implementing
some
of
the
navigation
work
that
jess
has
been
very
diligent
in
working
with,
or
I
link
the
figma
file
there
or
what
the
thing
looks
like,
and
I
love
looking
at
this
just
because
this
looks
so
much
better
than
what
we
have
yeah.
G
I
am
going
to
actually
try
to
do
the
component
generator
that
I
told
myself
I
was
going
to
do
last
iteration.
I
scoped
it
down
a
little
bit
just
because
I
like
had
some
questions,
and
I
I
linked
an
issue
for
it
that
I
didn't
link
in
the
stock,
but
I
that
we
have
for
structuring
where
these
files
are
actually
going
to
end
up
being
generated.
G
We
might
restructure
the
repo
a
little
bit
to
see
like
there's
some
stuff
going
on,
essentially
we're
figuring
it
out,
and
so
I
sculpt
it
down
so
that
we
could
just
like
focus
on
what
is
actually
delivering
value
here,
so
click
on
the
dock.
Once
again,
I
want
to
have
a
grid
sync
discussion
with
design.
G
A
Thanks
avi,
so
for
me
this
week
I'm
gonna
try
and
run
some
usability
tests
on
our
current
free
trial,
page
just
to
kind
of
find
out.
What's
working,
what's
not
working
what's
missing,
what
do
we
have
too
much
of
all
that
good
stuff,
and
then
I
also
am
going
to
help
out
hobby
with
our
devsecops
survey,
landing
page
with
whatever
they
need
there
design
wise
and
that's
it
for
me
and
who's
up.
Next
stephen.
H
H
Everybody
sees
my
screen,
sweet
and
yeah,
so
we
just
ran
through
you
can
see
who's
here
on
the
meeting.
Some
people
on
this
call
were
there
and
we
just
went
through
a
couple
of
scenarios.
We
had
some
decision,
trees
worked
up
and
how
it
ties
in
a
little
bit
to
the
navigation
work.
So
there's
a
couple
of
to
do's
from
this,
which
is
kind
of
down
here.
So
this
is
the
stuff
that
I'll
be
tackling
this
spring,
been
in
a
couple
of
sprints
after
that
as
well.
So.
G
H
A
Jinx
and
then
I
see
that
we
also
added
a
sprint
name,
while
we
were
going
through
some
of
our
work,
which
I
believe
is
called
building
the
airplane
et
cetera,
because
we're
kind
of
building
out
our
commit
event
as
we're
riding
it.
It's
not
a
perfect
analogy.
I
don't
know
someone
could
jump
in
and
explain
if
they'd
like
all
right,
all
right.