►
From YouTube: Magento PWA Backlog Grooming, 16 November 2018
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
thank
you,
sir.
So
let's
go
and
get
started
here,
so
we've
got
a
couple
items
too.
It's
a
cover.
We'll
put
this
on
record
for
folks
who
are
following
along
remotely,
so
welcome
to
grimming
is
their
last
grooming
before
before
Thanksgiving
break
for
those
of
us
here
in
the
u.s.
we've
got
three
items
to
cover,
namely
some
developer
documentation
here.
So
mr.
Calculon
is
gonna
cover.
A
Some
discovery
work
on
account
details,
and
so
for
those
who
were
here
last
week,
we
we
did
some
some
early,
some
early
work
on
ratings,
and
we
did
some
early
work
on
on
wish
list
for,
after
after
our
MVP
after
our
2.3
release,
just
to
really
start
thinking
what
that
authenticated
experience
looks
like
and
so
AHA
so
anxious
to
get
through
that
and
really
get
some
some
feedback
and
some
initial
sizing
ahead
of
the
the
UX
work
there.
So
as
always,
thank
you.
Everybody
for
attending
and
let's
go
ahead
and
get
started.
A
A
B
Okay,
so
what
I
think
we
kinda
talked
about
this
last
week?
You
know:
what's
the
simplest
thing
we
can
have
people
make,
and
you
know
the
usual
is
a
hello
world
kind
of
project
and
I.
Think
the
simplest
thing
we
could
ask
them
to
do
is
a
hello
world
react
component
like
something
that
will
print
out
hello
world
as
a
is
this
function,
and
a
second
step
to
that
would
be
to
actually
integrate
that
into
venya,
somehow
put
that
somewhere
in
vineya
and.
B
And
after
that,
the
next
you
know
task
we
would
ask
them
to
do-
is
implement
a
CSS
module
to
give
that
component
style,
and
then
we
factor
it
so
uses
props
like
setting
the
text
size
and
color.
This
will
just
be
like
the
beginner,
a
beginners
kind
of
tutorial
right.
These
are
pretty
simple
basic,
that's
it
most
developers
would
already
know
or
are
able
to
pick
up
for
easily
yep
and.
A
B
B
Another
thing
that
a
beginning
topic
would
be
integrate
Peregrine's
component
into
their
own
component.
I
know
we
have
price
and
lists
which
are
pretty
simple.
That
could
be
easily
integrated,
I
would
think
and
then
creating
a
storybook
test
would
be
another
thing
kid
we
could
have
do
as
a
tutorial
that
we
had
documentation
already,
but
yeah
make
it
part
of
that
tutorial
of
the
beginning
for
a
beginner
yep.
A
Yeah,
let
me
good
thing
the
link
to
as
well,
so
that
makes
sense
no
I'm
mr.
Calculon,
the
on
on
these
I'm
looking
through
this
and
you've
got
some
good
suggestions
on
content
here
between
HelloWorld
CSS
module
and
such
are
these
ones.
You'd
like
to
note
in
here.
You
just
want
to
kind
of.
Are
you
kind
of
putting
them
out
there
for
discussion
to
see?
If
there's
not
it
see,
that's
valuable
cuz.
You
know
you
know
there
would
be
great
things
to
add
here
if
we
feel
like
they
are
both.
C
A
C
Feel
like
yeah
there's
so
many,
and
it
would
take
me
some
time
to
think
about
what
should
be
top
level
and
how
to
group
them.
If
there's
anything
that
I
think
if
there's
anything
that
I
think
is,
is
basic
and
kind
of
missing
its
how
to
use
venía,
Peregrine's
and
Bill
pack
as
NPM
dependencies
rather
than
through
what
so
far
has
been
our
developer
use
case,
which
is
to
clone
the
PWA
studio
repository
itself,
mm-hmm
yeah
I'd
say
how
to
use
them
as
video
dependencies
I
and
working
with
the
cloud.
A
Yep
that
makes
sense.
Yeah
I
mean
one
I
think
when
we
we
only
look
at
this,
and
we
can.
We
can
expand
it.
We
thought
about
what
would
their
tak
what
those
tasks
might
be
after
configuration
instead
of
but
I
think
there's
a
it
seems
like
there
might
be
a
build
component
if
I
understand
correctly,
that
that
might
be
might
be
helpful
there
once
that's
once
that's
done
right
and
so.
C
D
C
Enzyme
ingest,
you
use
mattress
under
certain
circumstances,
I
mean
a
lot
of.
It
is
just
learning
to
do
testing,
but
I
think
we
might
also
like.
Presently
we
have
mostly
unit
tests
and
I
think
it
might
be
a
good
idea
to
start
encouraging
people
to
add
integration
and
scenario
tests
which
test
at
the
level
which
you'd
store
those
tests
in
the
Fenian
base
directory.
Then
they
would
prefer
to
workflows.
B
B
A
A
Look
at
you
know
maybe
one
to
three
point
types
of
stories
that
fall
into
that
as
we
as
we
get
through
that,
and
so
that's
probably
the
next
step
of
that
there's
you
know,
have
you
do
do
it
here
live,
but
nobody
wants
to
sit
here
and
watch
me
type
for
that
one,
so
I'll
break
these
out
and
James
I'll,
probably
Calculon
lean
on
you
to
help
a
little
bit
with
some
of
estimates,
and
these
then
become.
Actually
you
know
in
the
spirit
of
identifying
things
that
are
helping
you
to
for
the
community.
A
E
A
Alright,
we
get
ourselves
an
epic.
Thank
you,
everybody
all
right,
let's
switch
gears
here.
So
mr.
zetlen
stop
using
first
names.
We
just
confuse
each
other
with
something
change
I.
So,
let's,
let's
take
a
look
at
what
you've
got
here.
I,
don't
know
if
you'd
like
to
share
yourself
and
kind
of
make
some
modifications.
If
you'd
like
me
to
do
so,
I'm
happy,
oh.
C
No,
it's
it's
as
it
should
be
it.
If
we
come
to,
then
I'll
go
ahead
and
edit
myself
and
you
can.
You
can
refresh
whatever
sharing
my
screen.
I,
don't
know,
I'm
like
on
the
Wi-Fi
and
a
little
room,
I'm
worried
and
the
lighting
is
terrible.
I
mean
you
know
when
these
things
are
for
meetings,
I
feel
like
backlighting,
you,
everyone
just
looks
like
a
ghoul.
It's
the
worst
I'm,
not.
E
C
I'm
just
concerned
about
reading
facial
expressions.
Okay,
now
that
that's
out
of
the
way,
we
need
to
add
some
instrumenting
that
is
code,
that
meta
analyzes
other
code
of
runtime
to
venía
and
peregrin
into
our
react
components
in
framework
in
general.
So
that
end
end
testing
is
possible
most
of
the
time
with
client-side
applications.
I
think
everyone
who
has
worked
in
any
scenario
where
your
QA
automation
team
wants
to
automate
a
test
against
a
single
page
app.
It
is
very
frustrating
for
them
because
they
don't
know
how
to
know
when
the
page
is
loaded.
C
All
of
their
frameworks
and
systems
are
designed
for
web
pages
and
then
navigating
between
web
pages
and
they're
all
rendered
server-side.
They
have
made
the
adjustment
to
like
using
the
Dom
content
loaded
events,
although
they
don't
actually
subscribe
to
it.
They
just
check
for
whether
it
has
occurred
in
a
polling
loop,
that's
the
limitation
of
webdriver,
and
indeed
almost
every
other
thing
that
I've
seen
actually.
C
C
They
all
have
trouble
detecting
when
a
react
component
tree
has
reached
a
certain
state,
and
this
is
especially
a
problem
for
progressive
web
apps
because
they
very
deliberately
load
in
chunks.
So
the
page
load
event
takes
place
long
before.
Perhaps
the
rest
of
the
functionality
has
come
in.
The
cart
may
still
be
loading
functionality
as
a
drawer
opens.
It
may
be
placing
an
external
call
and
react
is
continuously
rendering
and
re
rendering
its
components.
So
it's
a
difficult
question
to
answer,
but
we
need.
C
To
be
true
and
I
would
say,
you
know
if
they're
checking
say
for
a
given
URL
to
be
loaded
like
the
home
page
or
a
product
page.
Then
we
should
set
that
URL
as
loaded
equals.
True
somehow
in
that
global
context,
so
that
they
can
do
that
detection
and
we
can
put
the
code
right
in
the
source
or
in
a
wrapper
component
that
wraps
around
roots
or
something
and
then
put
the
entire
implementation
inside
an
if
node
and
V
equals
test
clause
which
will
make
it
disappear
in
the
in
the
production
bundle.
C
So
if
we
do
it
right,
then
it's
just
like
the
react.
Production
mode
it'll,
just
all
of
that
code
will
go
away
when
it
hits
prod.
So
this
is
I
think
a
toughy.
This
is
a
framework
level
thing,
but
it
is
also
really
interesting
work
and
it's
stuff
that
we
need
to
prioritize,
maybe
not
as
high
as
some
other
things,
but
we
need
to
get
a
concept
started
on
this
right
away.
F
F
C
C
At
that
point,
there
needs
to
be
something
which
sets
a
global
variable,
reflecting
that
the
product
detail
page
is
really
finished.
Loading
because
I
don't
think
that
a
test
that
simply
waits
a
period
of
time
is
going
to
be
a
resilient
test.
If
the
server
under
test
is
slow
for
that
test
run,
then
the
test
will
give
you
a
false
negative.
C
If
the
server
gets
much
faster
than
the
test
will
be
unnecessarily
slow.
So
we
want
to
avoid
waiting
for
hard-coded
timeouts,
and
so
the
story
is
about
setting
variables
so
that
the
polling
loop,
which
runs
more
than
one
times
a
second
and
to
detect
exactly
when
the
snare.
The
UI
scenario
is
loaded.
C
A
C
A
G
G
C
C
The
the
QA
team
is
open
to
maybe
changing
frameworks,
but
MF
TF
is
the
easiest
answer,
because
the
whole
point
of
this
end
end
testing
is
to
get
to
the
magento
definition
of
quality,
for
which
FF
TF
is
the
thing
the
thing
about
it
is
MF,
TF
happens
to
be
written
in
PHP
and
the
tests
are
written
in
XML,
but
the
core
problem
is
that
it's
a
webdriver
and
web
drivers
can't
subscribe
to
Dom
events.
Just
that's
the
thing.
Okay,.
G
A
Yeah,
it's
a
good
call
out.
There's
a
lot
of
buzz.
That's
I
react
to
comment
on
that
one
I
do
haven't
had
a
chance
to
dig
in
but
yeah
echo
game
this
point.
Our
goal
here
is
really
alignment
within
a
TF
and
if
there
are
ways
for
us
to
look
at
options
that
Interop
we
interoperate
with
that
in
a
nice
clean
way,
then
I
think
that's
great,
but
but
we
definitely
need
to
stay
focused
on
the
standards
here
as
much
as
we
can.
C
A
C
The
fact
that
there
is
a
number
of
there's
a
number
of
different
pieces
of
prior
art
to
examine
there
is
some
communication
asynchronously
with
the
test
team,
John,
Stennett,
etc.
To
do
well,
actually,
no
I.
Don't
think
that
second
part
is
necessary.
That's
that's.
Extra
complication,
I
mean
I,
think
it's
definitely
a
full
spread
for
some.
What
I
call
they
ate.
A
This
one
is
groomed.
Well
we'll
come
back
to
this.
If
we
feel
like
it's
any
bigger,
we
certainly
can
convert
it
to
an
epic
and
then
break
off
a
couple
discovery
efforts
as
all
yeah,
the
Cypress
one's
interesting
James.
Let's
talk
offline,
we
saw
a
kind
of
a
quick
demo
of
how
Cypress
is
use
against
I
believe
an
older
build
of
venya
by
one
of
the
presenters
at
at
the
react
account
again.
A
You
know
it
was
one
of
many
frameworks
that
we
used
to
kind
of
evaluate
things
and
so
I'd
be
asked
to
look
at
this
from
an
MF
yeah
standpoint,
but
it
was
interesting
so
but
again
not
that
not
the
experts
here
and
so
yeah.
You
know
we'll
put
them
on
the
list
of
things
to
do
so,
cool
all
right.
So
let's
switch
gears
then
so
everybody's
favorite
topic
is
a
venya
here,
and
so
let's
switch
gears
a
little
bit,
and
so,
as
promised.
A
One
of
the
things
we'd
like
to
do
is
similar
to
the
spirit
of
readings
and
see
what
some
of
the
spirit
of
wish
list
as
estelle
Mia
is
really
thinking
about
the
UX.
For
this
there
are
some
some
basic
things
that
we
can
call
out
in
a
discovery
form
because,
ultimately
again,
if
you
look
at
this
example
for
Veronica
Costello,
it's
pretty
straight
forward.
So
imagine
a
Rita
read-only
scenario
that
that
would
have
the
basics
right,
contact
information.
A
You
know
newsletters,
yes
or
no
billing
and
shipping
information,
potentially
recent
orders
that
does
get
into
what
was
what
was
just
created
for
purchase
history.
But
that's,
okay
and
I.
Think
the
starting
place
of
this
would
just
be
address
only
recently
ordered
same
same
ideas,
purchase
history
and
then
start
to
get
into
wish
lists
as
well,
which
which
I,
which
is
also
being
covered
under
separate
story.
But
again,
the
spirit
of
this
is
getting
similar
to
getting
into
similar.
A
What
we've
started
to
do,
which
is
to
you,
know,
kind
of
take
with
what
we've
got
on
the
on
the
back
end
and
start
to
start
to
expose
pieces
of
this.
All
of
this
is
available
if
you
look
into
the
details
of
Veronica
Costello
on
the
back
end,
and
so
the
hope
and
the
the
promise
of
the
story
is
to
is
a
little
bit
of
discovery
based
on
what's
available
either
graph.
A
Ql
arrests
I'd
be
able
to
expose
this
in
a
way
that,
as
a
standalone,
page
versus
a
slider,
and
then
you
know,
look
at
a
very
primitive
form
of
this,
which
is
just
has
to
be
read.
Only
we'll
worry
about
editing
and
other
aspects
of
this
later,
but
again,
I'm
kind
of
putting
this
up
on
the
board
to
say.
Okay,
this,
you
know,
do
we
need
to
you,
know,
create
any
subsequent
graph.
Ql
issues.
Do
we
feel,
like
we've
got
good
coverage?
What
are
the
concerns
here?
Are
they
related
or
similar
to
other
ones?
A
How
does
this
relate
to
wishlist,
purchase
history
and
so
on?
There's
definitely
work
here
to
get
started
ahead
of
where
we're
gonna
land.
With
with
this
month's,
this
month's
MVP
really
the
venya
theme,
and
so
so
here's
the
story
so
in
its
basic
forms,
the
shopper
you
wanna
be
able
to
view
account,
details
put
in
contact,
address,
orders
and
other
related
information.
You
guys
saw
the
example
from
luma,
and
the
purpose
here
is
to
make
an
informed,
accurate
or
maybe
even
a
repeat,
if
spelled
correctly,
purchase
in
the
future,
so
assumptions
here
pretty
straightforward.
A
A
The
purchase
history
work.
So
the
IE
palm
team
has
gotten
that
underway
with
purchase
history.
So
taking
a
look
at
what
what's
been
checked
in
for
that
as
a
PR,
just
to
see
how
this
might
relate
to
the
orders
that
you
see
here
again
in
this
guy
right
here,
and
so
that
would
be
a
read-only
variety
of
that.
And
then,
of
course,
you
know,
beginnings
of
a
basic
recount
readout
of
account.
A
Details
against
Zambia
will
work
for
magic
in
that
and
make
this
a
wet
lab
was
a
lot
more
compelling
than
what
we've
got
here
for
mobile.
But
the
beginnings
of
this,
the
shell
of
this
is
where
we're
gonna
start
so
edit,
maybe
something
a
bit
more
in
line
versus
what
we've
got
currently
and
Change.
Password
will
probably
be
a
lot
more
elegant
than
a
separate
page.
We
want
to
take
advantage
of
what
we
did
for
create
accounts
and
those
types
of
things,
but
none
of
those
really
need
to
be
solved
for
in
this
discovery
effort.
A
We
just
want
to
be
able
to
pull
this
in.
So
in
theory
this
could
you
know
the
hopes
is.
This
could
be
very
small,
but
actually
you
know.
More
importantly,
let's
make
sure
this
isn't
too
big
for
us
to
start
start
looking
at
for
our
for
our
next
milestone,
just
after
GA,
which
we're
kind
of
noting
here
as
a
release.
A
Five,
so
for
those
were
following
release,
or
is
the
essentially
where
we're
gonna
be
intending
to
to
finish
off
at
the
end
of
the
month
with
MVP
at
least
five
gives
us
essentially
another
quarter
or
ninety
days
after
that
for
this
one
zone.
So
that's
what
I've
got,
and
so
this
is
again
the
beginnings
of
where
we
aware
we
would
leave
off
with
luma
the
presentation
of
it
in
a
in
a
in
a
in
a
venya
form
factor
that
at
least
plays
off
of
the
navigation.
A
All
right:
well,
let's
add:
let's
go
ahead
and
analyse
die
for
the
new
comments,
let's
let's
hazard,
an
estimate
here,
and
so
where
do
we
like
to
to
start
the
bidding
on
this
one.
C
As
a
discovery,
I
think
that
it
needs
to
be
time
boxed
so
effectively.
What
we're
doing
when
we
estimate
this
is
not
estimating
how
long
it
would
take
Finnish
discovery,
but
how
much
discovery
to
do,
and
that's
I
don't
want
one
person
to
spend
the
whole
time
doing
this.
So
I
I
want
to
call
it
a
three
I
want
to
say:
do
whatever
do
those
tasks
in
whatever
detail
allows
you
to
do
them
in
things
three
to
five
days
max
yep.
E
A
A
A
All
right
there
we
go
perfect
done
and
done
excellent.
That's
what
we've
got
so
so
again.
You
know:
we've
got
I,
think
we've
made
good
progress
and
I
think
I've
identified
a
really
good
update
on
tutorials.
You
know,
James,
you
know,
I
appreciate
your
help.
Getting
the
MF
TF
work
and
kind
of
the
the
story
up.
There
I
think
looking
for
someone
to
help
there
and
then
also
the
beginnings
of
some
discovery
work
for
for
a
count
here,
which
may
be
a
good.
A
You
know
good,
follow
up
to
some
the
create
accounts,
work
as
well
and
so
anything
else
that
we
like
to
groom
as
a
team.
These
are
the
ones
I
prepared,
but
always
open
to
at
least
starting
something
that
we
could
always
come
back
to.
Given
the
given
the
attendance
that
we
have
here,
any
any
other
questions,
comments
or
suggestions
for
for
another
story.
C
A
Now
that
makes
sense
so
well
good.
Well,
let's,
let's
wrap
things
up
here,
just
a
couple,
a
couple
of
administrative
notes
and
so,
as
you
guys
know,
we're
definitely
in
the
throes
that
you've
got
three
release,
and
so
you
know
bear
with
us.
A
You
know
we
doesn't
want
to
show
that,
and
you
know
ultimately
from
our
project
that
it
was
only
intended
to
to
showcase
product
details
in
categories
part
of
the
GA.
We've
got
a
pretty
compelling
and
basic
commerce
experience
that
we're
we
should
all
be
pretty
proud
of,
and
so,
if
there's
anything
outstanding,
you
know
definitely
stay
on
top
of
that
to
the
best
you
can
again
bear
with
us.
If
there's
some
questions
that
are
outstanding,
you'll
see
us
dividing
and
conquering
where
we
can
on
the
unalaq
channels
and
such.
A
A
lot
of
you
guys
and
actually
I
think
should
improve
overall
overall
velocity
and
kind
of
the
self-sufficiency
of
things,
and
so
I
look
forward
to
that
here.
You
know
after
the
Thanksgiving
break,
but
as
always,
keep
us
honest
on
the
you
know
on
the
feedback.
Let's
have
any
questions
and
by
all
means.
Thank
you
so
much
for
your
help
and
support.
Don't
with
that
have
a
great
rest
of
your
day
and
for
those
in
later
time,
zones
have
a
great
have
a
great
weekend.