►
From YouTube: Digital Experience Sprint Retro 2021-02-11
Description
Sprint Retro Doc: https://docs.google.com/document/d/1kMNiUF2UDuSrMDuzLyRi8OEhVxry_MJoYi38RmmWafY/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
Yeah
I've
said
this
a
bunch
to
like
in
different
contexts,
different
meetings
like
over
and
over
again,
but
it's
worth
reiterating
and
like
writing
down
in
a
retro
how
much
the
new
sprint
schedule,
bringing
like
the
design
system
and
cms
work
together
in
one
schedule.
Just
like
night
and
day
like
this
was
like
so
much
easier
to
manage
time.
B
I
felt
like
something
I
noticed
very
specifically
is
like
there
was
a
real
rhythm
to
the
sprint
for
me
this
time,
where
the
beginning
of
the
beginning
of
last
week
was
like
planning
some
synchronous
meetings
like
getting
set
up
moved
into
like
working
like
in
the
mid
and
late
week,
did
agency
day
work
and
then
the
start
of
this
week
was
a
lot
of
like
wrap
up.
I
started
to
see
more
like
either.
I
was
being
asked
to
review
things
or
other
people
were
reviewing.
B
A
I
think
I'm
next,
so
I
just
want
to
shout
out
to
tina
for
helping
this
morning
doing
some
peer
designing
on
the
partners
page
hero.
I
was
kind
of
stuck
on
something
and
she
just
like
wonder,
woman
right
in
there
and
with
the
correct
answer,
and
it
was
awesome
and
also
I'm
super
stoked-
that
we
got
access
to
optimal
workshop,
which
is
another
user
research
tool.
A
A
B
Yeah
we
talked
about
this.
We
did
a
workshop
on
boards
and
I
wanted
to
bring
some
ideas
back
here
to
things
to
improve
on
which
is
you
know
one?
How
can
we?
How
can
we
use
boards
better?
So
hopefully
we
can
integrate
them
into
sprint
planning
and
that
will
require
no
like
extra
work,
just
to
change
a
little
bit
in
how
we're
working
but
resolve
some
challenges
there.
B
I
think
we
could
get
better
at
like
issue
waiting,
but
I
wonder
if
this
will
come
through
better
use
of
the
boards.
I
know
like
starting
out
the
sprint.
I
thought
that
maybe
I
would
have
too
much
on
my
plate
and
then
by
like
the
mid,
the
middle
of
it,
I
was
like.
Oh,
I
might
even
be
done
early.
So
I
know
time
estimation
like
is
always
like
it's
there's
no
solution
to
it
right.
B
B
I
think
we've
had
some
conversations
in
slack
and
I
think
down
in
the
document
about-
and
we
talked
about
it
last
time
about
including
agency
day
work
in
planning
and
releases.
I
thought
that
like
if
it
was
well
contained
to
one
day
I
was
like
we
shouldn't
include
it.
I
have
definitely
changed
my
opinion
because
I
just
don't
think
any
of
this
work
will
ever
be
contained
to
one
day,
but
I
think
it's
also
useful
to
flag,
because
I
think
maybe
we
should
not.
B
There
may
be
some
expectations
setting
internally
or
like
collaborating
with
other
teams
about
like
what
does
constitute
agency
day
work
and
like
what
is
an
appropriate
scope
and
like
what
will
hap
what
are
the
implications
for
work
outside
of
that
day,
because
it
seems
to
be
in
from
listening
to
other
folks
like
there
are
implications
outside
of
that
one
day.
So
yeah
just
things,
I
think
that's
about
it
and
javi's
up.
D
D
I
think
that
will
be
more
clear
with
within,
like
our
new
cadence,
but
there's
like
a
point,
where
kind
of
how
tyler
was
saying
like
the
sprint,
like
tapers
off
the
more
stuff
that
you
do,
which
is
great
because
there's
like
things
that
I
can
do
that
are
small,
but
I
wish
there
was
like
kind
of
like
a
prioritization
of
that
done
beforehand,
just
so
that,
like
after
I
finished
the
work
that
I
said,
I
was
gonna
do
the
sprint.
I
have
other
things
by
order
of
importance,
rather
than
just
like.
C
And
I've,
I
just
want
to
say
I've
had
kind
of
a
similar
experience.
I
you
know.
Similarly,
my
milestones
I
planned
out
months
in
advance
and
it
wasn't
working
because
you
never
knew
what
you
were
going
to
be
working
on
and
how
much
time
and
all
that,
and
so
I
kind
of
came
to
a
similar
conclusion
as
lauren
for
myself
personally,
one
of
the
things
that
I
have
been
doing
is
basically.
C
Now
that
we're
using
epics
more
clearly
as
a
bucket
of
work,
as
opposed
to
like
here's,
where
we
are
here's
where
we
want
to
go
it's
more
of
like
here's,
all
the
things
related
to
this,
I'm
almost
using
epics
kind
of
like
a
board
right
like
I
know
this
sprint.
We
want
to
be
working
on
the
cms,
so
I'll
pull
up
the
cms
epic
and
look
at
the
work
that
remains
to
be
done
and
start
working
on
it.
C
That
way,
I
know
that's
not
ideal
and
that's
not
where
we
want
to
go
necessarily
and
we
need
to
evaluate
boards
in
our
workflow,
but
that's
just
I
figured
I'd
put
in
my
two
sense
of
how
I've
been
working
lately
and
I
appreciate
what
has
been
done
with
the
epics.
So
I
just
figured
I'd
mention
those
two
things.
I
had
a
follow-up
just
to
what
you
said.
D
That's
an
interesting,
I
never
thought
of
doing
it
that
way,
but
I
would
be
interested
to
play
around
with
the
idea
in
terms
of
setting
epics
in
regards
to
sprints,
as
so
much
like
bodies
of
work
that
are,
you
know
like
need
to
be
structured
out
just
because
I
think
it
makes
more
sense
to
the
work
that
we
do
and
it's
easier
to
organize
that
information,
but
yeah.
We
can
have
like
a
broader
discussion
of
that.
Maybe
during
the
call
after
the
call,
I
don't
know
just
thoughts.
I.
F
F
In
my
next
I'm
next,
the
this
is
kind
of
a
classic
problem
to
solve,
but
figma
file,
delivery
and
handoff
to
engineering
could
be
a
little
bit
smoother
and
I'm
realizing
now
that
we're
a
new
team
and
we've
never
actually
had
this
discussion.
So
I
think
it's
going
to
be
a
really
easy
thing
to
solve,
and
I'm
volunteering
myself
to
either
create
a
survey
or
a
workshop,
or
something
like
that
to
solve
that.
C
A
F
We
definitely
have
to
iron
that
out,
because
I'm
realizing
that,
once
an
agency
day,
project
gets
reassigned
to
whomever
is
building
it
there.
Sometimes
it's
in
a
new
issue
and
can't
be
expected
to
read
all
of
the
conversations
that
happened
in
the
wireframe
or
design
issues.
So
we
need
to
find
a
way
to
pull
those
key
pieces
of
information
out.
A
Yeah,
so
I
just
had
a
lot
of
last
minute
changes
this
sprint.
My
original
plan
for
this
print
was
to
do
navigation
work,
and
I
only
had
to
do
one
day
of
that.
So
I
don't
think
it
was
like
any
particular
fall.
That
might
just
be
like
a
weird
sprint,
but
we
had
like
the
pricing,
page
changes
or
all
of
a
sudden,
and
then
the
agency
day
work
took
too
long
and
then
another
agency
project
got
turned
into
a
normal
project
and
got
prioritized.
A
So
I
don't
really
know
what
to
do
about
that,
but
it
just
obviously
was
not
what
I
was
planning
to
do
and
since
heart,
just
it
was
hard
to
plan
for
something
when
so
many
changes
are
coming
at
you,
and
so
many
priorities
are
shifting
so
quickly.
So
I
just
thought
I'd
call
that
out
hobby.
Thank
you
next.
C
So
he's
asking
you
know
he
should
handbook
contributions
be
a
more
regular
occurrence.
I
encourage
everyone
to
contribute
to
the
handbook.
I
know
that
it's
a
bit
of
a.
Where
do
I
start
sort
of
a
situation,
but
we
can
all
definitely
review
the
digital
experience
team
page,
even
the
inbound
marketing
page
and
just
go
over
and
look
at
things.
C
B
We
want
to
like,
because
that
stuff
is
supposed
to
expire
and
it's
gone
in
90
days,
so
you
shouldn't
assume
you'll,
be
able
to
go
back
and
get
the
answers
there.
So
yeah.
I
think,
starting
with
him.
We
talked
about
this
too
in
like
the
boards,
like
start
with
the
mr.
So
if
you've
got
a
question
about
stuff
that
needs
to
be
permanently
answered,
like
make
an
mr
about
it,.
D
D
I
think
that
there's
a
lot
of
times
where
it's
like,
we
should
document
this
and
it
ends
up
just
like
being
left
in
an
issue.
So
maybe,
if
there's,
I
think,
we've
talked
about
this
a
little
bit
with
our
board
discussion
about
like
the
deliverables
for
things
being
contributions
to
the
handbook.
I
think
that
would
solve
itself,
but
I
still
wanted
to
call
that
out
explicitly
because
that's
something
that
I've
been
thinking
about,
because
things
often
get
out
of
date
really
quickly
with
the
handbook
and
so
trying
to
figure
out
what
that
looks
like.
D
I
also
have
the
next
point
on,
like
kind
of
the
question
of
if
people
are
aware
that
our
agencies
days
are
only
like
were
planned
to
only
be
on
friday.
I
am
my
instinct
is
to
say
that
that's
not
super
clear
because
of
the
expectations
that
I
think
other
people
have
and
based
on,
like
how
we've
been
working
outside
of
our
own
regular
agency
studies
to
get
work
done.
F
A
Okay
yeah,
I
was
just
going
to
say
similarly
a
lot
of
my
agency
day.
Work
hasn't
been
over
the
right
friday,
like
we're
only
supposed
to
do
it
every
second
friday
after
a
sprint
is
finished
like
tomorrow,
but
I
also
noticed
that
a
lot
of
the
parts
that
come
in
on
my
agency
work
the
content
and
the
photos
and
the
assets
and
the
whatever
they
also
were
given
tomorrow,
to
do
it
like.
A
So
now,
I'm
like
ready
to
build
a
page
and
there's
just
nothing
there
for
me,
because
everyone
has
the
same
due
date,
but
I
need
that
stuff
before
I
kind
of
start
building
it
and
and
then
we
start
getting
these
back
and
forth
and
it
drags
on
for
a
few
more
days.
So
I've
definitely
noticed
that
also.
E
I
will
add
to
that.
It
came
up
with
the
campus
page.
Last
friday
I
looked
at
it
and
I
saw
that
tina
had
like
just
finished
the
issue
like
that
morning
and
there
was
a
huge
thread
of
information
to
go
through
and
I
was
like
okay,
no,
I'm
not
gonna
like
I
need
more
than
you
know
one
hour
of
that
this
morning.
So
it.
C
And
then
I
was
just
gonna
say
also
when
I
did
that
exercise
that
I
mentioned
earlier
planning
my
calendar
out
for
kind
of
the
sprint,
and
you
know
blocking
out
times
and
stuff
like
that.
I
realized
that
it's
not
just
that
agency
day
is
friday
right.
It
was
hinted
at
earlier.
Basically,
you
go
to
release
something
and
you
need
a
review
and
no
one's
there
to
review
it.
So
the
date
slips
to
oh.
C
You
know
first
thing
monday,
assuming
that
there
aren't
revisions
to
be
made
right
like
if
it
goes
through
design,
review
or
code
review
monday
morning,
and
then
it's
gotta
make
code
changes.
Then
you
gotta,
do
it
again
so
realistically,
agency
day
is
not
you're
working
for
the
whole
day.
It's
you're
spending
that
thursday
afternoon
prepping,
which
is
not
ideal,
but
you
know
that
seems
to
be
what
we're
all
doing.
C
Friday
morning,
you
go
to
get
started
middle
of
the
day
friday.
Maybe
you
send
it
for
review
and
then
it
gets
reviewed
so
like.
Basically,
you
only
have
a
quarter
of
a
day
at
most
to
do
that
agency,
work
and
if
to
lauren's
point
you
get
your
stuff
to
start
on
friday,
then
you're,
also
behind
that
quarter
of
a
day
where
you
were
planning
on
thursday
or,
however
long
you
do
so,
I
don't
know
that
one
day
is
a
realistic
number
for
agency
day.
C
F
B
I
think
like
brandon
says
something
there
about,
like
appropriate
like
a
day
may
be
an
appropriate
amount
of
time,
but
it's
not
the
like.
I
think
that
blocking
off
one
specific
day
to
do
the
work
is
also
not
like
async
first
right
and
saying,
like
oh,
like
agency
day,
work
happens
here,
it's
like
not
great
for
us,
because
it
puts
us
in
this
weird
place
where,
like
information,
gathering,
execution
and
review
has
to
happen
in
one
day.
E
C
Personally,
if
I
can't
put
an
item
on
my
calendar
and
block
out
all
other
things,
then
I
cannot
be
focused
on
that
one
thing
so
like
I
would
not
get
any
agency
day
work
done
unless
it
was
on
agency
day.
I
didn't
set
this
theory
up,
that
we've
been
working,
but
it's
been
working
out
for
me,
but
I
totally
get
that
why
it's
not
working
out
for
some
of
y'all
and
so
their
flexibility
is
always
an
appreciated
thing.
C
Oh
so
it
sounds
like
we
have
a
lot
to
review
for
agency
day
and
sprint
boards
and
other
things.
I
don't
want
the
call
necessarily
to
go
on
too
much
longer,
because
I
know
we
all
have
things
to
do,
but
if
there
are
any
closing
thoughts
on
this
or
any
other
topics
that
we
want
to
discuss
great,
let's,
let's
hear
them
otherwise
looks
like
I'm
getting
some
blank,
stares
and
nodding
heads
for
the
moment.