►
From YouTube: Rachel and Fabian discuss changes to Geo Team workflow.
A
Encouraging
specific
things
to
land
up
in
certain
milestones
and
the
other
thing
I
was
thinking
about
was
for
the
first
one.
We
can
also
encourage
the
team
that
this
is.
This
is
the
way
that
we're
trying
to
work
going
forward
and
for
verifying
or
replicated
data.
This
is
what
we
would
like
to
try
to
do
and
see
how
that
works.
So
we
want
to
try
get
it
into
a
good
State
push
it
through
the
process
that
we've
defined
and
get
it
done
for
a
specific
milestone,
and
then
retrospect
about
how
they'd
wait.
I
think.
A
A
B
A
B
What
I
can
I
think
what
I
can
say
is
for
especially
I
think
on
an
epic
level,
but
probably
also
on
a
like.
If
it's
really
fine,
you
know
if
there
are
certain
things
that
I
may
be
a
little
bit
more
valuable
earlier
on
than
others,
but
I
can
I
think
what
I
can
say
is
say:
okay,
for
example,
this
automatically
choosing
the
best
best
note,
I
can
say:
okay.
B
This
is
something
where
I
feel
this
is
valuable
to
our
customers,
and
we
we
should
work
on
this
next
and
the
better
we
define
in
what
that
really
means
the
easier
it
should
be
to
say:
okay
in
12.3,
we
will
very
likely
deliver
X
right,
but
we
won't
be
able
to
do
all
of
it.
That
will
probably
take
until
twelve
point
four
or
four
longer
that's
the
discussion
that
we
need
to
have
that's.
A
That's
very
much
how
I
view
it
as
well,
because
you
can
come
to
me
and
say
you
know.
This
is
the
most
important
customer
thing
that
we
need
to
be
looking
at
next
and
we
would
really
like
this
year
and
then
I
can
for
argument's
sake,
say
all
right.
I
understand
that
that's
important
we've
also
had
a
production
incident,
which
means
if
we
actually
offered
we're
prioritizing
this.
A
B
A
And
that's
the
way
that
I've
done
it
in
the
past
as
well.
I
was
actually
on
my
one-on-one,
for
you
tomorrow
is
actually
talking
about
how
to
prioritize
bugs
and
other
issues
that
come
up
and
in
the
past,
I've
had
meetings
with
the
product
managers,
saying,
let's
just
talk
about
bugs
and
how
they
fit
into
what
we're
currently
doing,
where
they
go
and
I
think
that
that
becomes
really
useful
like
if
it's
perhaps
setting
up
a
sensual
time,
every
Friday.
Where
we
talk
about
well.
This
is
the
state
of
the
board's
at
the
moment.
A
This
is
what's
currently
in
progress
and
what's
going
to
make
it
not
going
to
make
it
and
is
there
anything
you
want
to
reset,
because
you
know
on
Monday,
people
are
going
to
be
open
for
new
things
or
just
using
using
the
week
as
some
kind
of
boundary
marker
for
having
those
discussions.
I
think
that
would
be
I
think
they
would
be
really
useful.
I.
B
A
I
think
I
think
I
like
that,
and
also
then
we
can
encourage
the
people
who
own
epics
to
join
in
and
if
they're
people
who
have
epics
that
are
starting
that
are
perhaps
in
different
time
zones,
and
we
can
be
flexible
about
trying
to
make
it
that
they
can
be
part
of
the
you
know
whatever.
That
is,
but
I
like
the
idea
of
having
a
regular
conversation
about
how
that
fits
and
making
that
public.
A
B
Is
the
conclusion,
then,
essentially
that
things
that,
like
issues
that
go
on
to
the
Billboard
and
that
are
ready
for
development,
should
have
a
milestone
associated
with
them?
Because
that
is
something
that
we
need
to
agree
on
and
then
that
should
essentially
determine
the
priority
order
for
the
team,
because
they
can
look
at
this
and
say
like
okay
for
12.1
or
12.2
or
whatever
it's
going
to
be.
This
is
sort
of
the
you
know
the
upcoming
milestone
stuff,
but.
A
A
A
A
A
A
B
A
Cool,
so
the
so
the
only
thing
about
this
is:
that
means
every
time
the
milestone
is
close
to
closing.
We
have
to
change
the
board
and
also,
as
we
get
towards
the
end
of
a
milestone,
we
can't
see
the
next
items
that
are
coming
up
because
they
will
be
hidden.
So
that
was
why
we
were
coming
back
to
this
idea
of
having
an
active.
Yes.
A
A
What
if
we
built
the
board
without
a
milestone,
and
so
when
I
say
build
the
board
without
a
master
and
I
say
we
just
used
the
like
the
tag
geo
and
something
is
like
some
some
form
of
just
labels,
because
then
it
doesn't
matter
what
milestone
you'll
end
up,
adding
to
it
they're
all
they
will
all
show
up.
Yes,.
B
A
A
B
Say
my
transition
is,
you
know,
like
I
would
have
to
write
the
checklist,
but
essentially
it's
going
to
be.
You
know
like
the
issue.
Description
is
in
place,
but
it
belongs
to
an
epoch
once
all
of
those
things
are
done,
but
I
think
we
need
to
mark
it
as
active
and
decide
essentially
on
a
a
milestone.
Well,.
B
Because
this
means
that
essentially,
things
move
from
my
planning
board
into
our
actual
backlog,
but
which
now
is
what
I
would
like
the
backlog
to
be
the
place
where
things
are
that
we
intend
to
do
at
some
point,
what
I'm
not
doing
right
now
and
then
we
need
to
go
through
the
backlog
and
say:
okay,
you
know
what
is
like.
Epics
and
issues
are
in
this
backlog.
A
B
B
I
think
that's
actually
compatible
with
any
change
that
is
being
made
in
product
right
now,
because
the
the
flow
in
product
is
essentially
just
you
know
like
what
goes
into
the
planning
and
what
goes
into
the
building.
But
it
doesn't
I
think
mechanically
prescribe
how
to
actually
manage
this,
and
this
should
allow
us
to
do
it.
So
fantastic.