►
From YouTube: Digital Experience Iteration Planning 03/15/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
B
B
I
added
the
first
three
here:
the
sprint
timing
is
a
little
weird
because
it's
like
the
like.
It
ends
the
sunday
but
then
like
in
the
dock.
Here
it
ends
the
wednesday
and
like
starts
the
thursday,
so
the
days
are
a
little
off.
Maybe
I
will
make
a
message
or
ask
a
question
about
that
elsewhere.
So
I
included
the
first
three
items
just
because
I
did
them
at
the
end
of
last
week,
which
was
like,
I
think,
technically
part
of
this
iteration
and
they're
in
review.
B
Lauren,
and
I
had
worked
on
duplicating
the
existing
blog
styles
for
the
new
slippers
blog
component.
That's
been
been
reviewed,
one
stage
and
just
needs
an
engineering
review,
and
then
I
pushed
up
an
mr
for
like
conflicting
styles
and
resolving
that
which
also
need
to
review
along
with
an
image
gallery,
mr
as
well.
So
those
three
things
are
like
ready
and
like
kind
of
done
in
this
iteration,
but
maybe
last
iteration,
something
like
like
last
milestone,
but
this
iteration
and
then
I'm
on.
B
So
we
all
have
family
and
friends
day
friday,
I'm
on
pto
next
week,
so
I'm
just
gonna
wrap
up.
There
are
like
four
and
a
half
components
to
do,
which
is
just
the
pull
quote:
the
merch
banner
and
the
sidebar,
which
is
that
half
component,
because
it's
kind
of
the
same
but
kind
of
different
the
featured
image
for
the
blogs
and
then
just
like
some
of
the
link
styling
as
well.
B
So
that's
going
to
be
my
plan
to
like
get
that
wrapped
up
this
week,
so
that
we
can,
I
saw
lauren,
had
put
down
some
of
the,
like
blog
wrap
up
tasks
for
the
whole
milestone
and
then,
after
that,
if
I've
got
capacity,
I
made
an
issue.
Sonme
had
mentioned
in
slack
about
doing
like
a
workshop
on
slippers,
workflow
and
like
what
we're
thinking
about
using
and
stuff,
and
we
had
a
good
conversation.
I
think
in
retro
about
like
just
some
of
the
missing
docs
and
workflow
stuff.
B
So
if
I've
got
so,
I
made
an
issue
for
questions
to
like
work
on
them.
Async.
If
I've
got
remaining
capacity,
then
I'd
I'll
be
down
to
like
fill
out
some
of
my
thoughts
there.
But
if
I
don't
perhaps
that's
like
good
contents
on
me
for
you
to
like
build
your
workshop
off
of
or
collaborate
there,
so
yeah
that's
my
plan.
I
think
tina
is
up
next.
C
Thanks
tyler,
the
biggest
item
on
on
my
deck
for
the
consideration
is
the
template
event
templates
using
commit
as
a
use
case.
So
I
weighted
that
as
six
points,
because
we're
not
only
going
to
do
this
once
we're
going
to
create
a
set
of
templates,
as
I
said,
using
commit
as
a
use
case,
but
they
have
to
work
for
other
types
of
events
as
well.
So
it's
a
little
bit
more
involved
than
just
a
single
wireframe.
C
C
C
For
my
first
time
book,
page
update
and
last,
I
put
this
as
a
weight
of
one,
but
I'm
not
even
sure
it's
really
going
to
make
an
appearance
in
in
this
iteration,
but
we
did
apply
some
heat
mapping
to
a
couple
pages
and
once
those
come
in,
I
will
take
a
look
at
those
and
make
a
plan
for
next
steps
for
the
free
trial
user
journey.
Okr.
A
Yeah,
so
I
just
wanted
to
mention
you
know
everyone's
got
kind
of
different
amounts
of
sprint
point
capacity.
So
as
we're
weighting
these
you
know
keep
in
mind
that
one
person
might
have
20.
Another
person
might
have
10
and
you
know
do
keep
in
mind
your
you
know.
Pto
requests
also
impact
how
much
you
can
do
in
a
sprint
but
yeah.
A
So
the
first
thing
I'm
going
to
do
is
you
know,
get
an
access
request
filed
for
the
engineers
to
use
marketo
because,
as
we
realized
at
the
end
of
last
week,
I'm
the
only
one
with
access
to
the
system
at
the
moment.
Next
up
is
a
pricing
page,
a
b
test
follow-up.
You
know
we
we
did
one
recently
where
we
were
testing
the
table.
View
of
the
feature,
comparison
versus
kind
of
a
list
under
the
plans,
and
so
the
next
test
we're
gonna
do.
A
A
Obviously
we
want
to
record
what
we've
been
doing,
but
we
don't
really
have
a
single
source
of
truth
for
where
the
tests
where
we
can
go
to
look
at
to
find
the
results
of
tests
and
do
an
analysis
on
you
know
this
perform
better
or
worse
because
of
button
color
and
then
move
that
information
forward
into
a
repository
where
we
can
save
that
information
so
hoping
to
establish
that
in
the
figma
file.
This
is
based
on
some
research.
A
I
did
in
earlier
issues,
and
I
talked
about
it
with
stephen
so
kind
of
going
to
spend
some
time
getting
that
set
up
based
on
the
past
few
experiments,
we've
done
taking
screenshots
writing.
You
know
x,
y
and
z,
about
the
test
and
why
things
were
done
so
that'll
give
us
a
good
kind
of
footing
moving
forward.
D
D
So
I
finished
up
the
template
last
wednesday
and
aws
is
our
first
one,
that's
kind
of
what
we
used
for
the
template,
so
that
one
should
be
pretty
solid
right
now,
we're
just
waiting
on
kind
of
final
copy,
final
assets
and
one
once
we
have
those
it
should
be
pretty
easy
just
to
fill
in
all
the
others.
So
we
have
six
total.
I
don't
think
there's
any
particular
order
to
them,
but
we'll
fill
those
in
as
they
come
and
I
think
lauren's
next.
E
E
So
that's
going
to
take
a
lot
of
my
time
for
today
and
tomorrow,
there's
a
couple
slippers
components:
the
blog
header
and
breadcrumbs
slash
tags
that
we
will
be
adding
to
the
repo
an
issue
came
in
last
week
with
the
typeform
content
type.
There
aren't
any
real
good
instructions
on
how
to
build
your
type
form
in
typeform
and
style
it
and
then
embed
it.
E
So
I've
got
the
passwords
and
I'm
gonna
document
that
and
add
it
to
the
handbook
for
our
marketing
folks,
and
then
I
just
created
two
issues
here
for
me
and
tyler
for
to
actually
implement
the
new
slippers
blog
to
the
entire
blog.
That's
gonna
be
a
big
one
and
then
a
second
issue
for
catching
and
fixing
all
of
the
edge
cases
that
are
surely
going
to
come
up
and
that
one
might
extend
into
next
iteration
as
well.
D
F
Hello,
some
of
the
things
that
I
want
to
work
on
is
making
it
easier
for
people
to
contribute
with
slippers
and
one
really
cool
and
interesting,
and
not
super
hard
thing
to
do.
That
tyler
mentioned
was
having
like
a
yarn
script
that
essentially
lets
you
create
like
all
of
the
files
you
need
when
you
create
a
new
component
within
slippers.
That
way
you
you
know,
people
can
just
have
like
all
of
the
templated
things
that
essentially
are
just
copy
pasteable
ready
and
set
to
go.
F
I
think
that's
kind
of
like
a
developer
experience
type
thing
that
like
makes
it
easier
for
people
to
get
things
done
and
also
makes
it
so
that,
like
you,
don't
really
have
to
re.
You
don't
really
have
to
understand
what
storybook
does
for
you
to
like
use.
The
thing
which
I
think
is
like
a
point
of
a
pain
point
for
people,
because
it's
like
it
there's
a
anyway
storybook
is
complicated
and
I
don't
think
people
really
need
to
understand
how
it
works.
Butterwork.
F
This
is
stuff
from
last
iteration
that
I
didn't
have
time
to
do
this.
Could
this
could
be
a
rabbit
hole
that
I'm
like
pursuing,
because
I
think
that
some
of
the
questions
that
might
bubble
up
from
this
is
the
actual
creation
of
the
the
partial.
The
actual
creation
of
the
component
in
slippers
is
one
thing,
but
also
like
that
integration
plan
is
like
interesting,
because,
like
does
that
mean
I'm
making
a
partial
in
slipper
in
www.
F
G
Oh
sorry
thanks,
so
this
spring
I'm
going
to
be
working
on
the
highlighted
partners
page
which
may
carry
on
into
our
next
frame,
because
we
are
still
waiting
for
some
assets
that
jesse
is
still
waiting
for
for,
in
order
for
us
to
close
the
design
issue.
Well,
I'm
gonna
be
working
to
put
the
wireframe
and
everything
into
place
so
that
when
the
asset
comes
then
everything
comes
together.
G
Then
I'm
gonna
be
creating
some
more
six
related
issues
to
the
same
highlighted
partner
speech,
because
we
have
to
build
individual
six
pages
for
all
our
partners
and
I
think
we
have
six
of
them
presently.
So
that
is
what
I'm
going
to
be
working
on
this
friends,
then,
during
this
sprint,
we're
going
to
be
having
a
peer
programming
for
sleepers
for
sleepers,
avi,
laura
and
tyler
working
on
it
presently.
But
I
want
to
be
the
eyes
from
the
out
of
the
box.
G
I
want
to
be
the
second
pair
of
eyes
that
looks
into
everything
that
we're
doing
test
it
to
ensure
that
we
have
something
that
is
reusable
and
fits
into
the
criteria
of
the
things
we've
set
up
to
do
so.
The
last
thing
that
I'm
going
to
be
working
on
is
with
brandon
on
marketo
market
marketo
is
he's
going
to
be
getting
the
license
for
all
of
us
so
that
we
can
always
log
in
into
it
and
see
how
it
works.