►
From YouTube: 14.8 Ops Section R&D Retrospective Summary
A
Hello,
everyone
and
welcome
to
the
48
of
section
retrospective.
This
is
a
summary
video
where
we're
going
to
go
through
all
these
things
that
went
well
and
what
went
wrong
and
how
can
we
improve
in
the
op
section?
My
name
is
mitchell
torres
and
we're
going
to
go
through
this
slide.
So
I'm
sharing
my
screen
now.
A
And
we're
going
to
start
with,
14
8
was
released
in
february
22nd
many
amazing
things
happen.
We
have
around
25
plus
things
and
improvements
very
exciting
things.
We
have
deployments
approval
api
verify,
have
amazing
things
like
improvements
on
the
runner
in
the
pipeline.
Editor
and
patients
put
a
custom
right
limit
in.
We
have
some
release
badge
for
the
project
and
many
amazing
achievements.
There
deviates
we're
going
to
go
through
what
praise
do
we
have
for
the
team?
What
went
well
what's
been
grown
and
what
can
we
improve?
A
So,
let's
start
with
what
praise
do
we
have
for
the
team?
In
summary,
we
have
excellent
examples
of
collaboration
between
ux,
frontend
and
bucket
engineers
and
verify
between
multiple
backend
engineers
supporting
front
and
work
in
monitor
package
team
working
together
in
between
go
and
rails
engineers
and
release
with
the
onboarding
for
their
new
engineers.
We
also
have
in
pricing
cost
savings
and
improvements
on
our
budgets
with
verify
and
package
teams
and
runners
have
also
some
cost
savings
in
there,
and
we
have
some
examples
on
efficiency
and
transparency
on
what
when
well
this
milestone.
A
A
We
were
experimenting,
multiple
teams
with
different
areas,
which
is
exciting
to
see
all
teams
experimenting,
new
things
like
tracking
a
manual
way
for
the
seiju,
applying
kanban,
targeting
a
full
focus
on
one
epic,
in
the
milestone
or
even
planning
in
a
different
way
and
more
iterated,
the
myosin
planning,
and
we
can
see
that
the
results
were
amazing
and
that
we
became
more
efficient.
This
milestone,
what
went
wrong?
We
can
summarize
that
we
miss
some
dependencies
between
backend
and
front-end
and
that
we
miss
also
some
ux
research
before
following
issues
as
ready
for
development.
A
We
have
some
couple
of
regulations
and
reverbs
the
okay
air
planning
was
not
as
smooth
as
we
would
like,
and
we
had
some
engineers
posting
their
maintainering
work
and
community
reviews.
What
can
we
improve?
We
have
better
tracking
of
issues.
We
want
to
have
a
an
experiment
with
you
are
here
indicator.
A
In
general,
I
will
say
this
was
an
amazing
milestone.
I
can
see
from
all
the
teams
and
the
great
collaborations,
so
thank
you.
Everyone
we're
going
to
have
the
discussion
today
monday.
So
please
join
us.
You
can
see
the
meeting
today
at
12
est
17
utc,
you
have
the
england
agenda
and
you
can
see
all
the
topics
and
and
add
your
topics
also
there.
A
One
of
the
discussion
topics
proposed
for
today
is
how
are
we
measuring
diversity,
inclusion
and
belonging
value?
As
you
can
see,
we
normally
have
examples
of
collaboration,
results,
transparency,
but
we
don't
see
much
in
there.
So
I
would
like
to
discuss
on
that
one.
Please
make
sure
that
you
go
to
the
agenda
and
add
your
topics.