►
Description
PnP Webcast around the organizational considerations for SPFx solutions. More details available from https://dev.office.com/blogs/sharepoint-framework-and-organizational-considerations.
A
Welcome
everybody,
business
trip
on
patterns
and
practices,
the
webcast
and
this
time
we're
going
to
talk
about
something
and
not
related,
actually
d,
dive
on
the
development
of
SharePoint
framework,
rather
on
the
organizational
considerations.
So
essentially,
what
are
those
things?
What
you
should
think
true?
If
you
are
a
customer
or
a
partner
or
a
developer
or
an
architect
when
you
are
either
consuming
or
ordering
requesting
somebody
to
develop
a
solution
or
when
you
are
a
designing
and
developing
a
sharepoint
framework
solution?
My
my
name
is
Lazar.
B
A
Indeed,
indeed
so
we
do
not
have
like
mentioned,
we
do
not
have
any
actual
code
within
this
webcast,
but
we
really
wanted
to
kind
of
a
raise
awareness
of
considerations
around
these
k
topics
so
that
the
customers
and
partners
when
you're
taking
a
sharepoint
framework
inter
used.
You
would
actually
think
about
those
things
from
a
day
one
rather
than
thinking
days,
processes
or
considerations
afterwards,
when
something
already
has
been
developed
before
we
go
to
the
actual
content
so
quickly,
introduction
to
the
SharePoint
patterns
and
practices.
A
Sociopath
Patterson
practices
is
coordinated
and
owned
by
the
SharePoint
engineering,
but
we
do
work
with
together
with
community
like
MVPs
and
non
MVPs,
to
provide
code
samples,
guidance
documentation.
We
have
open
community
calls
and
case
studies
on
the
on
the
usage
of
the
BMP
patterns
as
well,
diarrhea
for
on
the
SharePoint
framework
shape
and
adding
model
of
max
of
crafts
and
office
365
APRs
in
general.
The
SharePoint
topics
obviously
quite
often
apply
for
on-premises
as
well.
A
Currently,
the
SharePoint
adding
model
is
tiff
with
supported
in
on-premises
shipment
framework
or
piece
of
ordered
in
2016
sharepoint
2016
later
this
year,
HTTP
AKMs
ship
BNP
is
the
one
address
to
remember
from
where
you
can
find
links
to
all
of
our
web
tasks,
links
and
samples
and
all
of
that
stuff.
Well,
let's
actually
move
into
today's
topic,
so
organizational
considerations.
A
So
let's
actually
talk
about
these
things
and
let's
and
could
true
what
does
it
mean
in
practice
as
an
interactive
discussion
and
together
with
Waldo
but
anyway,
so
the
SharePoint
framework
is
no
doubt
a
new
tool
tool
chain.
So
we
need
to
understand
the
new
tool
chain,
which
has
been
new
requirements
for
skill
set
as
well,
and
so
there
are
a
new
if
you
are
a
classic
shape
on
developer.
This
might
take
some
time
and
we
do
absolutely
acknowledge
that,
and
we
are
here
to
as
an
example.
A
The
BNP
is
here
to
provide
you
guidance
on
how
to
learn
the
new
skill
sets
and
the
toolchain
within
your
company
you
what
you
should
be
also
considering
it's
the
client
side,
like
ER
usage,
essentially
meaning
which
of
the
libraries
you
will
be
using
how
you're,
using
them
and
choosing
the
right
way
of
talking
against
the
sharepoint
and
then
the
last
topic.
Kannamma
in
a
high
level,
is
the
hosting
location,
because
the
client-side
web
parts
of
all
the
SharePoint
framework
solutions
in
general.
A
They
are
actually
based
on
JavaScript,
so
they
are
client-side
implementations
and
which
are
typically
visible
within
the
UI.
Maybe
you
need
to
think
through
where
those
Java
scripts
are
actually
hosted,
because
that
will
actually
have
an
impact
within
your
overall
and
define
so
putting
all
of
these
together,
essentially
quite
simply
means
that
you
should
have
and
Covenants
plan
it
doesn't
matter
if
you're
a
customer
or
if
you
are
a
provider
or
an
isv
or
assistant
integrator.
You
should
have
a
provenance
plan
in
place
to
think
through.
How
do
we
address
this?
A
Let's
say
this
individual
topics,
so
where
do
we
host
the
stuff?
What
is
the
libraries
which
are
using?
What
does
the
news
get
a
new
tool
chain
actually
mean
and
for
your
company?
How
do
we
actually
train
the
people
to
use
the
generic
tool
sets
which
are
required
or
the
news
to
get
to
new
skills
for
the
new
total
chain
and
rambling
on
parole
by
myself
the
world?
Like
anything,
we
want
to
add
on
this
one?
Yes,.
B
You're,
so
as
you,
you
said,
you
should
have
a
plan,
no
matter.
If
you
build
SPF,
X
solutions
or
only
use
them
and
order
them
from
somebody
else,
you
should
have
an
idea.
How
are
you
going
to
to
deploy
them
support
them
from
where
load
them?
How
do
they
work
right?
Because,
if
things
break
you
have
an
idea,
you
have
a
process
in
place.
How
are
you
going
to
solve
the
issue?
So
do
you
have
to
look
up
somewhere
else
because
those
scripts
live
on
a
another
location
or
are
they
a
internal?
B
A
Absolutely
absolutely
and
one
thing
to
consider
but
or
governance
plan.
Quite
often,
then
people
might
freak
out
and
say:
hey
okay,
but
we
don't
want
to
build
60
pages,
worthless
or
governance
plan,
and
that's
not
what
we
actually
mean
with
this.
It
could
be
one
or
two
pages
which
are
essentially
just
defining
hey.
Who
do
I
contact
or
what's
the
process
when
there
is
a
requirement
to
start
doing
a
sharepoint
framework
solution?
So
what
is
the
the
conduct
flow
to
get
started
whose
then,
and
the
person
who
is
requesting
that
stuff
to
be
developed?
A
Who
are
we
kind
of
conduct
where
for
the
development,
who
are
the
persons
who's
going
to
approve
and
validate
and
accept
what
has
been
delivered?
And
then,
if
something
breaks,
because
well
eventually
something
might
break
and
quite
often
in
OIT
is
something
we
need
to
have
that
plan
anyway
in
place.
A
Who
do
we
actually
contact
who's
responsible
of
fixing
the
situation
if
stuff
is
getting
pokin,
and
what's
this
too
late
for
doing
that,
and
because,
obviously,
there
is
a
late
and
defines
the
process
as
well,
and
that's
really
is
dependent
on
what
are
we
actually
implementing
as
well?
Is
it
a
business,
critical
or
not,
function?
December.
You
want
right.
B
And
also
essential
bottom
part.
There
is
that
actually,
this
plan
should
be
as
simple
as
possible,
because
imagine
that
you
have
to
be
able
to
execute
on
the
plan.
So
there
is
no
point
in
creating
a
really
exhausted
plan
that
you
just
put
on
the
shelf
and
nobody
can
use
because
it
is
too
complex
right.
The
point
is
that
you
that
you
have
an
action
plan
that
is
comprehensive,
simple
and
covers
everything
that
you
you
you
need,
and
that
is
actually
made
in
a
way
that
you
can
act
upon
it.
B
So
imagine
that
that
you
would
say
that
your
company
only
accepts
solution
that
are
built
in
react,
so
in
other
words,
you
have
to
have
a
process
in
place
that
will
allow
you
to
verify
that
every
time
you
get
a
solution,
you
can
actually
verify.
That
is
built-in
react
and
not
an
angular
right.
So
you
have
to
have
exactly
the
not
only
in
the
requirements
but
but
also
houses
in
place.
That
will
allow
you
to
to
verify
that
these
requirements
are
met
every
single
time,
sure
sure
absolutely.
A
That's
really
the
key
point.
Now,
let's
actually
move
on
slightly
and
we'll
come
back
on
the
on
the
topics
in
the
following
slides
as
well.
So
when
we're
using
SharePoint
framework
when
we
are
implementing
stuff
on
a
SharePoint
framework,
this
is
how
the
SharePoint
framework
solution
essentially
built.
So
whenever
we
are
deploying
a
SharePoint
framework
solution,
we
actually
deployed
a
manifest
file
to
the
catalog
and
the
manifest
file
is
the
one
which
is
defining.
What
is
the
solution
which
is
available
where
the
javascript
is
being
hosted
and
and
where?
What
does
the
solution
actually
contain?
A
But
the
solution
file,
SB
pkg
file
with
the
circuiting
added
on
that
catalog-
does
not
contain
the
actual
customization.
It
does
not
contain
the
code.
The
code
itself
is
hosted
somewhere.
The
code
itself
can
be
hosted
in
CDN,
open
an
enormously
accessible
CDN.
It
could
be
hosted
in
SharePoint
as
well
on
the
SharePoint
Online,
but
the
key
point
of
form
a
covenant
planning
perspective
is
that
you
actually
define
the
troll.
A
And
that
means
that
if
you
reference
a
random
file
without
any
thinking
from
random
location
from
internet-
and
you
have
a
potential
security
challenge,
which
is
exactly
the
reason
why
you
should
be
thinking
through
the
process
and
having
that
kind
of
a
governance
plan
in
place
which
of
the
locations
which
are
safe?
Where
do
we
actually
host
the
chevra
script?
And
what
does
it
actually
mean
in
practice?
B
If
anyone
is
able
to
update
that
script
without
you
even
knowing
about
it,
then
it
would
be
that
that
in
a
week
or
injian
shoot
in
in
few
to
student
a
time
the
coolness
of
the
script
will
change
and
the
script
will
do
something
else,
then
what
it
initially.
So
you
have
to
have
process
in
place.
You
have
to
know
where
do
you
load
scripts
from
and
what
the
SLA
around
it
is
so
who
is
allowed
to
access
update
these
scripts
and
when
right?
B
A
If
you
need
to
have
a
full
isolation
of
the
off
the
customization
within
a
sharepoint
online,
and
you
don't
want
to
go
through
this
approval
process
and
verification
and
all
Sun
keep
on
using
Addie
model
because
that's
based
on
or
off,
and
it
has
the
permission,
checkups
and
the
isolation
and
the
scripts
cannot
actually
access
on
behalf
of
the
user
functionalities
and
that's
a
really
key
point.
Now.
We've
mentioned
quite
a
few
things
already,
but
let's
kind
of
a
think
these
true
first
from
a
customer
perspective.
A
So
if
you
are
a
customer,
these
are
the
things
which
would
be
the
first
things
to
actually
think
through.
First
of
all,
you
want
to
standardize
your
client
side
library,
and
this
really
actually
is
standardizing
your
JavaScript
library,
what
is
being
used
within
your
shipment
on
lantana.
We
do
support
whatever
libraries
in
SharePoint
framework,
so
you
can
actually
use
view.
Angular
react
handlebars.
It
doesn't
really
matter
what
the
more
libraries
you
put
on
a
page.
A
Essentially,
if
you
have
multiple
webparts
debate,
size
actually
gets
crowing
as
well,
and
also
the
fact
that
if
you
have
multiple
different
libraries,
give
let's
say
developed
by
one
is
three
or
system
integrator,
and
then
they
will
move
on
and
then
after
a
while
in
a
year,
you
will
need
to
do
some
chances.
You
might
want
in
the
big
significant
challenges,
because
you
actually
have
multiple
libraries
and
users,
and
can
you
find
the
scale
for
people
who
understand
those
efforts
as
well?
A
So
it's
an
absolutely
active
practice
to
standardize
the
client
client
side
library
which
is
being
used.
Is
it
a
reactive,
design
wheeler?
Is
it
something
else?
Let's
try
to
speak
on
one
library
rather
than
having
multiple.
You
also
want
to
define
a
policy
for
your
external
scripts.
Essentially,
you
want
to
make
sure
weeks
of
the
external
scripts
can
be
default
can
be
used
and
from
which
location-
and
this
really
comes
down
on,
for
example,
that
what
world
accepts
related
on
the
referencing
external
scripts
from
CDN.
You
need
to
be.
A
You
need
to
know
from
which
locations
are
being
referenced
so
that
those
locations
are
essentially
in
quotes
safe
and
that
refers
to
the
hosting
location.
So
you,
you
probably
want
to
make
sure
that,
where
ever
your
reference
in
external
scripts
or
the
SharePoint
framework
JavaScript
solution
scripts,
the
host
known
location
has
been
defined
so
that
they're
safe
and
you
don't
have
to
worry
about
JavaScript
files
getting
suddenly
updated.
Technically,
you
don't
have
to
refer
external
scripts.
B
That
needs
to
be
patched
and
if
so,
which
ones.
What
is
the
update
office
right?
If
you
have
only
one
it's
way
easier
for
you
to
keep
track.
Let's
say
angular
right.
If
there
is
development
in
that
or
there's
important
patch,
it's
easier
to
follow
only
one
framework
as
opposite
to
become
an
expert
I
mean
view
and
in
angular
and
react
and
handlebars
and
in
everything
else
that
you
might
and
might
not
use
right.
B
B
So
with
that,
you
should
also
ensure
that
you
try
to
use
as
few
libraries
across
the
whole
internet,
as
you
can
do
simple,
to
simplify
the
maintenance
for
yourself
right
and,
as
you
you
said,
the
requirements,
that's
also
a
very
important
thing
to
be
able
to
wrap
all
of
these
requirements
together
and
to
give
that
ahead
of
time
to
either
SI
is
v
or
or
your
internal
iiit,
so
that
they
know
up
front.
What
do
you
require
of
them?
B
And
it
could
be
even
the
case
that
you
require
your
things
to
be
built,
an
angular
where
they
only
to
react
right.
So
it
could
be
their
case
that
even
they
will
say
well,
we
do
not
even
do
it
or
the
price
or
time
we'll
go
up,
because
you
asked
us
to
do
something
in
in
library
that
that
we
do
not
know
turn
tradition.
But
it's
important
to
have
that
discussion
up
front
and
not
when
things
are
already
done.
True.
A
Absolutely
it
should
be
in
the
requirements
of
the
of
the
requests
for
getting
something
moving
regardless
of
the
process
and
the
under
model,
who
is
actually
implementing
that
now
moving
on
to
the
other
side,
so
the
customer,
whoever
the
customer,
is
that
the
Dean
house
customer
is
a
day
actual
customer
and
the
development
happens
out.
First
you're
getting
a
requirements
in
for
a
developer,
architect
perspective.
There's
few
aspects
to
to
acquiesce
well
over
to
the
library
considerations,
the
hosting
considerations.
All
of
them
actually
applies
the
developers
and
architects
as
well.
A
You
need
to
understand
those
requirements,
those
implications
options
and
all
of
them,
but
then
in
the
actual
development.
Obviously
you
need
to
have
a
plan
on
how
do
I?
How
do
we
do
development?
How
do
we
work
as
a
team?
What
is
the
actually
tools
were
using?
What
is
too
simplistic
stuff?
What
is
the
first
control
system,
what
we're
actually
using
or
where
do
we
save
or
or
what?
What
is
the
scripting
tooling,
what
we're
actually
using
and
how
do
we
merge
our
stuff?
And
how
do
we
do
testing?
A
How
do
we
actually
do
integration
testing
degree,
which
is
highly
dependent
on
what
kind
of
solution
it
is?
Is
it
a
one
web
part
this
is
multiple
web
parts.
This
is
a
web
part
with
the
web.
Api
calls
north
on
so
everything
significant
advance
on
on
the
scale
of
the
solution,
but
really
thinking
through
what
is
the
testing
process
around
quality
assurance?
Do
we
have
a
separate
uat
process
where
somebody
goes
some
science
off
before
it
goes
to
the
production
to
be
used?
A
So
what
is
the
promise
we
can
actually
give
for
the
customer
if
there
is
a
requirement
to
do
modifications
which
is
highly
dependent
as
an
example
on
the
chava
script
hosting
location,
because
if
you're,
an
ISV
or
a
system
integrator,
if
you're
hosting
the
cello
scripts
in
your
CDN
or
from
a
centralized
location?
And
you
can
update
that
easily
if
thats,
a
crees
on
the
requirements
and
a
plan
with
the
customer
if
customer
is,
is
in
a
deployment.
B
Absolutely
so,
if
you
go
back
to
two
requirements
that
we
talked
about
before
they
spent
across
things
like
obviously
location
framework,
external
scripts
and
all
that,
and
that
determines
also
everything
that
you
see
here.
So
imagine
that
you
would
be
an
angular
house
when
you
have
a
requirement
to
do
things
in
angular.
You
might
already
have
experience
in
that,
but
imagine
that
you
want
to
expand
your
services,
and
you
want
to
also
be
able
to
do
things
in
react
as
well
so
doing
things.
B
It
reacts
will
probably
be
different
than
doing
things
in
angular
and
that
stands
from
things
like
different
tools.
Different
way
to
test
the
different
quality
checks,
different
coding
style
season
right.
So
you
have
to
have
all
of
that
in
place,
and
that
is
based
on
the
requirements
that
the
customer
gave
you
and
the
same
also
approach
applies
to
testing
right,
because
there
are
frameworks
that
allow
you
to
test
solutions
that
work
better
with
angular
than,
for
example,
in
react.
And
if
you
would
build
savvy
react,
then
you
would
use
in
our
approach
as
well
right.
B
So
that's
that's
also
a
thing
that
you
have
to
take
into
account
that
the
framework
that
that
you
use
or
the
library
that
as
you
use,
determines
your
whole
tool
chain
and
approach
from
coding
guys
to
testing
right
all
of
that
and
also
from
support
or
interview.
There
is
also
an
interesting
point,
so
in
the
past,
actually
that's
a
few
times
that
a
small
shop
would
build
solution
deployed
to
customer
and
then
another
company
would
support
it.
B
Well
in
the
past
it
was
all
c-sharp
net
right,
so
it
was
quite
easy
story
to
support
solution
that
somebody
else
bill
now
with
that.
That's
not
really
the
case,
because
if
you
don't
know,
react
and
you
would
have
to
support
react
solution
that
it
might
mean
that
you
have
to
have
some
additional
ramp
up.
B
So
that's
why
it's
essential
that
you,
before
you
accept
support
supporting
something
you
understand
how
it's
built
by
whom
is
build
and
what
scripts
and
libraries
are
being
used
so
that
you
can
commit
to
it
and
actually
be
able
to
do
it
as
opposite
to
just
accept
it
and
then,
after
the
fact
see.
Oh,
but
its
built-in
react,
we
don't
all
react
to
write
so
so
that
you
would
not
be
able
to
to
deliver
the
SLA
that
you
promised
Rachel.
Yes,.
A
Sorry,
go
no,
no,
no
I'm
thinking
through
this
and
going
through
the
previous,
slides
and
previous
slide
on
this
line.
One
of
the
things
what
I
actually
before
we
kind
of
a
ramp
up
on
the
on
the
webcast
as
well,
but
if
one
of
the
kind
of
I
have
a
chat
with
you
while
I
cam
is
that?
Well
somebody
listening
this
webcast
might
feel
like
a
me,
but
this
isn't
this
kind
of
a
making
the
SharePoint
framework
solution.
Development
super
super
complex.
All
of
these
considerations.
B
A
On
that
one,
what
are
you
ready
intact?
There
was
one
way
of
doing
things
because
yeah,
essentially
in
a
farm
solution,
time
frame,
we
had
a
different.
We
had
a
different
t-shirt
vb.net.
There
was
multiple
other
options
and
an
ulcer
sharepoint
customizations
can
be
always
done
in
multiple
ways.
Right.
B
But
in
the
past,
so
if
you
go
back
to
dozens
n
tonight
right
we
only
had
obvious
piece
and
sure
you
could
do
it
with
with
vb
net,
but
the
majority
did
she
sharp
right.
So
that
was
just
a
jersey
right
and
and
back
then
there
was
the
only
approach.
Then
we
go
sandbox
which
in
a
way
was
similar
to
the
obvious
p,
but
not
quite
then
we
go
eddins,
but
that
was
still.
If
you
will,
it
was
still
see
shark
net
and
it
was
the
ramp
up.
A
Year
in
so
that
is
yet
when
I
can
sorry
for
jumping
on
that
one,
but
but
as
an
example,
on
the
other
hand,
one
of
the
considerations
in
a
farm
solution
has
always
been
the
fact
that
in
sharepoint,
when
you
need
to
do
a
customization,
you
have
multiple
ways
of
doing
now
back
in
2008
timeframe.
Yes,
the
language
was
typically
the
same.
C-Sharp
know
you
can
actually
develop.
A
She
sharp
in
multiple
different
ways,
and
you
can
do
visual
web
board,
so
you
can
do
in
line
HTML
within
a
web
part
or
you
can
do
a
user
custom
actions
or
you
can
do
find
definitions
or
you
can
do
what
template.
So
all
of
that
kind
of
the
essentially
how
stuff
should
have
been
implemented
should
have
been
actually
in
the
comments
plan
as
well
right
right.
B
What
else
much
I'd
say
yeah?
So
what
you
said
is
this
is
true,
but
the
way
I
I
see
it
is
that
it
was
more
related
to.
It
was
still
sheesh.
My
point
right,
so
there
was
a
number
of
options
that
you
had
now
with
with
that
with
FB
FX.
I
would
say
that
there's
probably
framework
release
or
library
release
every
day
and
there
will
be
always
a
new
version,
a
new
library
that
does
something
better
than
something
else.
Yeah
right
with
that
I
think
is.
B
It
will
help
you
a
lot
at
the
end
of
the
day,
if
you
juice
just
pick
one
and
stick
using
that
as
opposite
to
try
to
using
the
latest
one,
because
there
will
be
a
new
library
every
day,
every
week,
yeah
and
at
the
end
of
the
day
you
want
to
be
efficient.
You
want
to
whatever
you
build.
You
want
to
make
that
in
a
way
that
it's
cost-effective
for
everyone
turn
right
and
chasing
and
rebuilding
the
build
process,
build
change
pollution
itself
as
well.
It's
not
going
to
help
you
with
that.
B
So
with
that,
I
would
say
that
you
should
try
to
rationalize
the
libraries
that
you
use
and
just
pick
one
and
stick
to
that
and
not
switch
every
month
or
every
three
months
from
one
to
another.
I
mean
sure.
Is
it's
good
to
try
and
to
see
what
is
out
there,
but
at
the
end
of
a
pic
1
and
use
that
as
much
as
you
can
really
choose.
A
A
Yeah
good
example:
it's
angular,
so
angular
4.0
is
going
to
be
released
relatively
soon
so
which
has
to
release
2.0
what's
happening,
so
the
speed
is
too
fast
and
people
can't
keep
up,
and
it's
so
always
good.
Let's
say
the
dynamic
with
web
staff
development
in
the
smaller.
Let's
say,
companies
must
be
completely
different
than
the
rules
and
setup
which
we
need
to
do
for
enterprise
companies
or
a
bigger
company,
internal
yeah
cute
so,
and
one
of
the
things
so
just
such
a
reference.
A
Some
of
the
resources
which
are
available
from
the
data
burst
at
home,
/
SharePoint,
with
this
D
landing
page
for
shipment
development
and
I
one
feature.
So
we
do
have
a
separate
article
on
the
interface
guidance
kind
of
a
raising
considerations.
What
people
should
be
thinking
and
also
on
a
team
development.
We
didn't
actually
deep
time
in
this
session
on
Team
Development
considerations
too
much.
But
there's
that
article
is
touching
things
like
hey.
How
do
we
do
internal
NPM
or
package
structure
or
library,
sharing
structures
and
other
considerations
like
source
code?