►
Description
John-Mason says thank you to the team and gives his read out.
Follow-up to https://youtu.be/CXeCeYYc1ew
A
Hello,
John
Shackleford
here,
thanks
again
all
for
joining
that
design
session
this
morning
and
thank
you
Gabe
for
hosting
it.
I
was
really
impressed
by
the
number
of
ideas
that
this
team
generated
and
thank
you
thanks
for
being
brave,
and
you
know,
with
very
little
context,
just
jump
right
in
I
thought.
A
There
was
a
lot
of
great
stuff
that
came
out
of
it,
and
I
can't
wait
to
make
further
iterations
on
those
same
ideas
now
I'm
afraid
I
had
to
leave
the
meeting
before
I
could
share
mine,
so
I
thought
I
would
do
that
real,
quick
and
then
I
hope
in
a
follow-up
session.
We
could
share
with
one
another
what
we
like
about
each
of
the
designs,
in
particular
by
the
way
I've
got
my
pal
Benjamin
here
with
me,
he's
gonna
be
helping
me
through
this
all
right.
A
A
So
the
filter
bar
allows
us
to
highlight
items
in
the
workflow
view,
either
by
a
particular
epoch
or
by
a
team
member.
So
the
idea
is,
if
you
highlight
one
of
those
items
or
select
one
of
those
items,
all
of
the
individual
issues
will
will
turn
a
dark,
color
or
or
something
to
indicate
that
they
are
connected
to
that
particular
epoch.
Same
thing
can
be
done
with
team
member
and
and
of
course
we
could
show
a
few
key
pieces
of
metadata
about
the
epoch
like
when
we
expected
it
to
be
finished.
A
A
Here,
I've
got
one
for
input,
design
and
dev,
and
so
on.
These
are
sort
of
reflective
of
our
current
gate
lab
process,
but
they
could
be
customized
for
a
particular
process
and
as
I
move
down
the
column,
things
start
to
be
different
from
a
Kanban
board.
First
of
all,
we've
got
the
little
boxes
instead
of
the
whole
issues
highlighted
and
the
secondly,
is
the
column
is
divided
into
sections,
and
so
the
very
first
one
you
can
see
here.
A
A
That
might
be
different
for
a
different
kind
of
input
as
we
go
further
down.
We've
got
one
here
that
is
for
support
issues
or
for
bugs
and
they're
the
lead
time
may
be
different
and
the
work-in-progress
limit
may
be
different,
and
each
of
these
you
know,
we've
got
one
for
security
and
compliance.
These
are
different
sources
of
demand
for
your
system
and
then
up
at
the
top
we've
got
this
flow
distribution
graph.
A
This
is
the
chart
of
sort
of
the
percentage
of
those
different
inputs
over
time,
so
that
I
can
see
how
I'm
spending
the
resources
that
I
have
am
I
primarily
fixing
bugs
am
I
primarily
building
features.
What's
the
ratio
there?
Maybe
I
want
to
make
some
corrective
action
around
the
WIPP
limits
here
to
adjust
that
mix.
A
Then
items
come
over
into
the
next
column
and
the
first
step
in
this
process
is
a
design
step
and
because
this
is
not
an
input
here,
we've
chosen
to
highlight
their
work
and
not
just
the
working
process
limit,
but
also
cycle
time.
How
long
is
something
typically
in
this
particular
area,
and
then
items
are
moving
down
the
column
and
so
on?
So
to
the
estimation,
step
and
I
wanted
to
do
this
to
save
space
so
that
I
could
get
my
whole
flow
on
one
page
and
I
didn't
have
to
do
any
scrolling.
A
I
could
see
the
whole
thing
at
a
glance,
even
if
there
are
a
lot
of
steps
that
I'm
that
I'm,
using
icons
to
indicate
different
kinds
of
items
and
my
really
fuzzy
little
selectors
over
here
I've
got
things
selected
by
the
filter
or
my
legend
here.
Normal
items-
and
this
is
one-
is
really
important
to
me.
This
is
an
item
that
hasn't
moved
in
24
hours.
A
So
if
I'm
expecting
progress
to
be
made
on
these
things-
and
it
shows
up
with
this
little
dot
in
it-
and
that
tells
me
something
something's
gone
wrong
or
I
did
not
expect
it
to
be
waiting
around
with
no
activity
of
any
kind
I
expected
either
to
move
to
the
next
stage
or
I
expected
some
comments
on
it
or
some
code
to
be
committed
against
it
and
I
might
ask.
Why
is
that
thing
not
moving
and
then
I've
got
another
one
here
for
indicating
increased
cycle
time
and
I
see
that
here?
A
In
my
review
bucket
this,
this
items
for
review
and
I
really
care
about
items
that
they're
approaching
the
average
cycle
time
for
items
in
that
area,
so
that
if
we
don't
move
that
on
quickly,
our
metrics
are
gonna
start
looking
worse
for
this
particular
stage,
and
then
things
move
on
into
the
release
queue
and
this
year
we're
calling
out
hey.
This
is
a
batch
type
process
in
which
things
are
just
waiting.