►
From YouTube: FY21'Q3 - OKR - SA Demonstration Retro
A
Hi
everyone-
this
is
tim
poffenberger,
and
this
is
a
quick
recap
of
the
solutions:
architecture
okr
for
fiscal
year,
2021
quarter
3
regarding
demonstration
repositories,
the
the
intent
behind
this
was
to
initiate
the
start
of
curating,
a
well-maintained
demonstration
repository
index
that
folks
can
use
and
leverage
to
better
drive
what
they're
demonstrating
to
customers
and
what
good
looks
like
current
state.
We
have
quite
a
few
different
locations
where
demonstrations
are
stored,
some
solutions,
architects,
prefer
gitlab.com
in
their
own
location
or
a
shared
group.
A
Others
use
the
gitlab
demo
hosts
and
others
use
their
own
self-managed
gitlab
instance
the
the
most
popular
variant
that
we've
discovered
was
a
spring
boot
app,
which
is
a
java
web
framework.
There
were
also
some
node.js
projects
that
we
found
in
dot-net
projects
and
python
projects.
Most
projects
today
are
web
applications,
we're
not
seeing
a
whole
lot
of
api
services
or
mobile
apps
or
any
batch
oriented
applications
as
well.
A
One
of
the
things
that
we
were
trying
to
do
was
track
how
demos
are
recorded
and
to
get
better
visibility
into
when
demos
are
being
performed,
and
so
that
we
could
collect
information
about
those
demos.
But
it
wasn't
super
easy
to
do.
Demos
don't
always
show
up
in
chorus
specifically
emia
is
not
allowed
to
record
to
send
their
recordings.
A
A
What's
a
demo
and
not
a
demo,
and
there
are,
there
are
a
myriad
of
reasons
why
essays
kind
of
like
their
own
control,
one
is
when
you're
giving
a
demonstration
you
want
to
be
rock
solid
in
in
terms
of
what
you're,
demonstrating
and
any
variance
or
change
caused
by
you
know.
Someone
else
contributing
to
the
same
project.
It
can
certainly
wreak
havoc
on
the
experience
that
customers
and
prospects
have.
A
There
are
ancillary
efforts.
One
of
them
is
the
sample
data
project
which
allows
us
to
store
as
a
template
or
within
a
template,
a
project
template
data
regarding
previous
issues
and
merge
requests
and
all
that
information
will
be
cure
or
populated
upon
import
of
a
project
which
is
good,
there's
also
a
solutions,
architecture,
architecture,
knowledge
base
and
you'll
see
in
a
little
bit
that
we're
we're
utilizing
that
same
gitlab
group
to
store
the
demo
catalog,
so
I'll
provide
links
to
all
the
slides
and
everything.
But
we
do
have
a
demo
catalog
project.
A
We
also
created
a
30
day
of
demos
that
we
were
able
to
find
spreadsheet
from
chorus
throughout
the
month
of
october
and
or
I'm
sorry
september,
and
then
we
also
did
a
survey.
We
had
eight
people
complete
the
survey
regarding
demonstrations,
how
they
demo
what
features
they
find
valuable.
We
had
17
demos
added
to
the
demo
catalog
project
across
10
different
folks.
So
thank
you
for
those
contributions.
Everyone
feel
free
to
head
over
to
that
demo
catalog
project.
If
you
have
any
questions
and
want
to
get
engaged.
A
So
what's
next
for
q4,
what
we're
hoping
to
do
is
potentially
pitch
ideas
for
for
extending
troops
dot
ai,
to
allow
us
to
get
some
more
visibility
into
when
demos
are
taking
place
and
what's
being
utilized
for
that
demo.
We
haven't
agreed
upon
any
any
set
structure
here
and
we
we
do
want
to
make
sure
that
any
additions
that
we're
making
to
troops
are
in
conjunction
with
any
other
editions
that
other
folks
want
to
be
making,
because
we
certainly
don't
want
to
inundate
all
the
essays
with
lots
of
information
that
they
need
to
record.
A
A
Let
me
go
back
to
the
demo
catalog
project
to
just
showcase.
What
we
have
out
here,
every
image
or
every
issue
is,
is
really
pointing
to
a
particular
type
of
demonstration,
and
you
can
leverage
labels
and,
for
example,
I
needed
to
find
something
a
way
to
demonstrate.
Jira
integration,
and
I
did
a
quick
search
for
jira
and
was
able
to
find
a
integration
demo
with
jira,
and
there
was
a
link
to
the
project
and
instructions
from
joel
kruswick
on
how
to
utilize
this
project,
which
is
great
so
thanks.