►
From YouTube: Digital Experience Iteration planning - May 10, 2021
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
All
right
welcome
everyone
to
digital
experience,
sprint
planning
for
the
week
of
starting
or
for
the
cycle
starting
may
10th.
Today
we're
going
to
be
working
towards
trying
to
get
some
event
pages
going
so
I'll
go
first.
First
items
I'm
going
to
be
working
on
is
the
pricing
page.
A
There
was
some
there
were
some
issues
with
basically
handoff
of
triage,
and
so
when
you
get
started
and
go
through
the
backlog
of
triage
and
things
like
that,
so
yeah,
oh
and
then
also
some
analyst
page
updates
as
well
and
then
looks
like
next
up
is
lauren.
B
All
right
so
for
this
iteration
we
have
a
follow-up
of
the
event
template
for
slippers
to
do,
and
so
I'm
going
to
work
on
patching
up
our
copy
block
in
our
event
cta.
So
they
all
line
on
the
the
same
grid
and
then
I'm
going
to
shift
over
to
actually
building
the
components
in
the
www,
repo
and
so
I'll
work
on
shipping.
B
The
copy
and
image
block,
the
cta
event
block
cards
and
the
connect
block
we'll
get
those
all
patched
up
in
dub,
dub
dub,
and
then
I
have
a
point
for
booting
up
with
the
get
lab
code
base
and
firing
that
up
on
machine
and
that's
part
of
the
okr
working
towards
adding
the
footer
to
the
product.
B
Then
we
have
a
blog
categories,
seo
error,
so
I
added
pagination
to
our
blog
category
pages
and
there's
an
seo
error
that
occurs
where
they're,
using
the
the
same
description
for
every
tabbed
page.
So
I'll
go
and
fix
that,
and
then
I
had
them
turn
on
the
feature
flag
for
epic
boards
for
inbound
marketing.
So
I'm
going
to
get
in
there,
try
it
out
and
provide
some
feedback
on
that,
because
epic
boards
could
be
really
cool
over
to
tina.
C
Thanks
so
I'm
going
to
prioritize
project
planning
for
cross-functional
support
initiatives,
okr
so
specifically
I'll,
be
focusing
on
information
gathering
for
this
iteration
for
the
comparison,
localization
and
partner
portions
of
the
epic,
so
that
I
can
kind
of
get
caught
up
and
start
collecting,
reviewing
and
assigning
issues
and
creating
epics.
C
I've
also
set
some
some
time
aside
to
support
with
commit
and
the
events
page
cms,
I'm
going
to
work
with
javi
to
get
an
issue
started
to
house
our
efforts
to
improve
our
collaboration
or
team
internal
team
collaboration
so
that
we
can
keep
that
conversation
going.
And.
Lastly,
I'm
gonna
update
the
handbook
to
include
our
figma
file
handoff
process,
and
that's
it
for
me
for
this
iteration
tyler.
D
Yeah
I've
got
some
wrap
up.
I
had
sort
of
like
poked
into
a
few
small
like
seo
things
with
our
no
with
our
site
map
and
some
localization
attributes,
and
so
I
just
picked
up
those
issues
from
the
unassigned
column
today,
so
that
I
could
close
them
out
this
iteration.
But
beyond
that,
the
rest
of
my
capacity
is
just
event
template
just
keep
on
keeping
on
looked
at.
I
like
think
we
might
be
able
to
close
out
step
two
and
a
half
and
three
like
heads
down
this
iteration.
D
We
might
still
be
at
risk
on
that
third
step
coming
up,
even
with
all
my
available
time
going
there.
So
yeah,
laura
you're
up
next.
E
Thanks
yeah,
I
set
aside
some
time
to
do
a
bit
of
okr
planning
for
the
inquiry
to
free
trial.
Okr
jess
has
already
done
a
lot
of
investigating
and
adding
tickets
to
okr.
I
just
want
to
look
at
some
of
the
engineering
lift
for
that.
I
also
grabbed
one
of
the
unassigned
pieces,
which
was
the
partners
page
templates,
a
few
fixes
for
that
which
should
be
fairly
small,
and
then
I
also
want
to
keep
my
head
down
and
do
some
events
template
work.
So
I
grabbed
a
few
of
those
blocks.
E
F
Hello
due
to
popular
demand
before
this
call,
there
is
a
desire
and
want
for
there
to
be
an
engineering
navigational
epic.
So
I
went
ahead
and
created
one,
as
this
call
was
happening
in
terms
of
like
the
work
that
I'm
doing
this
iteration
with
that
there's
some
stuff
with
the
styling
that
still
needs
to
be
worked
on,
specifically
the
drop
down
navigation
for
css.
At
the
desktop
query.
F
This
will
lead
to
like
having
to
modify
slightly
how,
like
the
data,
is
being
brought
in
from
that,
because
we
have
like
the
segmentation
across
different
sections,
yeah.
Okay,
this
will
lead
us
to
work
with
slippers,
only
layouts
in
the
www
repo
and
then
eventually
merging
this
into
the
repo
I'm
gonna
try
to
see
if
we
can
just
drop
this
in
and
see
what
happens.
F
If
this
ends
up
not
working
out,
I
will
probably
have
to
consult
tyler
in
terms
of
like
understanding
how
to
use
web
component
technology
to
get
all
of
this
stuff
to
work.
That's
like
the
navigation
stuff.
I
put
up
scoping
of
eight
just
because
I
anticipate
this
to
take
a
lot
of
my
effort.
I
have
one
point
set
down
for
handbook
changes
specifically
with
collaborating
with
outside
teams.
Over
the
weekend
I
was
listening
to
this
audiobook
for
a
mike
monterey
book
for
a
book
called
design
as
a
job.
F
I
think
there's
a
lot
of
stuff
in
that
that
I
could
just
straight
copy
and
pull
and
reference
in
the
sprint
planning
document.
I
have
the
pdf
to
the
entire
book.
If
people
are
interested,
I
don't
know
if
that's
like
legal,
but
whatever
it's
there.
I
also
wanted
to
have
like
something
in
terms
of
quarterly
planning,
because
it
seems
like
there's
stuff
that
we
do
and
we
should
say
that
we
do
them
somewhere
so
and
I
had
written
that
down
in
the
retro.
F
But
I
don't
remember
like
what
context
that
was
in,
but
I
just
figured
that
I
would
throw
that
in
there.
I
have
one
point
for
trying
to
get
engineering
work
aligned
closer
to
figma
foundations.
I
have
a
ton
of
work
already
done
in
this
already,
specifically
like
working
with
like
the
inset
variables
within
tailwind,
which
is
inc,
which
is
like
top
left
right
right
now,
that's
not
aligned
with
like
the
way
that
we've
spaced
things
now.
F
What
is
it
called
container
aligned
with
our
grid,
and
I
can
link
documentation
to
container
within
tailwind
but
like
getting
that
tailwind
container
utility
to
align
with
our
own
grids,
I
think
is
like
a
good
thing
for
us
to
have
just
because
at
least
I've
been
using
it
and
it's
unfortunate
when
those
two
things
don't
align.
So
that's
it.
For
me
up
next
is
jess.
E
Thanks
the
first
thing
there
for
me
is
the
next
iteration
of
the
pricing
page,
which
is
just
kind
of
like
a
contact
sales
call
out
and
it's
already
started.
We're
just
kind
of
a
waiting
copy
should
be
a
quick,
quick
one,
and
then
I'm
gonna
put
an
asterisk
on
my
next
one,
I'm
hoping
to
do
user
research
for
the
free
trial,
signup
forms,
but
there's
some
question
about
how
to
actually
do
that.
So
it
could
end
up
being.
E
The
reverse
could
have
been
doing
that
this
is
the
excuse,
doing
the
design
first
and
then
kind
of
researching
on
a
prototype
afterwards,
so
tbd,
but
one
of
those
and
but
my
last
thing
is
just.
If
I
have
time
I
still
need
to
do
the
research
readout
for
the
product,
slash
devops
page,
which
I
did
I
think
in
march,
was
the
actual
user
research
just
kind
of
when
I
get
the
time
so
and
then
stephen
you're
up
next.
G
Yeah,
my
first
one
is
my
okay,
our
planning
breaking
out
the
15
pages
into
issues
so
they're
a
bit
more
manageable.
So
it's
not
a
huge
mountain
to
decline
and
I
say
the
spices
are
correct.
G
I
felt
that
wrong.
Excuse
me
yeah
so
doing
that
and
then
there's
a
issue
open
at
the
minute
for
in-line
link
styling,
so
we're
adding
that
to
repo
making
sure
that
that's
all
good
and
reflected
in
figma
and
then
my
q1
okr
still
has
some
work
in
it
and
I'm
just
seeing
how
that
transfers
over
to
q2.
So
I
have
to
do
a
bit
of
looking
into
that
with
michael
as
well,
and
that's
it
for
me.
A
So
everyone,
thanks
for
stopping
by
and
listening
to
us
plan
good
job.
Everyone
have
a
good
week
or
cycle
later.