►
From YouTube: TEC Sprint Retrospective: Sprint 1
Description
Timecodes:
00:00 - Intentions and distractions
04:22 - Retrospective document
08:50 - TEC sprint 1 "The kickoff" exercise
🙏 Thank you for watching! Hit 👍 and subscribe 🚩 to support this work
🌱Join the Community🌱
on Discord https://discord.gg/DDr5kYU
or say hello on Telegram http://t.me/CommonsStack
Join the conversation https://forum.tecommons.org/
Follow us on Twitter: http://twitter.com/CommonsStack
Learn more http://tecommons.org/
B
Thank
you.
My
intentions
are
to
yeah,
follow
this
first
review
and
see
how
we
go.
I'm
curious
about
this
meeting
and
my
distractions
is
that
every
time
I
start
a
call,
this
machine
in
the
construction
beside
me
starts
at
the
same
time,
so
we're
having
like
a
non-spoken
fight
here
but
other
than
that,
I'm
present
and
to
jake.
A
Hi
everyone
yeah,
that's
that's
retrospect
distractions.
Well,
it's
not
so
bad
zola's
doing
school
at
her
at
her
mom's
zayden's
destroying
something
downstairs.
I
don't
know
what's
going
on
there
other
than
that,
it's
it's
it's
okay!
I
mean
I
did
just
get
horrible
news
from
cash
app
that
they
they
don't
like.
A
A
A
A
Thank
you,
septimus,
sorry,
for
being
late.
I
completely
forgot.
My
intentions
is
to
go
over
the
first
retrospective
see
how
we're
doing
try
to
improve
help
other
members,
wherever
I
can
and
get
ready
for
tomorrow.
New
sprint,
I
don't
know
who's
missing
so
I'll,
pass
it
to
time,
and
you
can
moderate.
C
Take
it
I'll,
take
it
and
then
metaverde
has
to
go
too.
I
think
that's
it
yeah.
I'm
excited
for
this
call
I'm
a
little
distracted,
because
I'm
talking
to
wesley
about
some
of
the
bugs
that
are
in
his
token
log
but
other
than
that
sending
some
screen
shots
will
be
over
as
far
as
intentions.
C
I
I'm
very
excited
to
hear
what
we
think
what
we
can
improve.
It's
the
first
sprint,
there's
always
things
that
we
can
do
better.
You
know
we're
taking
a
model
that
was
made
for
one
group
of
people
and
applying
it
here.
It's
not
gonna
fit,
so,
let's,
let's
make
it
better,
but
there
are
probably
also
a
lot
of
things
that
went
really
well
and
I'm
excited
to
talk
about
those
as
well.
Not
just
complain,
although
that
that'll
be
a
major
part
of
it
too.
I
will
pass
it
to
metaverde.
B
Hey
my
distractions
are
really
super
low,
because
folding
laundry
helps
me
focus
and
I
got
really
excellent
workout
last
night
the
gyms
are
open
and
I
got
in
two
martial
arts
classes,
so
I'm
appropriately
tired
and
my
attention
is
on
listening
and
following
the
workflow
and
getting
a
feel
about
how
you
run
your
sprints
and
about
how
I'm
going
to
integrate
with
this
that's
kind
of
it.
Thank
you.
I
think
I
was
the
last
one
so
back
to
the
meeting
perfect.
D
Okay,
so
if
you're
not
in
the
document,
I'm
just
going
to
share
the
screen,
so
everyone
can
see
it,
and
essentially
there
are
three
key
meetings
in
scrum.
So
I'm
doing
this
just
for
the
benefit
of
anyone.
Who's
not
already
gone
through
the
experience
of
working
with
a
scrum
framework.
D
Essentially
it's
the
two
together
and
to
have
mutual
accountability
of
our
of
our
commitments
for
the
next
two
weeks,
and
then
it's
the
retrospective,
where
we
talk
about
the
review
where
we
present
our
work
and
for
us
at
the
tec,
our
review
is
really
the
community
sink
that
we're
gonna
have
have
later
tonight.
So
that's
our
review
meeting
where
we
show
the
work
that
we've
done
over
the
sprint
and
then
this
retrospective
is
really
geared
towards
improving
our
process.
D
So
the
the
scrum
framework
is
super
lightweight
and
it's
designed
to
be
completely
adaptable
to
the
team
to
the
circumstances,
to
the
context
to
the
time
of
year
to
whatever
to
whatever
we
need.
So,
every
two
weeks
we
look
at
what
went
well
about
our
process
and
we
looked
at
what
could
go
better
and
then
from
the
what
could
go
better
category.
D
We
select,
we
brainstorm
some
action
items
and
we
select
the
one
or
two
most
important
ones
and
we
test
them
out
and
we
see
if
it
actually
does
improve
our
process.
So
it's
a
it's
a
very
it's
it's
under
the
agile
planning
framework
and
it's
a
it's
a
it's
a
way
to
stay,
super
agile
and
continuously
improve
our
process.
D
So
what
I
would
say
is
if
everyone
can
right
now
open
up,
zen
zenhub
and
have
a
look
at
this
milestone
and
just
have
a
look
at
where
you
are
check
in
with
yourself.
We
don't
need
to
do
this
for
everyone,
we're
not
going
to
go
around
and
do
this
for
everyone.
I
think
we'll
do
a
close-out
session
at
the
beginning
of
our
sprint
planning
tomorrow,
just
because
our
schedule's
a
little
tight
today
to
do
to
do
the
retrospective
in
one
hour.
D
So
I'm
gonna
give
everyone
like
two
or
three
minutes
just
to
think
about,
like
you
know
what
you
committed
to
two
weeks
ago
and
how's
that
going
you
know,
were
you
able
to
focus
on
the
things
that
you've
committed
to?
Did
things
get
in
the
way?
Think
about
you
know
if
some
things
didn't
get
completed,
just
know
why,
so
that
we
can
sort
of
when
we're
doing
our
brainstorming
session
on
what
could
we
do
better?
We
could
think
about
how
we
could
improve
this
process.
D
D
It
is
in
the
calendar
if
you
go
to
the
calendar
in
the
notes
section,
it's
also
in
the
yeah.
That's
the
best.
That's
usually
the
best
place
to
find
it,
but
it's
also
in
the
telegram
stewards
group.
D
B
D
Our
reflection
time
is
is
over,
but
normally
we
would
close
our
board
before
we
do
these
the
retrospective.
So
I
didn't
want
to
jump
in
without
giving
everyone
a
chance
to
look
at
where
you
are
so,
if
everyone
can
confirm-
or
in
anyone
say
if
they
are
having
problems
getting
into
this
mirror
board.
D
So
we'll
jump
here
and
basically
the
instructions
are
just
on
the
side.
Oh
sorry,
the
timing
is
a
little
different.
Now
we're
gonna.
Do
this.
I
think
well,
we'll
see
we'll
see
if
we
can
do
it
with
a
little
shorter
timing,
since
we
have
45
minutes
to
this
to
the
rest
of
this
meeting.
D
So
what
we'll
do
now
is
we'll
spend
about
four
minutes
and
if
everyone
can
just
grab
a
post-it
note
the
green
post-it
note
and
say
what
you
think
went
well
about
this
sprint
like
what
are
the
things
that
you'd
say,
we
should
keep
doing.
What
are
the
things
that
you
feel
were
we
did
strong.
It
can
be.
D
You
know
there
was
from
yesterday's
meeting.
We
have.
Oh
sorry,
that's
actually
for
what
we
could
do
better,
so
feel
free
to
take
four
minutes
and
write
down
what
you
think
we
actually
did
well
what
we
could,
what
we
definitely
want
to
congratulate
ourselves
for
and
keep
doing,
and
I
will
let
you
know
when
three
minutes
has
passed
and
we
have
one
extra.
D
D
B
B
B
D
All
right
10
seconds
left
and
then
we
will
take
some
time
and
read
them
together.
D
B
D
So
these
are
the
things
that
went
well
so
keep
communication
in
between
the
onboarding
group
managed
to
create
active
actions
towards
onboarding
and
getting
to
know
people
through
hatcher
on
board
yeah.
We
really
did
we
did
that.
Well,
maturity
in
the
progress
having
a
sprint
planning
helps
a
lot.
I
didn't
write
that,
but
whoever
did
yeah
general
high
vibes
on
the
project,
yeah
really
so
true
having
a
deadline
was
so
useful.
It
helped
me
justify
to
people
why
I
needed
this
done
asap
excellent
in
a
coordinating
role.
D
Okay,
zero,
finally
started:
yay
collaboration
has
great
flow.
New
people
join
the
community.
The
forum
is
more
active.
Caring
for
the
well-being
of
members.
Prioritization
helps
focus
so
much.
It
feels
like
we
are
so
close
to
being
ready
to
hatch
gravity.
Training
is
starting
yeah,
exciting,
yeah
the
sprint,
the
sprint
our
organization
improved
a
lot.
We
spread
our
excited
to
watch
the
progress.
Getting
up.
Notifications
are
awesome,
onboarding
is
moving
fast
and
with
a
pulse
taking
ownership
of
github
issues,
I'm
happy
with
turnout
for
work
sessions
to
finish
up
tasks.
D
Soft
govs
in
terms
of
service,
tsc
programs
in
his
progress,
legal,
wrapped
up
legal
wrapped
up
getting
wrapped
up
creation
of
gravitron
and
we're
waiting.
All
we're
waiting
on
is
the
c-stack
dap
and
we're
moving
right
along.
I
feel
working
sessions
can
really
help
excellent
and
I
threw
some
down
here,
because
I
thought
we
were
going
to
spread
them
over
the
board.
But
I
love
this
that
they're
all
so
neatly
placed
using
mentions
in
comments
on
github
issues.
D
I
think
we've
done
extremely
extremely
well
with
that
coordinate
better
with
other
groups
manage
better
with
zenhub,
getting
used
to
the
tool
getting
used
to
add
issues
info
to
the
issues.
This
is,
I
don't
know
who
wrote
this.
Is
this
something
that's
going
well
we're
coordinating
better
with
other
groups
and
managing
better
with
zenhub.
D
D
Well,
I
will
then,
I
think
I
think
everyone
is
doing
really
really
excellent
and-
and
we
are
getting
closer
and
it's
nice
to
see
it's
nice
to
see
that,
and
I
think
it
becomes
very
clear
as
we
package
together
bodies
of
work
and
sprints,
and
we
can
just
see
the
execution
sprint
by
sprint.
C
Something
can
I
also
say
something.
I
just
wanted
to
say
that
it
was
so
nice
to
have
like
this,
at
least
for
for
me,
with
the
common
stack,
we're
kind
of
doing
alternated
weeks.
C
So
it's
like,
I
have
a
deadline
one
week
for
the
common
stack
sprint
to
get
everything
done
and
there's
a
few
other
sprints,
unfortunately,
that
I
I
have
this
thing
same
thing,
but
it's
nice
to
have
that
in
one
week
and
then
the
token
engineering
commons
deadline
and
it's
like
okay
now
I
need
to
focus
get
these
things
out
for
the
token
engineering
commons
get
it
get
it
deadline
deadline,
oh
yeah,
okay
and
then
success.
You
know
and
we
can
revel
in
the
success
in
the
call
today.
D
You
know
if
we
we've
experienced
the
first
sprint
like
what
do
we
want
to
do
next
time
like?
How
can
what
can
we
do
better?
What
what
do
we
think
we
can?
Where
can
we
improve?
We
can
always
improve.
Where
can
we
improve
and
I
will
do
another-
I
think
five
minutes
for
this,
so
I'll,
let
you
know
when
four
minutes
has.
D
B
B
D
Cool
all
right
so
we're
the
next
steps
just
to
explain
how
we're
going
to
approach
this
is
to
read
all
of
the
things
that
we
could
do
better
and
then
just
sort
of
group
them
into
themes
after
we
group
them
into
themes.
D
D
So
our
task
distributions
some
people
seem
overloaded
being
conscious
of
speech
time
end
of
the
call
time
of
speech
time
and
a
call
time
yeah,
I
think
so
meeting
length
only
sometimes
keeping
the
focus
on
the
topics
of
the
meeting
synthesizing
information
after
discussion
happens
in
calls
engage
new
contributors
to
collaborate.
People
want
to
do
things;
they
don't
know
how
to
help
okay,
adding
new
people
to
the
contributor
sheets.
D
I
just
need
to
in
a
coordinating
role.
A
lot
of
things
are
people
hard
to
predict.
Sometimes
what
will
get
done
need
to
tell
the
other
people
right
after
sprint
planning
about
the
issues?
I
need
them
for.
D
Some
groups
are
trying
too
much
garden.
Swarm
is
on
a
different
pace.
It's
okay,
but
it
would
be
nice
if
we
shared
sprints.
D
D
I'm
going
to
read
them
all,
and
then
I
think
I
might
ask
for
a
little
more
clarification
on
a
few
of
them.
We
need
to
focus
more
more.
We
need
more
focus
on
our
group
calls,
so
we
can
clearly
specif
them.
I
feel
sometimes
we
spend
too
much
time
explaining
misunderstandings
or
definitions
and
not
getting
to
the
heart
of
the
problem.
D
D
B
D
Okay,
can
I
can
I
ask:
if
any,
can
I
ask
someone
to
explain
this?
One
new
processor
terms
shouldn't
be
considered
self-explanatory.
So
when
you
people
come
or
new
concepts
are
brought
to
the
table
to
have
them
described
with
clarity
and
sync:
does
someone
want
to
speak
a
little
more
on
that.
A
Yeah,
I
will
explain
that,
because
I'm
the
one
who
wrote
that,
basically
sometimes
I
see
concepts
and
stuff
brought
to
a
table
and
there
and
some
terms
and
certain
concepts
are
not
self-explanatory,
like
if
I
say
one
hive
over
and
over
and
over
sometimes
doesn't
mean
that
everyone
in
the
and
in
the
meeting,
understand
what
it
what
that
implies
or
how
it
refers.
A
It
doesn't
mean
that
you
need
to
explain
everything
every
time,
but
it's
just
to
assure
that
everyone
is
on
the
same
page,
at
least
if
it
matters
for
that
concept
or
for
the
thing
that
is
brought
up.
Everyone
understands
what
it
implies,
because
sometimes
I
feel
everyone
doesn't
say
anything,
but
when
we
end
up
the
call
we
finding
out
that
not
everyone
got
caught
up
on
that
and
not
everyone
understood
everything.
So
clearly
what
was
intended
for
so
yeah.
It's
about
that.
This
is.
A
D
Okay,
all
right
so
does
this
look
like
good
groupings
so
distributions
overloading
coordinating
sort
of
community
and
contributors
engaging
new
contributors
yeah.
D
This
is
really
around
the
protocol,
which
we
have
a
great,
a
great
protocol
from
juan
carlos
for
for,
like
a
guideline
from
gravity
group
for
running
meetings
or
for
hosting
having
meetings.
Okay,
so
there's
one
two,
three,
four:
five,
six,
seven,
eight
nine
ten
of
us.
If
everyone
wants
to
grab
a
star
and
vote
on
what
you
think
are
the
two
most
important
of
these.
Oh.
B
B
D
So
the
pink
stars
are
not
used.
Yet
sorry,
if
that
wasn't
clear,
we're
just
taking
the
green
stars
for
well
what
we
could
do
better
and
then
the
pink
ones
we'll
use
for
actions
to
improve.
If
it's
it's
not
the
end
of
the
world,
if
you
started
using
it,
I
guess
it's
only
important
to
use
two
to
only
vote
for
two
things.
D
B
Anymore,
all
right:
okay,.
D
All
right
so
being
conscious
of
speech
time
and,
at
the
time
called
keeping
focus
on
the
topics
of
the
meeting
meeting
length
agenda
protocol
could
be
held
tighter
and
we
need
to
focus
more
on
group
calls,
so
we
can
clearly
specify
what
we
want
to
achieve
with
them.
Okay,
great.
D
So
it
looks
like
this
cluster
and
this
cluster
here
are
the
winner
or
the
top
two
there's.
The
top
two
is
adding
people
to
the
contributor
list,
really
engaging
the
contributors
who
want
to
do
stuff
and
don't
know
how
to
start
don't
know
how
to
help
and
task
distribution.
People
seem
overloaded.
D
Some
groups
are
trying
to
do
too
much
and
in
coordinating
role,
a
lot
of
things
are
dependent.
Okay.
So
why
don't
we
take
and
in
actions
to
improve
we're
gonna
do
the
same
process?
We're
gonna,
take
five
minutes
and
we're
gonna
think
about
how
we
can
address
those
three
issues.
What
can
we
do
to
change?
You
know?
What
can
we
try?
D
B
D
D
So
I
will
set
a
timer
for
issues
yeah,
so
very
good.
Actually,
so
the
first
cluster
of
issues
is
around
helping
contributors
be
able
to
contribute
so
adding
new
people
to
the
contributor
sheet
engaging
new
contributors.
D
People
want
to
do
things,
but
they
don't
know
how
to
help
so
quite
succinctly:
how
can
we
empower
contributors
or
better,
I
guess
on
board
them
new
people
and
how
can
we
help
them
find
their
way
into
something
that
an
action
that
they
can
take
in
the
community.
D
And
then
the
second
one
distributions
that
some
people
seem
overloaded,
some
groups
are
trying
to
do
too
much
and
in
coordinating
lots
of
things
are
dependent
on
other
people
hard
to
predict
to
get
something
some
some
things
done
sometimes
so
this
one,
I
guess,
is
really
like.
How
do
we
better
balance?
What
we're
taking
on
and
maybe
better
balance
the
amount
of
work
workloads
in
particular
groups.
D
Or
your
group,
if
one
of
you
wrote
this
and
because
you're
flagging
that
and
the
third
one
is
around
our
calls
and
we
sort
of
it
seems
like
respecting
focus
respecting
the
time
you
know
my
my
action
item
here
would
be
to
you
know,
follow
the
gravity's
protocol
tec
protocol
guide
call
guide,
maybe
that
that's
something
that
we
should
revisit
in
the
beginning
of
each
meeting,
just
to
remind
ourselves
as
yeah.
So
that's
potentially
one
of
the
action
items.
D
I'll,
let
you
know
there's
one
minute
left.
So
four
minutes
is
starting.
D
D
D
Nudge
people
to
check
calendar
links
and
prepare
for
meetings,
so
we
are
trying
that
we
are
trying
that
now
with
ivy
sending
reminders
for
agendas
and
nudges
for
for
calendars,
but
maybe
there's
something
more.
We
can
do
need
to
tell
the
other
people
right
after
sprint
planning
about
the
issues
I
need
for
them.
D
D
Go
to
less
meetings,
that's
overload,
so
maybe
we
do
meeting
pro
to
call.
It
will
be
here.
B
Be
load
workload.
D
Practice
start
community
building
rituals
more
more
often,
oh
juan.
I
can't
move
your
your
for
some
reason.
This
your
thing
is
stuck.
Oh
here,
sorry
practice
turn
community
building
rituals
more
often
icebreakers
having
a
moment
during
each
call
for
people
to
pick
issues.
Okay,.
D
Okay,
community
have
a
hand
holder
guide
for
new
dc
docs
were
overwhelming.
It
took
me
a
month
to
get
at
all
savvy
and
it's
going
to
be
community,
or
is
that
load?
That's
community?
We
could
have
something
similar
from
transparency
audit,
but
for
calls
quality
share
it
only
with
the
call
moderator
in
between
stewards.
So
no
one
feels
exposed.
D
Let's
practice,
call
moderation,
tag,
team
and
call
and
check
out
the
awesome,
carlos
I'm
sorry.
Let's
practice
call
moderation
tag
team
and
calls
the
calls
and
check
out
on
carlos's
awesome
meeting
protocol
all
right.
We
have
a
lot
of
great
ideas
here,
have
more
organization
for
set
problems,
so
we
know
what
we
can
look
for
and
new
people
wanting
to
contribute.
D
A
single
point
of
contact
to
focus
on
ensuring
new
contributors
have
paths
issues
good.
First,
issues
in
the
board,
personal
reach,
tracking
new
members,
sprint
planning
refinement,
keep
an
eye
on
overloading
and
call
to
mind,
gravity
tesol,
called
protocol
guide
at
the
starting
calls
in
a
simple
way,
link
to
the
full
document.
All
right.
D
So
we
have
a
lot
here.
Our
goal
is
going
to
get
is
going
to
be
to
find
two
one.
Maybe
two
of
these
that
are
the
most
impactful
to
to
to
our
doing
better
and
our
next
sprint.
So
here
is
where
I'm
going
to
ask
everyone
in
our
last
12
minutes
to
tell
to
express
what
they
think
will
be
the
one
or
two
most
important
and
then
we'll
vote
for
them.
D
So
if
I
go
first
actually
hold
on
one
second,
because
we
have
we
have
too
many
individual
ones
in
each
of
these.
Okay,
so
can
I
ask?
Can
we
vote
on
which
of
these
three
we
focus
on
for
the
next
for
the
next
sprint?
So,
if
you'll
take
the
pink
stars,
just
vote
for
one
section
and
then
we'll
pick
one
or
two
from
that
section.
D
Kun
we're
voting
with
stars
moving
stars
on
the
page.
B
D
All
right
so
seems
like
we
have
a
very
large
cluster
on
meeting
protocol.
I
certainly
agree
so
of
these.
D
Okay,
all
right
so
of
these
go
to
less
meetings,
share
those
tasks
we
need
help
with
when
getting
overloaded
need
to
tell
the
other
people
right
after
sprint
planning
the
issues
I
need
to
help.
I
need
help
for
if
someone
feels
overloaded
should
ask
for
help
nudge
people
to
check
calendar
links
and
prepare
meetings
to
follow
the
agenda
and
the
amount
of
time
for
each
topic.
D
D
D
This
is
all
very
good
so,
which
ones
will
we
actually
be
able
to
do
I'd
like
to
hear
from
the
other
stewards
in
the
call,
so
I
will
pass
it
around
and
please
do
share
your
thoughts
juan
carlos.
Can
I
start
with
you.
A
Well,
I
think
that
all
of
them
are
really
important,
but
I
was
thinking
in
the
one
that
I
wrote
and
is
about
community,
and
I
think
that
I,
this
is
something
that
I
can
like
start
doing
and
is
to
practice
certain
community
building
rituals,
more
often,
maybe
to
make
icebreakers
for
people
to
know
each
other,
like
informally.
A
But
that
is
a
very
good
community
building
exercise
and
the
other
idea
is
to
have
transition
loans,
and
this
that
sometimes
we
have
too
much
calls
in
a
row
and
when-
and
we
are
in
this
hurry
going
from
flow
to
another.
A
So
it
would
be
nice
to
have
like
a
five
minute
transition
transition
launch
between
long
sessions
to
like
yeah
to
like
ease
the
body
to
like
ease
the
mind,
have
some
breathing
exercises
or
some
like
warm
up,
so
that
we
can
have
like
this
active
process
that
helps
us
to
to
manage
our
our
attention
and
our
and
and
our
disposing
to
the
different
meetings.
A
A
B
Oh
okay,
thanks
is
it
should
we
share
the
ones
we
thought
were.
A
good
idea
is
that
it.
B
B
I
think
it
really
cool
if
we
could
have
like
a
hack
session
together
to
make
issues
that
would
be
focused
to
contributors
like
someone
that
is
joining
that
it's
in
the
first
week,
and
they
want
to
do
something
like
that.
We
had
the
list
on
github
that
were
labeled
for
contributors
and
then
those
were
very
easy
to
be
onboarded
to,
and
then
maybe
we
could
create
like
a
couple
from
each
working
group
and
have
them
it's
easy
to
like
give
something
to
people
when
they
feel
like
doing
something.
B
B
B
Excuse
me
guys,
but
you're
freaking
off
a
lot
that
you
should
try
to
to
log
in
and
out
of
discord
that
sometimes
works.
Sorry
for
for
interrupting
by
the
way.
C
Thanks
keown
stephanie
did
he
hears
that
libby
passed
you
oh.
A
I
I
didn't
hear
it.
It
was
good,
sorry
yeah
for
me
like
the
thing
we
could
improve,
but
it
depends
on
each
one.
But
when
someone
feels
a
very
overload,
I
think
they
should
be
like
saying
and
for
example,
people
like
me.
I
have
a
lot
of
time
and
I'm
glad
to
help
and
yeah
I
mean,
of
course
not.
Everyone
can
do
all
the
tasks,
but
just
communicate
better.
When,
when
you
feel
overload
and
ask
for
help,
I
think
that's
nice
and.
C
Cool,
so
the
I
really
like,
I
I'm
surprised,
I
didn't
write
this,
but
having
a
moment
during
each
call
for
issues
and-
and
it's
not-
I
really
like
this
issue
and
I
think
it
goes
well
with
what
livia
said
where
we
need
to
probably
first
focus
on
making
sure
there
are
some
issues
that
are
contributors
in
our
in
our
group.
But
it's
a
really
nice
practice
and
it's
not
about
leaving
the
space
open
like
who
wants
to
pick
issues
hell.
No,
never
do
that.
C
Please,
just
like
hey
we're
going
to
do
around
and
see
who's
working
on
in
this
you
know,
and
if
you
want
to
work
on
an
issue,
let's
pick
one
and
then
go
and
make
put
everyone
on
the
spot
and
encourage
them
to
say
no.
If
they
don't
want
an
issue,
but
they
everyone
has
to
have
their
moment
to
do
that
and
the
other
one
that
I
I
really
liked
was
the
meeting
protocol
that
I
made
we
have.
C
We
keep
getting
derailed
in
our
calls,
and
I
feel
like
most
of
our
calls,
could
be
half
an
hour
honestly
if
we
just
like
actually
stick
to
the
agenda
and
then
try
to
end
early,
and
I
will
pass
it
to
craig.
If,
if
your
internet's
working.
D
A
Cool
gosh,
as
you
may
have
noticed,
I've
been
hopping
in
and
out,
I
missed
all
kinds
of
stuff
and
I'm
not
looking
at
the
mirror
board
just
so
that
I
can
listen
to
you
guys
and
doing
my
best.
A
I
don't
really
haven't
been
useful
to
add.
I
just
don't
know
exactly
what's
happening.
So
sorry,
thanks
yeah.
D
If
you're,
if
you're
not
looking
at
the
mirrorboard,
it's
gonna
be
hard,
but
I'm
glad
you're
here
and
you're
listening,
that's
cool
and
when
you
have
a
chance,
do
and
check
out
in
the
calendar
interest
entry
is
the
agenda
and
then
the
agenda
is
the
mirror
board,
and
you
can
see
everything
that
we
were
talking
about
during
this
retrospective
and
I'm
sorry.
We
are
out
of
time
normally
yeah
these.
These
do.
D
These
can
take
a
little
while,
but
I
am
glad
that
everyone
had
a
chance
to
to
do
this
retrospective.
I
think
that
we
can
also
improve
the
retrospective.
So
that's
another.
That's
an
action
item
that
I'll
take
for
myself
and
I
think
what
what
came
out
of
this
is.
You
know
some.
You
know.
Definitely,
let's
figure
out
how
to
encourage
the
meetings
to
be
more
focused
and
using
the
protocol
from
gravity.
D
I
definitely,
I
think,
that's
a
really
good
one
too,
and
maybe
that
one
will
sort
of
solve
this
one.
If
we
could
end
meetings
a
few
moments
earlier,
that'll
give
a
break
between
the
back
to
back
to
back
that
we're
feeling
and
the
the
one
that
livia
prioritizing
onboarding
calls
and
then
practice
community
building
rituals,
I
think,
are
two
nice
action
items
that
we
can
implement
this
next
sprint.
D
So
I
mean,
if
someone
feels
overloaded,
should
ask
for
help.
I
feel
like
that's
a
given.
That's
that's
always
a
given,
so
we
shouldn't
like
we
should
encourage
to
to
modify
all
of
these
so
that
we
take
these
actions
into
into
account.
But
I
would
say
these
three
or
these
four
we
can
in
corporate
sprint.
D
Yeah:
okay,
we're
at
the
top
of
the
hour
thanks
for
coming
I'd
love
for
us
to
also
spend
some
time
in
our
sink
on
next
wednesday
to
share
a
little
feedback
about
how
this
retrospective
went
and
maybe
how
we
can
do
this
better
too
hope.
Everyone
has
a
good
next
meeting.
Thank.