►
From YouTube: Product Marketing DEX | Iteration Planning 2023 02 13
A
Everyone,
this
is
our
iteration
plan,
sync
meeting
for
the
product,
Marketing
Group
on
digital
experience
for
February
13th
Tina
is
out
but
I'll
hand
it
over
to
fails
out
to
kind
of
speak
through
what
Tina's
working
on
this
iteration.
B
So
Tina's
working
on
a
few
things
and
a
few
things
are
blocked
by
for
a
stakeholder
review.
So
the
first
one
is
incubation.
The
incubation
engineering,
page
Lorena,
just
messaged
me
and
said
some
of
that
will
be
delayed
by
about
a
week
as
some
of
the
stakeholders
are
in
scope.
So
we
won't
be
getting
feedback
this
week.
B
The
startup
solution,
page
we
have
design
ready
copy,
is
ready.
We
just
need
the
final
check
from
Lorena's
side,
which
she
said
she'll
provide
by
end
of
day
today
and
that
will
be
ready
for
engineering.
Then
the
customer's
case
studies
summer
thing
we're
waiting
on
a
bit
of
stakeholder
review,
but
ideally
we
get
that
soon.
So
we
get
a
first
iteration
in
this
iteration,
it's
a
lot
of
iteration
and
then
the
security
page
MVC
one.
B
That's
primarily
engineering
heavy,
but
Tina's
gonna
work
this
early,
this
iteration
just
to
break
that
down.
So
there's
some
issues
to
pick
up
for
the
engineering
team
and
then
Tina's
also
supporting
the
search
nav
support
team
in
a
couple
of
things.
But
we
can
discuss
that
in
that
team.
C
Thanks
I'm
all
over
the
place
consideration,
we
still
have
some
ongoing
work
with
infrastructure
and
smartling
over
the
fastest
stuff,
but
I
think
Lauren's
gonna
take
point,
maybe
for
this
iteration
just
so.
He
neither
of
us
go
crazy,
trying
to
trying
to
work
on
it
and
then
there's
some
redirects
work
that
needs
to
get
done
and
then
I
think
just
last
iteration
the
product
team
stopped
using
PPS
scores
and
features
yaml,
and
so
they
asked
if
we
could
remove
it
from
that
file
and
I
found.
C
There's
only
one
place,
we're
using
it
still
in
buyer
experience,
so
I'll
just
remove
it
from
that
one
file
and
then
it'll
get
rid
of
like
3000
lines
from
features
the
ammo,
which
will
be
awesome
and
then
yeah.
If
there's
any
leftover,
I
think
there's
some
documentation.
I
have
lingering
that
I
haven't
done,
that's
been
carrying
over
and
then
maybe
work
on
the
next
three
epic
or
try
and
figure
out.
C
D
Hello
thanks
Nathan,
this
iteration
I
have
one
small
issue
from
let's
kind
of
carry
over
ish
from
the
last
iteration,
the
slippers,
devops
stage,
icons,
I'm
gonna
go
ahead
and
rename
some
of
those
because
essentially
we're
using
more
complicated
logic
than
we
need
to
in
some
of
the
templates,
so
I
think
just
renaming
the
icons
would
just
fix
some
of
that.
That's
it
for
me
that
I
have
scoped
I'll,
be
happy
to
jump
onto
other
things
as
they
come
up.
Ups
next
is
Margaret.
E
Yep,
so
for
the
situation
now,
I'm
gonna
be
working
on
factoring
the
software
faster
Carousel
component
to
fix
some
issues
with
the
previous
data
layer.
Besides
that
I'm
just
open
to
working
in
any
other
issues
that
may
come
up
in
the
future,
yeah
I
think
that's
it.
For
me,
next
is
material.