►
From YouTube: Product Analytics 15.6 frontend group retro
Description
In this call we discuss our experiences in the 15.6 milestone.
A
Okay,
there
we
go
hello,
everyone
welcome
to
the
15
6
product,
analytics
front-end
team,
retro,
that's
quite
a
mouthful
yeah.
This
is
going
to
be
our
first
Team
retro
as
a
front
end
group,
it's
something
Rob
and
I
did
frequently
in
compliance
or
other.
We
did
like
a
kickoff
that
was
both
a
retro
of
the
previous
Milestone
and
kind
of
planning
and
sinking
ahead
for
the
next
one.
That's
usually
the
white.
A
A
Oh
I'm,
seeing
a
thumbs
up
and
a
rope
that
looks
virtual.
In
that
case,
yeah
I
thought
we
could
retro
the
Milestone
board
and
look
at
basically,
you
know
what
was
what
is
the
items
that
are
still
struggling
left
in
you
know:
blocked
ready
for
development
and
in
development,
and
also
in
review
that
didn't
make
it
through
to
complete.
A
A
A
So
it
seems
like
he's,
happy
and
I
updated
the
dev
kit,
setup
instructions,
I'm
sure
everyone's
seen
this
by
now,
but
yeah.
That
was
quite
stale
and
wrong
in
a
few
places,
and
it
was
also
a
fun
experience
because
I
got
to
merge
this
myself
because
we
don't
yet
have
like
a
whole
approval
system
on
the
def
gate
projects
and.
B
B
Charts
has
found
that
it's
not
playing
how
it's
supposed
to
so
I'm,
currently
bashing,
my
head
against
the
wall,
trying
to
figure
out
why
that's
happening
and
then
my
main
task
throughout
this
entire
Milestone
was
being
a
designer,
a
mediocre,
slow
one
at
that,
but
a
designer
all
the
same,
so
I've
been
out
of
the
loop
with
what
everyone
else
has
been
doing
more
or
less
just
focusing
on
this.
The
designs
are
99
finished.
B
We
just
need
to
add
a
way
of
getting
back
to
the
tracking
codes
view
which
I'm
doing
right
now,
so
that
is
over
overflowing
the
Milestone
slightly
and
there
are
issues
attributed
to
every
single
one
of
the
views
that
we've
created.
Now
we
have
a
weekly
ux
with
Sam
just
to
go
through
the
ux
meeting
to
go,
go
through
ux
stuff
as
Sam,
so
he's
happy,
yeah
I
think
that's
everything
I've
done.
A
Yeah
Sam
promoted
this
to
an
epic
just
for
you
know,
I'm
sure,
you're
well,
aware
of,
but
just
for
the
recording,
just
sharing
that
it's
been
promoted
to
an
epic
and
yeah
here's
the
list
of
issues
that
we
have
for
the
onboarding
NBC,
and
so
it's
going
to
be
pretty
simple
because
we're
starting
out
with
those
pre-built
dashboards
and
we're
not
including
any
of
the
project
instance
management
or
projects,
dashboard
management
into
it
as
a
first.
The
milestone.
B
It
doesn't.
We
need
the
back
end
API,
so
we
can
run
queries
against
production
without
needing
to
hit
products
and
console,
but
the
UI
doesn't
necessarily
need
to
be
there,
but
we
do
want
it
there
shortly
after
to
prove
like
the
whole
flow
to
an
internal
stakeholders,
but
to
start
collecting
data
and
showing
dashboards,
we
don't
need
it
necessarily.
A
A
C
B
The
answer
to
that
is,
we
are
waiting
for
the
Jitsu
key
to
be
generated,
so
it's
meant
to
trigger
or
send
off
the
whole
Jitsu
process
generate
a
new
project
in
Jitsu,
tied
that
to
click
house
Cube
Etc
and
return.
The
key
that's
needed
for
the
Js
JavaScript
library
to
actually
send
queries
to
Jitsu.
So
we're
pretty
much
waiting
for
that.
We've
heard
me
and
Jan
had
a
conversation
with
Max
this
morning
around
how
we
can
know
when
the
back
end
is
actually
doing
that
process.
B
So
there's
going
to
be
a
a
redis
API
key
and
graphql
update
to
accommodate
that,
so
we'll
be
able
to
know
that
the
worker
is
working
to
to
stop
people
from
trying
to
create
multiple
instances
for
starters,
and
secondly,
also
so
we
can
progress
past
this
stage
as
well.
Once
we
have
that
key,
and
we
know
the
work
is
finished.
C
C
B
C
C
I
haven't
worked
a
lot
with
with
backend
or
Ruby
no,
but
not
for
not
saying
back
in
so
this
was
really
really
a
learning
process
for
me
and
and
a
really
good
teachable
moment
for
me,
because
I
got
this
a
bunch
of
reviews.
This
was
heavily
reviewed
with
with
requirements
like
things
to
fill
in
and
those
were
the
things
that
I
had
doubt
where
like
how
to
test
this
or
or
what
are
the
the
convention
that
we
have.
So
some
of
them
are
not
that
easy
to
discover
on
the
on
the
handbook.
C
A
Yeah
definitely
a
great
work
on
this
and
the
feature
spec
I
think
will
be
able
to
come
back
to
once.
We
have
the
actual
dashboards
connected
and
using
the
qproxy,
because
then
we
can
actually
verify
that
it's
you
know
using
the
correct
details
once
we
have
that
like
feature
worked
out
because
currently
it's
just
saving
it
and
you
know
I.
C
C
C
B
A
C
I
I
broke
it
in
like
a
few
months
in
and
it
was
a
really
visual
change
because
I,
because
I
use
flex
work
and
flexible
in
in
a
in
I
use
flexwork
in
a
container
which
only
have
inline
elements.
So
when
you
added
a
flexbook
element
it
it
removed
the
the
surrounding
space.
So
it
was
in
line
flex
and
in
line,
and
it
looked
awful
so
yeah.
B
C
B
That
that
documentation
only
refers
to
the
dashboards,
it
doesn't
refer
at
all
to
admin
settings
it's
sort
of
a
generic
product
analytics
page
and
right
now,
all
it
describes
is
how
to
create
a
dashboard
using
the
schema.
So
we're
also
going
to
need
we're.
Gonna
need
that
to
link
to
a
bit
that
talks
about
admin
settings
like
what
settings.
A
C
A
C
A
A
A
There
was
a
lot
also
to
take
in
and
then
also
setting
up
the
dev
cake
and
getting
it
all
working
and
some
blockers
along
the
way
that
Rob
has
graciously
helping
me
out
with
so
yeah.
That's
that's
pretty
much.
The
update
on
this
I
know
it's
super
important
that
we
get
this
unblocked
so
that
everyone
can
start
using
this
as
an
example
for
other
visualizations
going
forward.
A
B
I
guess
I
should
probably
also
mention
that
the
other
thing
is
the
blocked
issue
for
turning
this
on
for
the
internal
handbook,
obviously
we
haven't
got
sign
off
on
the
infrastructure
just
yet
so
that
hasn't
happened,
but
it
is
more
or
less
ready
to
go
so
we'll
see,
would
it's.
It
was
a
long
shot
before
it
hit
15
6
in
the
first
place,
so
yeah.
C
Yeah
from
my
side,
I
do
have
a
couple
of
issues
that
sleep,
the
Milestone,
but
those
are
basically
on
reviews,
so
I
didn't
mention
them
these.
This
was
like
a
like
a
I
I
I
I
talk
about
that
further
into
the
agenda,
but
yeah.
No,
nothing,
nothing
sleep!
Because
I
didn't
have
this
unimportant
delivery
so
deliverable
to
to
deliver
neither
like
any
important
blocker.
So
yeah.
A
A
A
A
This
is
just
like
something
to
keep
in
mind
is
to
keep
checking
back
to
like
Sam's
vision
for
the
the
two
demos,
the
internal
demo
and
the
first
user
demo
I
guess
that
can
also
get
confusing
and
that
gets
to
Rob's
points
of
like
you
know
it.
It
gets
confusing
because,
like
what
is
the
MVC
that's
being
discussed
in
in
a
given
context,
because
we
have
like
multiple
mvcs
with
multiple
targets
that
we're
trying
to
hit
so
I'll
segue
to
you,
Rob.
B
I
feel
like
the
true
MVC,
isn't
really
until
we
start
giving
it
to
customers,
because
before
that,
it's
before
it's
like
not
even
Alpha
at
this
point,
which
we
haven't
even
got
near,
Alpha
yeah,
I've,
I've
Echo
your
sentiment,
the
different.
We
need
to
be
better
at
making
sure
that
we're
in
alignment
in
those
Regard
in
that
instance,
especially
because,
like
I've,
been
doing
a
lot
of
design
stuff.
B
A
lot
of
that
has
is
several
Milestones
ahead
of
where
we
are
because
ux
has
to
be
built
and
prepped
for
future
Milestones,
not
right
now,
and
then
I've
also
been
in
serious
conversations
with
Max
around
back
end
and
talking
to
him
about
back
end
trying
to
be
a
counterpart
for
him,
because
he's
always
Lonesome,
which
again
is
a
milestone
or
two
ahead
of
front
end.
So
I'm
in
in
my
head,
I'm
about
for
I'm
spread
over
like
five
Milestones.
C
I'm
looking
forward
for
the
next
Milestone
planning
like,
and
this
is
basically
to
have
a
a
roadmap
laid
out,
and
this
is
something
that
I
have
been
looking
forward
to
inside
since
I
joined
team
like
we
started
with
a
with
a
general
direction
of
where
we
might
want
to
go,
and
now
now
we
are
like
a
bit
more
Square,
headed
and
I'm
really
excited
about
that.
So
because.
A
C
A
A
B
A
A
Our
thanks
I,
want
to
say
thank
you
to
the
both
of
you
for
when
I
joined
for
setting
up
that
front-end
recap
was
super
super
helpful,
something
that
I
referred
back
to
a
lot
throughout
my
first
like
a
week
or
two
here,
so
that
helped
me
a
lot
and
I
think
it's
also
going
to
help
future
team
members
that
are
on
board
so
yeah
thanks
so
much
rope.
You
have
the
next
one.
B
Jesus
the
prize
is
the
worst.
That's
the
worst
situation
of
the
section
for
for
a
British
person,
especially
me
I,
just
want
to
say
obviously,
I've
been
in
a
world
of
my
own
doing
design
stuff
I've
not
really
done
much
in
the
way
of
front
end.
This
Milestone,
so
I
really
appreciate
that
you
both
picked
up
the
front
end
task
kept
driving
the
team
forward.
Ask
our
group
forward
and
produce
some
excellent
work.
So
thank
you.
C
Yeah
and
from
my
side,
I
have
to
thank
you
both,
like
I,
had
a
couple
of
bad
weeks,
but
I
felt
like
pretty
supported
like
I.
It
happened
in
the
past
that
if
I
was
not
around
in
things,
didn't
move
so
so
yeah
I
mean,
and
that
was
of
course
a
source
of
stress
for
me,
so
yeah
yeah,
no
I'm
super
glad,
and
also
for
your
reviews
like
again
I
I,
not
I'm,
not
feeling
that
Rusty
now
but-
and
that's
also
thank
you.
Thank
you.
A
Yeah,
it's
it's
really,
it's
really
cool
to
be
part
of
a
bigger
team,
so
hopefully
we
can
continue
to
to
make
an
awesome
space.
My
last
thanks
is
also
just
for
I
mean
today
rob
you
were
a
big
help.
I
feel
like
stopping
what
you
were
doing
and
like
jumping
on
and
trying
to
unblock
me.
I
really
appreciate
that.