►
From YouTube: Weekly Package Meeting 06-25-19
Description
Our weekly team meeting, in which we talked about upcoming milestones and the value (both present and future) of this recurring meeting.
B
A
We're
recording
our
weekly
package
team
meeting
looks
like
the
first
couple
of
options
are
me
and
the
first
item
on
there
is
to
review
that
twelve
to
milestone
has
been
groomed
and
ready
for
initial
review.
So
we
have
a
meeting
this
afternoon,
actually
Dan
and
and
John
you
both
are
on
it
and
Nick
and
Steve
you're
optional.
A
B
B
A
B
A
No
problem
the
next
one's
an
FYI
I
wanted
to
share
with
the
team
some
of
the
user
interviews
that
I've
been
conducting
and
also
open
up
the
idea
we
have
a
few
friendly
ones
that
are
coming
up
dan
recommended
some
people
that
are
maintaining
container
registries.
If
anyone
would
like
to
participate
and
listen
in,
please
let
me
know
happy
to
invite
you
and
you
could
hear
firsthand
what
people
are
saying
instead
of
just
watching
the
video.
C
C
We
have
all
of
our
contracts
for
her.
Our
back-end
engineer
sign
now:
I'm
saving
for
one
which
we
have
a
verbal
acceptance
for
our
first
next
person.
I
think
that's
the
exact
correct
terminology
starts
on
the
8th
of
July,
and
then
we
have
another
person
joining
on
the
1st
of
August
and
then
another
person
on
the
5th
of
August.
C
The
last
person
who
we
are
in
the
process
of
getting
all
of
their
contracts
sorted
out
will
be
in
September
and
then
just
like
a
really
slow
process
to
sort
of
start
up
either
neural
wiring
is
done
at
least
as
far
as
the
banking
engineers
are
concerned,
but
yeah
I
just
wanted
to
updated
on
that
so
boom
like
a
week
or
two
we'll
have
someone
joining
the
team.
That
person
is
in
Melbourne
in
Australia,
rather
than
Florida
well,
rather
than
Florida
yeah.
C
Think
I
like
having
a
sort
of
a
get
together
and
sort
of,
say,
Natalie,
saying
hello
to
everyone
and
seeing
everyone's
lovely
faces,
but
doesn't
feel
like
there's
a
whole
lot
to
cover
here.
That
needs
to
be
covered
synchronously.
So
if
anyone
has
any
thoughts
on
that
or
a
preference
either
way,
I'm
happy
to
hear
it
now
or
you
can
just
chat,
we
can
chat
about
it
in
the
English
like
channel
or
somewhere
else.
That's
more
useful
towards
John
yeah.
B
I
think,
as
the
team
builds
out
a
little
bit
more
dan,
maybe
to
maybe
to
your
point
this
might
may
become
more
useful
as
we
have
issues
that
are
potentially
blocked
or
at
risk
and
more
team
announcements.
Things
like
that.
That's
kind
of
how
release
and
verify
have
been
working
so
far,
but
yeah
I
agree
we're
all
we're
getting
through
this
super
quick,
maybe
just
because
the
team
spinning
up
still
yeah.
C
And
maybe
maybe
it's
worth
saying
that
this
this
meeting
isn't
intended
just
to
be
for
Tim
and
I
to
make
announcements
or
you
know,
John,
to
make
announcements.
So
if
if
people
have
questions
or
anything,
it's
really
an
opportunity
to
have
you
know
a
couple
of
minutes
with
everyone
on
the
team?
Are
you
sort
of
aware
of
what's
going
on
and
and
ask
questions
put
it
in
the
agenda
and
we
can
cover
it
now?
Obviously
we're
recording
these
and
we
want
to
make
sure
that
we're
I'm
being
careful
about
you
know
visual.
C
B
C
And
it's
a
fair
point:
I
feel
like
the
intention
of
the
retro,
is
a
little
bit
different
from
this
right.
Like
surely
you
know,
Vera
retro
is
to
sort
of
say
what
went
well
and
didn't
go
well,
so
I
think
I
think
rather
than
sort
of
saying
you
know
we're
covering
things
here
that
we
ought
to
be
covering
there
or
vice
versa.
I
think
it's
worthwhile
sort
of
just
focusing
the
meetings
on
the
subject
at
hand.
It's
something
I
want
to
be
careful
about.
C
It's
not
like
packing
too
much
into
single
meetings
where
we
can
have
like
sure,
though,
like
little
get-togethers
and
get
through
what
we
need
to
get
through
as
long
as
it's
actually
helpful
to
do
it
synchronously
and
keeping
in
mind
that
we
will
have
people
spending
from
Melbourne
to
Romania
at
some
point,
and
so
these
synchronous
meetings
will
be
a
bit
of
a
luxury,
so
yeah,
that's
that
of
mine.
Those
are
my
thoughts.
Does
anyone
else
have
thoughts
on
that?
Well,.
D
C
Yeah
I
think
that's
totally.
It's
totally
something
we
can
do.
I
think
the
main
value
I
get
out
of
this
meeting
so
far
as
I
was
kind
of
alluding
to
before,
which
is
the
chance
to
sort
of
have
a
live
conversation
with
people
for
the
team's
sake
right
and
maybe,
as
John
said
as
we
get
larger,
will
have
more
moving
parts.
C
We're
gonna
have
more
work
because
we'll
have
more
people
actually
doing
that
work
and
so
there'll
be
there'll,
be
more
to
coordinate,
but
the
value
of
at
least
occasionally
sort
of
getting
together
and
having
a
chat,
and
this
could
be.
This
meeting
itself
could
become
less
from
or
rather
than
more
formal
I'm
a
bit
of
an
advocate
for
not
repeating
ourselves
like.
So,
if
you
put
notes
in
stand-up
I,
don't
really
if
there's
a
good
reason
to
discuss
it.
B
C
More
of
like
hey,
what
is
the
use
of
this
meeting
and
if
it's
just
some
other
same
form
of
something
we're
already
doing,
that's
like,
why
would
we
do
it
right,
yeah?
Anyone
else
have
thoughts
on
that.
I
tend
to
agree
that
this
is
a
chance
to
chat.
Steven
I
didn't
mean
to
shut
you
down
there
at
all.
Sorry.
D
C
A
B
Yeah
the
only
as
I
mentioned
earlier.
Maybe
we
won't
the
only
thing
we're
doing
a
little
differently
over
theirs.
We
have
we're
calling
out
specifically
a
sec
for
folks
and
at
risk
or
blocked
issues,
and
they
might
not
be
super
pertinent
right
now,
but
as
we
grow,
that
could
be
a
nice,
a
nice
way
to
call
things
out
kind
of
ties
in
maybe
to
what
Steve
saying
like
just
talking
points
around
issues,
but
that's
nice.
Just
so.
C
For
that,
but
just
sort
of
understanding
what
what
dates
come
next,
you
know
Tim
I
think
you
did
a
you
do
a
great
job
of
that
already,
but
that's
helpful
for
me
what
what
time
in
the
morning?
What
time
of
this
is
this
meeting
for
you
Nick,
sorry
to
change
the
subject,
we
can
go
back,
it's
4:00
p.m.
for
me
right
now.
Well,
it's
not
okay.
So
this
is
not
too
bad
for
you
call
or
even
say
Tim,
sorry
about
that.
I.
A
Was
gonna
say
the
important
date
we're
working
towards
now
is
first
so
having
by
the
first.
We
want
scope
and
capacity
planning
done
for
the
upcoming
milestone,
which
is
12
2.
So
if
we
and
then
the
kickoff
is
on
the
8th
still
so
the
idea
is
agreed
but
agree
on
scope
and
then
on
by
the
8th.
We
have
the
kickoff
document
updated
with
what
we
will
be
working
on
and
what
we
plan
to
finish
and
then
we
go
through,
and
you
know,
update
that
as
we
go
cool.
C
All
right,
so
it
sounds
like
we're
just
in
this
for
place
right
now,
where
we
have
not
a
whole
lot
to
talk
about.
Is
there
aren't
a
whole
lot
of
us
and
the
some
extent
I
mean
Steve
still
getting
up
to
speed
next
door
getting
up
to
speed,
so
maybe,
as
John
suggested,
this
sort
of
just
a
function
of
us
being
kind
of
just
all
new.
It's
tough
so
so
happy
to
keep
this
I
think
it's
what
set
mine?
What
what
sort
of
got
my
alarm
bells
ringing
was?
A
C
For
I
mean,
as
we
talk
about
these
dates,
I
don't
know
if
there's
a
good
format
to
maybe
it's
worth,
sharing
them
in
the
package
channel
and
they're
just
sort
of
linking
to
the
information
on
timings
so
that
you
know
other
people
in
the
team
can
sort
of
look
up
what
it
means
to
be
like
going
through
and
creating
issue
going
and
doing
all
that
sort
of
process
finalizing,
while
we're
committing
to
the
next
release
and
all
that
kind
of
stuff.
And
since
we're
all
new.
A
Yeah
and
one
thing
Jason
my
boss
does
for
me-
is
at
the
beginning
of
each
week.
He'll
remind
me
what
the
upcoming
milestones
are
for
the
week,
so
I'll
say
we're
working
towards
the
first.
We
should
be
working
on
scope
and
capacity
planning,
we're
working
towards
the
22nd.
It's
the
release,
post
and
blah
blah
blah,
so
I
I
could
just
do
the
same
thing
on
Monday
mornings,
just
post
in
that
the
important
date
for
the
week
as
well
I
find
it
helpful
for
myself.
So
hopefully
it's
helpful
for
the
channel
yeah.