►
Description
Melissa Ushakov walks through how to use groups and projects to model your organization.
Blog: https://about.gitlab.com/blog/2020/11/11/gitlab-for-agile-portfolio-planning-project-management/
Groups: https://docs.gitlab.com/ee/user/group/subgroups/
Projects: https://docs.gitlab.com/ee/user/project/
A
So
to
start
off,
let's
go
over
some
quick
definitions,
so
a
team
is
a
set
of
individuals
that
are
working
together
to
deliver
stories
or
bugs
these
teams
are
typically
working
in
two
week
sprints
or
maybe
one
month,
long
iterations
from
there
you
have
teams
of
teams
or
programs
which
are
working
together
to
deliver
features.
Typically,
these
are
done
on
a
quarterly
basis
and
there's
interconnectedness
between
these
teams
and
they're
packaged
up
into
a
program
from
there.
A
We
have
teams
of
teams
of
teams
or
portfolios
which
are
groups
of
basically,
and
sometimes
it's
called
a
business
unit.
Sometimes
it's
called
a
portfolio,
but
it's
typically
how
funding
is
done
at
an
organizational
level,
so
these
concepts
are
not
new
by
any
means.
Like
I
mentioned,
there
are
the
constructs
that
are
talked
about
and
some
of
the
common
scale
digital
frameworks,
and
this
is
something
that
can
be
easily
modeled
in
gitlab,
using
groups
and
projects.
A
So
in
gitlab's
projects
are
individual
containers
in
which
you
can
have
issues,
and
groups
are
collections
of
projects
in
which
you
can
create
epics
and
also
have
aggregation
of
projects.
So
you
can
already
see
how
these
concepts
are
similar
to
teams
and
the
aggregations
of
teams,
and
now
I'm
going
to
show
you
have
used
these
two
to
model
out
an
organization
in
gitlab.
A
A
In
this
particular
case,
I've
done
a
hierarchy
that
is
three
level
deep,
but
there's
a
lot
more
flexibility
with
that,
depending
on
how
complex
your
organization
is
something
that
is
very
interesting
about
doing.
This
is
that,
if
you
see
here
by
having
all
of
my
entire
organization
under
the
same
group,
I'm
able
to
get
a
high
level
view
into
every
epic
and
every
issue
under
this
hierarchy,
so
that
is
extremely
useful
to
have
visibility
into
the
entire
organization.
A
If
you
notice,
when
I
go
into
the
banking
organization,
the
count
of
my
epics
is
filtered
down
only
to
the
ones
that
relate
to
banking,
so
in
the
entire
organization
there's
seven
and
in
banking
there's
only
five
another
advantage
of
organizing
your
hierarchy.
This
way
is
that
you
can
have
distinct
members
of
each
of
these
projects
and
groups.
A
So
if
there's
somebody
who
is
overseeing
the
entire
company,
so
at
c
level
they
would
be
members
directly
of
melissa
inc.
If
there's
somebody
who
is
an
organization
leader,
so
like
a
vp
level,
there
will
be
members
of
banking
and
they
could
see
everything
within
it
and
if
there's
individual
contributors,
let's
say
a
product
manager
of
the
borrower
group,
they
only
can
be
added
to
this
specific
group,
so
they
can
only
see
issues
pertaining
to
their
group.