►
From YouTube: TEC Sprint 4 Retrospective “A rising Tide”
Description
Timecodes:
00:00 - Intro
03:40 - What went well
11:23 - Could do better
43:19 - Actions to improve
🙏 Thank you for watching! Hit 👍 and subscribe 🚩 to support this work
🌱Join the Community🌱
on Discord https://discord.gg/uM4ZWDjNfK
or say hello on Telegram https://t.me/tecommons
Join the conversation https://forum.tecommons.org/
Follow us on Twitter: https://twitter.com/tecmns
Learn more http://tecommons.org/
A
All
right
welcome
everyone
sprint,
four,
a
rising
tide
time
to
sail
away
and
say
goodbye
and
get
ready
for
sprint,
five
tomorrow,
okay,
so
everyone
knows
this
field.
Scrum
theory
is
founded
on
empiricism
and
lean
thinking,
and
the
purpose
of
the
retrospective
is
to
be
introspective
and
to
see
what
we
did
well,
what
we
can
do
better
and
then
to
take
concrete
actions
to
improve.
A
It
is
fundamental
to
the
the
idea
of
agile
planning
and
keeps
us
constantly
able
to
react
to
context
and
to
circumstances
as
they
change
so
I'd
like
everyone
to
take
a
few
minutes.
I
don't
want
to
take
too
much
time
doing
this
and
I
did
go
through
and
close
a
bunch
of
issues,
but
have
a
look
at
the
sprint
board.
Have
a
look
at
what
you've
done.
What
do
I
say
here
have
a
look
at
how
you
actually
did
the
work
that
you
prioritized
two
weeks
ago?
Did
you
do
it?
A
Did
something
else
come
up?
Do
you?
Can
you
find
out
ways
to
to?
I
don't
know:
do
you
need
to
prioritize
differently
coming
up
and
yeah?
Why
have
you
is
there
anything
you
haven't
completed?
Why?
I
think
we
actually
did
really
quite
well
of
the
issues.
Almost
more
than
half
of
them
was
closed
and
I
do
think
there's
still
some
issues
in
here
that
either
can't
be
closed
because
of
you
know
technical
technical
issues
or
just
little
blockers,
so
they
have
to
be
pushed
into
the
new
sprint.
A
A
A
I
hope
everyone
is
and
that
it's
working
out
a
reminder
tomorrow
is
our
sprint
planning,
so
any
label
that
you
want
to
be
a
candidate
for
the
next
two
week
of
works
tag
with
next
sprint
and
when
we
do
our
planning,
we
will
filter
by
next
sprint
and
those
are
only
the
issues
we're
going
to
look
at.
So,
if
there's
important
work
in
your
working
group,
please
make
sure
you
tag
it.
A
A
A
Okay,
all
right,
so
this
is
the
fourth
time
we're
doing
this,
so
I
think
we're
all
pretty
used
to
the
process.
I'm
just
gonna
grab
my
phone
four
minutes.
We
will
do
what
went
well
and
I'll.
Let
you
know
when
we
have
a
minute
left
and
then
we
can
yeah,
then
we
can
review
it.
If
we
need
more
time,
then
we
can
always
add
another
minute
and
the
timer
is
starting.
A
A
B
A
C
C
C
C
C
C
I
got
a
lot
of
help
in
my
different
areas
from
the
team
found
a
content
contributor
in
mitch
and
couldn't
be
happier
feel
really
good
about
the
potential
of
source
cred.
I
like
the
hustle
from
everyone
discord.
Groovy
bot
is
fun,
especially
for
priests.
Client,
graviton
training
is
mind.
Blowing
every
time.
Effortless
collab
on
github.
A
A
A
D
D
B
A
F
Yeah
yeah,
I'm
nodding,
I'm
just
searching
for
the
unmute
button.
All
right
could
be
better
more
people,
people
helping
hatcher
on
boarding,
regular
updates
on
progress
inside
issues
having
an
open
list
of
token
engineers
in
the
space
where
everyone
can
contribute
to
and
add
names,
re
checking
out
more
proposals,
shilling
proposals
that
are
already
on
the
forum
and
bringing
attention
to
them
contributors
have
a
hard
time
to
get
feedback
on
the
work
they're
doing
every
week.
F
F
Praise
quantification
discord,
telegram
handles
relation
more
contributors
coming
committing
to
issues
walking
the
line
of
the
regenerative
token
economy
against
funding
public
goods.
People
need
to
praise
themselves,
especially
on
meetings.
They
lead
streamline
onboarding
for
new
contributors
and
having
issues
assigned
to
them
immediately
explaining
to
people
the
base.
Layer
is
a
regenerative
token
economy,
but
the
more
important
piece
is
the
engineering
society-esque
nature
of
our
organization,
getting
dates
in
the
calendar
for
reaching
out
to
hatcher.
This
has
been
really
tough
for
me.
I
could
make
it
a
higher
priority.
F
A
G
Sure
I
think
one
thing
that
was
missed
in
the
what
we
did
well
with
the
transparency
audits
in
the
transparency
group.
I
think
that's
like
next
level,
because
I
don't
I
haven't
seen.
I
haven't
seen
a
successful
attempt
at
that
in
the
dow
space,
so
I
I
think
I
I
have
a
lot
of
confidence
that
we're
going
to
be
pretty
monumental
there.
I
also
put
some
very
confusing
ones
in
what
we
could
do
better,
so
walking
the
line
of
regenerative
token
economy
versus
funding
public
goods.
G
This
is
the
collective
psychosis
thing.
This
is
this
like
challenge,
that's
like
no
we're
going
to
do
what
is
normally
charitable
work,
but
we're
going
to
make
a
profit
while
we
do
it
and
it's,
but
it's
not
about
the
profit.
It's
about
doing
the
work,
but
the
work
deserves
respect.
It's
a
really
hard
thing
to
communicate.
I
don't
think
we
mastered
it
yet,
but
it's
authentic.
We
have
to
be
authentic
with
our
community
that
hey,
if
you're
a
hatchery,
you
might
make
money,
you
know
and
we
it
would
be
wrong
not
to
tell
them
that.
G
That
is
like
a
shelling
point
for
token
engineers
to
come
out
of
their
silos
and
share
ideas
and
meet
each
other
and
creating
value
through
the
structured
community.
I
don't
think
we've
really
talked
about
that
at
all,
but
that's
really
the
value
add
that
we
that
we're
creating
and
I'll
pass
it
to
olivia.
B
I
superb
second,
the
the
transparency
audit
and
I
put
there
the
the
whole
like
mutual
accountability
pack
that
I
think
is
getting
grounded
and
I
feel
like
we're
already
doing
that
it
was
very
like
it
emerged
very
organically
and
then
now
we're
just
formalizing
it
together
with
the
audit.
That
was
an
awesome
idea
and
and
then
on.
What
can
go
better,
that
I
feel
like
from
the
working
groups
that
are
not
so
ready
to
hatch.
B
Maybe
is
the
hatchery
on
boarding
that
we
need
to
onboard
a
lot
more
people,
and
maybe
we
need
to
bring
more
people
to
help
on
that,
because
it's
a
lot
of
like
a
time
consuming
thing
one
hour
to
onboard
each
person
so
and
it
takes
two
of
us
to
do
so.
So
it's
like
two
hours
of
our
collective
time
to
put
into
that.
B
So
the
more
people
we
have
interested,
the
better
we'll
get,
and
I
think
we
can't
forget
how
the
proposals
are
super
important
because
it
helps
the
hatcheries
also
when
they
get
in
and
they
see
what
is
there.
What
are
we
gonna
fund?
This
is
like
an
immediate
osmosis
learning
for
everything
we're
doing
it's
like.
Oh
we're,
supporting
this
project
and
it's
very
easy
to
look
at
them.
So
maybe
we
can
just
expand
the
shilling
process.
B
We
we
do
for
these
proposals,
so
more
people
feel
interested
to
come
in
and
put
their
proposals
there
and
it's
not
like
a
dead
end
where
they
just
come
to
the
thursday
call
and
talk
about
it.
But
if
we
had
a
lot
of
movement
in
those
proposals
like
commenting
on
it,
asking
questions
engaging
with
the
people,
I
think
that
would
be
really
cool
and.
H
I
think
that
not
the
time
that
development
is
is
is
taking
or
it
has
taken
slowing
down,
has
given,
given
the
rest
of
the
groups,
time
to
just
consolidate
all
the
all
the
issues
that
were
just
a
little
bit
maybe
delayed
and
has
given
us
as
a
whole
organization
at
the
time
that
maybe
we
needed
to
not
write
so
much
and
consolidate
everything
that
was
being
being
worked
on,
perceive
that
that
has
been.
Although
it
has
delayed
everything,
it
has
had
a
good
a
good.
H
H
Sorry
about
that,
my
connection
is
not
working
very
well,
so
I
just
perceived
that
we,
the
rest
of
the
groups,
needed
to
get
some
time
and
not
not
to
you
know
to
try
to
close
those
issues
that
were
we.
We
had
this
feeling
of
being
late
and
now
and
now
it's
like
everything
is
aligned
and
getting
more
and
more
ready
for
for
the
hatch.
So
that's
my
my
personal
sense
I'll
pass
it
juan.
A
I
J
I
J
Let's
say
trying
to
make
the
best
working
group
and
don't
think
of
the
it's
like.
We
are
working
on
the
same
lane
line
and,
for
example,
yesterday
I
was
talking
with
nate
and
we
were
discussing
like
what,
in
the
future,
for
example,
nh
wants
to
make
another
transparency
working,
but
I
was
feeling
like
man,
I
don't
see
it
happening,
it's
better
to
work
together
and
yeah.
I
I
have
this
vibe
or
the
community
for
the
community
and
that
I.
J
I
J
D
D
I
felt
that
everyone
took
the
time
and
and
the
effort
to
put
up
with
that
and
and
sync
with
everyone
and
we
managed
to
import
everyone,
so
that
went
well
also
the
the
audit
that
septimus
did
it.
I
think
that
went
very
well
for
me
at
least
I
really
like
that
that
went
well
and
the
things
that
we
could
do
better.
I
do
think
as
liberation.
D
I
myself
probably
underestimated
the
effort
on
time
that
took
to
onboard
people
it
was.
I
didn't.
I
didn't
think
it
was
such
a
natural
organic
process
which
is
part
of
our
cultural
build.
So
I
think
that
we
could
do
better
at
helping
on
the
onboarding
process.
Maybe
on
the
proposal
aspect.
Yeah,
that's
that's
my
feedback
on
that.
Back
to
you.
F
F
Definitely
what
I
noticed
from
my
perspective:
onboarding
new
contributors
somehow
smoothly
and
giving
them
immediately
an
overview
of
the
issues
or
the
tasks,
the
tasks
they
can
pick
up
and
at
that
at
the
same
time
it
is
important
that
these
issues,
whether
they're
documented
in
github,
are
really
good
this
and
descriptive.
So
they
have
immediately
everything
and
like
no
dependencies
with
other
people
to
even
begin
a
task
right.
C
Yeah,
that's
why
down
here
I
have
do
we
have
a
job,
I
mean
because
most
other
discords,
they
do.
They
have
a
job
board
and
we
then
are
responsible
like
for
each
individual
group
like
I,
I
don't
know
what
someone
may
need
in
onboarding.
I
don't
know
what
somebody
may
need
in
comms.
If
you
actually
get
on
someone,
that's
really
good
at
social
marketing.
We
need
to
get
that
person
lined
up
and
going.
You
know
what
I
mean
like.
C
For
instance,
we
just
had
a
really
credible,
front-end
dev
show
up
and
we
did
work
together
really
quickly
to
like
find
a
space
for
them,
and
that
was
really
good.
I'm
actually
really
proud
of
us
because
he
just
kind
of
just
showed
up,
but
he
has
credibility
and
credentials
and
he
can
work
and
we
did
throw
him.
So
we
threw
him
a
bone
and
I'm
really
glad
we
were
able
to
do
that.
C
He
was
directed
to
go
there,
but
I
think
if
we
had
something
already
established
like
what
marco
was
saying,
whether
it's
a
github
issue,
but
it's
in
the
discord
it's
there
for
people
to
see
where
they
can
contribute
without
having
to
actually
ask
us
all
these
questions,
then
they
know
exactly
where
they
should
go
or
exactly
who
they
should
talk
to,
and
then
we
can.
We
can
help
direct
them
better.
C
Yeah
I
I
would
really
like
a
social.
I
I
mean.
I
know
we
have
people
involved
in
the
social
media
aspect,
but
I
don't
know
how
well
we
coordinate
that
which
is
going
to
be
important,
because
it's
one
thing
but
before
we
launch,
but
once
we
are
launched,
for
instance,
you
know,
there's
really
nothing
bigger
in
crypto
than
twitter,
it
just
it
re.
There
really
isn't
and
we
need
to
shill.
C
C
You
don't
now.
If
we're
going
to
look
for
token
engineers,
you're
going
to
need
to
be
able
to
talk
to
some
of
these
people
and
they
speak
a
language
above
my
goddamn
comprehension
sitting
in
there
in
the
advanced
sessions
that
they
are
now
is,
is
mind-blowing
stuff,
and
it's
it's
very
difficult.
Now
they
are
patient,
incredible
people
and
they're
all
engaging,
and
you
can
ask
them
all
kinds
of
questions,
but
if
you
don't
have
any
understanding
or
basis
on
what
they're
doing,
how
are
we
supposed
to
help
them
build
what
they
want?
A
A
E
Let's
see
yeah
dishing
praise
to
yourself,
it's
okay!
It
took
me
a
long
time
to
do
that
so
yeah
you'll
figure
it
yeah.
I
guess
without
the
benefit
of
the
board
and
whatnot
and
halfway
listening,
I,
I
guess
I'll
just
after
like
a
step
back
perspective
in
that
we're
all
so
buried
in
so
many
details,
but
there's
just
so
much
amazing
things
being
built
right
now.
A
Cool
thanks
for
that,
okay
and
I'm
just
gonna,
share
my
thoughts
too.
I
mean
what
we
did
well,
I
like
the
discord,
server,
transparency
contributors.
We
have
some
really
like
super
motivated,
really
skillful
contributors
that
are
are
starting
to
find
us
and
want
to
find
ways
to
contribute
with
us
and
that's
becoming
more
and
more
evident,
which
is
really
really
a
testament
to
what
we're
what
we're
putting
together.
A
I
think
that's,
really
cool
praising
ourselves.
Hey,
marco,
I
also
didn't
know
we
were
supposed
to
do
this
or
that
it
was
even
polite
to
do
this.
So
I've
started
to
add
myself
at
the
end
of
the
list
of
people,
I'm
praising
if
I
was
involved
in
it,
it's
sort
of
like
a
little
bit
bashful
to
do
that
myself,
but
I
I'm
gonna,
try
to
do
it,
so
so
it's
so.
We
can
also
set
a
good
precedent,
so
everyone
does
do
it
too.
A
I
want
to
know
how
we
can
help
common
swarm.
I
mean:
what
can
we
do?
You
know?
Is
it
resources?
Is
it
like?
How
can
we?
How
can
we
help?
I
don't
know
what
it
is,
but
I'm
super
curious
to
to
try
to
find
a
way
to
to
help,
especially
if
momentum
is
lost
and
then
for
hatcher
onboarding
and
hatcher
outreach
man.
We
did
like
we've
done
a
really
great
dress,
rehearsal.
A
We've
really
practiced,
we've
refined
our
our
presentations,
and
I
think
we
all
have
a
lot
of
experience
under
our
belt
now
and
we
can
really
ramp
up
how
many
like
how
many
people
were
outreaching
too.
I
think
for
me:
it's
really
difficult
just
to
get
those
calendar
dates.
You
know
it
takes
like
20
30
minutes
just
to
put
an
hour
calendar
slot,
and
I'm
really
I'm
really
struggling
to
get
past
that
hurdle
and
I
would
say,
projects
as
well.
We
need
to
focus
on
and
we
could
do
that
better.
A
We
didn't
do
it
very
well
this
sprint,
so
I
would
say
for
this
friend
in
particular:
we've
done
it
well
in
other
sprints,
but
for
this
print
in
particular,
we
can
do
it
better
in
the
next
sprint
and
then
my
time
is
up
so
cool.
So
the
next
step
is
going
to
be
to
vote
on
the
two
that
you
think
are
we'd
like
to
address
and
I
would
say
there
seems
to
be
some
themes
around
hatcher
and
onboarding
onboarding
hatchers,
amplifying
proposals
and
reaching
out
for
more
proposals.
A
Token
engineers
focusing
on
token
engineers
well
yeah
and
the
rest
seem
to
be
singlings.
I'm
not
sure
what
this
means
more
contributors
committing
to
issues.
That
sounds
good,
not
bad,
so
maybe
it's
maybe
it's
a
different
meaning
than
I
understand,
but
I
would
say,
take
two
stars
each
person
and
put
it
on
the
one
particular
issue
that
you
think
we
should
focus
on
that.
You
think
we
should
football
actions
to
make.
A
A
A
Cool
all
right,
so
if
we
zoom
in,
we
see
a
clustering
here,
oh
new
one
here,
so
one
is
more
token
engineers
in
our
comm
having
an
open
list
of
token
engineers
in
the
space
where
everyone
contribute
and
add
names,
yeah,
that's
a
fantastic
idea
yeah.
So
we
have
a
nice
cluster
here
and
a
nice
cluster
and
helping
and
hatcher
onboarding,
which
is
fantastic.
A
A
G
J
Well
being
honest,
I
I
think
right
now:
it's
it
changed,
for
example
yesterday
and
they
were
working
so
hard.
Yesterday
night
they
sing
with
paolo
vivian,
sam
working
and
then
same
was
all
night
working.
I
think
the
worst
part
was
born,
I
mean
yeah,
I
mean
I
don't.
I
don't
know
if
I'd
be
showing
saying
that,
but
sam
was
not
feeling
like
yeah
super
motivated,
but
he
finds
the
motivation
and
I
feel
he's
working
like
since
yesterday.
J
G
It's
not
about
bad
feelings,
it's
more
just
like
how
can
the
non-tech
community
engage?
You
know
like
how
I
I
know
like
on
the
dev
side.
We're
stuck
it's.
It
is
what
it
is,
but
you
can
just
type
it
too
like
if
you
can
think
of
any
ideas
on
how
the
rest
of
our
community
can
swarm
them.
You
know
and
help
in
some
ways.
J
J
H
A
G
I
G
Onboarding
call
contributor,
onboarding
brainstorm
to
help
motivate
and
support
the
common
swarm
more
memes
one,
someone
dedicated
to
proposals
exclusively
next
sprint:
volunteers
for
being
hatch,
outreachers,
prioritize,
hatch,
outreach
above
all
else
for
one
more
contributors
continue
focusing
on
content
targeted
for
te
expert,
infographics
targeted
at
love
to
our
devs,
coordinating
a
team
for
socials
understanding.
What
is
token.
D
C
C
A
A
I
think
these
are
all
right.
I
just
need
to
move
this
a
little
bit.
I
think
these
are
oh
well
one
each,
but
around
the
hatcher
outreach
and
proposals
doesn't
really
seem
that
that
got
enough
stars,
though
assigning
taking
care
of
and
updating
and
closing
issues.
Awesome
totally.
Would
that
would
be
amazing
and
awesome
so
and
we
are
a
great
team,
don't
get
complacent
cool,
so
we
can
definitely
not
get
complacent.
A
So
I
think
our
actions
are
make
an
open
list,
so
we
can
open
a
github
issue
to
make
an
open
list
and
figure
out
how
we
can
start
to
like.
We
can
figure
this
out
this
sprint,
but
we
can
take
this
as
an
action
in
the
sprint
and
more
from
like
a
process.
Standpoint
is
assignees
updating
and
closing
our
own
issues
more
regularly.
I
think
that
can
also
help
us,
especially
in
terms
of
like
communicating,
what's
happening
on
each
particular
issue
as
well
as.
A
B
C
I
I
have
been
I've
been
speaking
with
sean
and
he
we
are
going
to
do
this,
but
he's
just
very
busy,
and
I
definitely
think
that's
a
great
idea
too,
but
he
is
very
busy
and
it's
also
going
to
be
difficult
for
him
to
dedicate
the
time
to
now
then
try
and
take
part
in
whether
it's
even
being
a
steward
or
helping
with
other
token
engineers
I
mean
otherwise
he's
going
to
be
using
part
of
his
lab
session.
To
then
tell
the
group:
hey
come
be
a
hatcher,
it's,
he
is
very
busy.
C
A
Yeah,
I
agree.
My
understanding
too
is
why'd,
you
extremely
low
bandwidth,
and
it
would
be
phenomenal,
so
just
keep
us
abreast
of
the
project
of
the
progress,
but
it's
a
good
idea,
and
if
not,
why
did
you
perhaps
somebody
else
in
our
list
of
te
engineers
that
will
do
this?
This
print
will
come
to
mind
thanks
for
adding
that
olivia
all
right.
I
went
on
to
sprint
five.
J
On
the
things
that
also
went
well,
we
didn't
mention,
and
the
omega
working
group
looks
so
exciting
and
there
is
a
lot
of
yeah
philosophical
questions
that
would
help
to
understand
the
token
engineering.
And
what
really
I
mean
they
are
talking
a
lot
of
issues.
We
were
mentioning
yeah,
just
saying
that
they
are
doing
an
amazing
work.