►
From YouTube: M365 Maturity Model - May 2021
Description
May 2021
Recorded:
May 18, 2021
Topic:
Power Platform through the lens of the Maturity Model
Overview:
In this session, April Dunnam and Hugo Bernier join the discussion on the Power Platform and how the Development and Customization competency could be used to improve your adoption of the Power Platform. We also discuss how the Power App CAT Teams; Power App Maturity Model can help.
Agenda:
• Practitioner overview
• Introduction to the Maturity Model
• Latest artifacts for the Maturity Model
• How to get more involved
• Picture time with the Together Mode!
Monthly Discussion: Power Platform through the lens of the Maturity Model
Hosts:
• ⭐Guest stars⭐ April Dunnam & Hugo Bernier
• Emily Mancini, Sympraxis Consulting | @eemancini
• Marc Anderson, Sympraxis Consulting | @sympmarc
• Simon Doy, iThink 365 | @simondoy
• Simon Hudson, Novia Consulting | @simonjhudson
B
B
The
the
first
one
is
that
it's
about
creating
a
mechanism
by
which
you
can
benchmark
how
good
you
are
at
a
given
thing,
but
let's
just
pick
one
one:
competency
at
random,
we'll
pick
communication,
because
that
comes
up
a
lot
in
our
discussions.
You
know.
Are
you
one
of
those
organizations
that
really
doesn't
have
a
communication
strategy
and
it's
therefore
completely
open
to
individual
interpretation
about
how
communication
should
take
place
or
do
you
have
a
process
for
doing
communication?
Is
that
process
effective?
Is
it
monitored?
B
If
better
is
what
you
want,
so
you
can
choose
how
at
a
very
granular
level,
you
can
say
we
need
to
be
better
at
this
part
for
whatever
business
reasons
you've
got,
and
these
are
the
steps
and
the
approaches
with
the
technology
support
that
we
can
take
to
get
better
and
that
moving
on
that
lets,
you
lay
out
both
a
business
and
a
technical
roadmap
based
on
what's
possible
in
the
technology
today,
and
the
maturity
model
is
designed
to
be
flexible.
So
when
new
things
come
on,
you
can
take
advantage
of
those.
B
So
it's
not
built
around
the
capabilities
of
today's
technology.
It's
supported
by
them.
Where
do
you
want
to
get
to?
How
good
do
you
want
to
be
at
different
parts?
And
what's
your
organization's
culture
and
drivers?
So
that's
really
important.
It's
not
about
us
telling
everybody
how
they
must
run
their
organization,
it's
about
having
a
flexible
set
of
tools
that
say
yeah,
but
we're
this
kind
of
a
style
of
organization.
B
This
is
not
just
about
the
technology,
but
it
is
about
understanding
how
to
use
the
technology
to
change
your
organization,
and
it
gives
us
a
common
set
of
terminology.
A
set
of
language
where
both
the
technical
people
and
non-technical
people
can
have
that
discussion.
It
creates
a
mechanism
for
strange
enough
communication
within
the
organization
and
finally,
there's
a
this
term
socialization
I
like
to
think
of
it
more
about
being
social
adoption.
B
I
might
be
a
real,
a
real
apostle
for
getting
certain
things
done
with
technology,
but
if
the
guy,
who
sits
next
to
me,
isn't
so
into
the
tech,
maybe
I
need
a
way
for
it.
I
can
carry
him
along
with
my
enthusiasm,
and
so
really
this
is
about
driving
social
adoption
being
able
to
spread
the
love
spread.
B
The
insight
spread
the
demand
and
desire
across
the
organization,
not
just
by
those
people
who
already
wedded
to
using
technology
as
a
tool
for
change
right,
deep
breath
and
we'll
look
at
some
of
the
competencies
right
now.
We've
got
a
set
of
what
is
that
about
eight
competencies
already
developed
when
we
set
out
to
build
the
model,
we
were
very
keen
that
it
should
not
be
driven
by
the
technology.
It
should
be
driven
by
a
set
of
things
that
underpin
effective
businesses
and
every
business.
B
Pretty
much
has
a
need
for
the
things
on
the
right
in
some
form
or
other
collaboration,
communication
management
and
content,
staff,
development
and
training
all
those
kind
of
things.
So
we've
identified
what
a
set
of
different
competencies
are
and
built
a
maturity
model
for
each
competency.
There
is
some
overlap
and
that's
a
good
thing.
We've
tried
to
keep
that
overlap.
It's
sane,
not
not
bright.
You
break
our
heads
too
much,
but
that's
where
we've
got
to
right
now
is
a
set
of
eight
public
competences.
B
We
have
a
number
of
other
competences
that
we're
working
on
some
of
those
are
quite
hard,
but
we're
in
progress
with
infrastructure.
We
are
looking
at
how
to
do
security
and
indeed
debating
whether
it's
different
to
or
the
same
as
or
part
of,
some
of
the
others
and
we're
going
to
work
on
data
analytics,
and
then
we've
created
a
set
of
supporting
articles,
things
that
define
the
principles
of
or
of
some
of
these
competencies
or
describe
how
you
can
effectively
move
from
one
state
to
another.
B
So
those
are
how
to
elevate-
and
let's
just
quickly
remind
ourselves
what
the
different
levels
are.
This
is
one
of
my
favorite
slides
and
I
I
talk
a
lot
with
the
businesses
and
the
people.
I
talked
about
these
levels
100
through
500.,
the
description's
really
important,
I'm
not
going
to
share
it
in
in
words.
Right
now,
you
can
read
that
up
on
the
on
the
microsoft
docs
site,
but
I
do
like
to
pull
call
people's
attention
to
the
keywords
on
the
right.
B
So
so,
if
we
look
at
the
entry
level
level,
100
processes
approaches,
thoughts
are
ad
hoc,
reactive,
uncoordinated,
uncontrolled
and
then,
as
you
move
up,
you
introduce
more
and
more
control
without
necessarily
or
indeed
hopefully,
without
introducing
barriers.
What
you're
trying
to
do
is
remove
barriers,
while
making
your
your
processes,
more
predictable,
better
defined
and
and
ultimately
self-optimizing,
so
they
improve
themselves
through
the
process.
B
A
A
It's
a
discussion
based
monthly
meeting
so
about
the
first
15
minutes
every
month
is
our
quick
review
of
the
maturity
model
and
the
practitioners
and
how
to
get
involved,
and
then
we
spend
the
final
45
minutes
discussing
different
items
depending
on
the
month,
and
this
month
is
the
power
platform.
So
we
can
occasionally
be
changing
our
discussions.
C
C
I
really
think
it
would
make
more
sense
if
you
said
it
this
way
to
you
know
providing
some
tools
that
you
may
have
created
as
you,
if
you
as
you
practice
this
stuff
out
in
your
organizations,
you
can
socialize
the
content,
you
can
talk
to
people,
you
know
on
social
media
and
in
forums
and
things
like
that.
Refer
them
to
the
to
the
content.
You
can
contribute
via
github
the
sharing
and
care
is
and
sharing
is
caring
sessions
that
help
people
understand
how
github
works
can
be
your
on-ramp
to
that.
C
If
github
is
too
complex
for
you,
you
can
always
just
get
in
touch
with
one
of
us
and
make
your
suggestions,
but
we
always
want
to
give
credit
to
people
so
doing
it
through.
Github
is
a
great
way
to
do
that
and
you
could
even
get
go
so
far
as
to
you
know,
presenting
a
case
study
or
a
story
about
how
this
has
gone
in
your
organization
to
this
set
of
people
so
that
we
can
all
learn
from
each
other.
One
of
the
things
that
that
happens
is
people
go.
C
You
know,
sort
of
through
the
the
levels
of
the
maturity
model.
Is
you
start
to
learn
how
to
tell
the
stories
better?
You
know
when
you're,
when
you're,
first
starting
out
at
level
100
with
something
there's
not
much
to
tell
you
know
we're
getting
by,
but
by
the
time
you're
you're
at
level,
200
or
300
or
400.
You
you've
got
some
better
practices.
You've
got
some
things
that
you
can
talk
about.
C
C
Most
of
us
have
our
cameras
on
right
now,
but
that
doesn't
mean
that
we're
not
very
open
to
having
anyone
contribute.
We
really
want
this
to
be
a
an
open
source
community
effort.
The
the
core
team
is
just
a
bunch
of
people
who
you
know,
we've
gotten
together
and
tried
to
give
this
thing
the
the
leg
up,
so
that
it
starts
to
be
useful,
but
we
want
everything
everyone
out
there
who's.
You
know
on
this
call
or
anyone
who
gets
some
benefit
from
it
to
be
able
to
participate,
and
that's
all
I
got.
C
A
Absolutely
and
that's
what
we
have
next,
so
just
a
big
thank
you
to
everyone
who
joined
us
in
april.
You
can
see
on
the
right
and
then
just
to
follow
up
on
what
mark
was
calling
out
david
put
the
link
in
the
chat
to
those
sharing
his
caring
sessions.
But
if
you
want
to
learn
a
bit
more
about
github,
we
have
that
first
time
contributor
session
coming
up
on
monday,
the
24th
and
community
docs
is
already
tomorrow.