►
Description
A UX Showcase to show the plan for managing, planning and executing releases across repos easy with GitLab
A
Hi
there,
my
name
is
haigha
nvidia
I'm,
a
senior
product
designer
it
lab
working
with
a
release
management
group
for
today's
to
actual
case
I'm
excited
to
share
with
you
our
vision
and
networks
for
the
CIT
Group
dashboard
and
the
group
releases
capabilities.
We
want
to
make
managing
planning
and
executing
Lisa
price
ripples
easy.
A
The
release
management
team
is
responsible
for
the
categories
of
release,
evidence,
release,
orchestration,
Super's
management
and
pages.
Today,
I'm
talking
to
you
about
the
release
orchestration
category,
which
is
the
ability
to
coordinate
complex
releases,
particularly
across
projects,
in
an
efficient
way
that
leverage
of
s-code
behaviors
as
much
as
possible.
This
project
has
a
couple
of
goals
based
on
problem
validation.
We've
learned
that
our
customers
need
the
ability
to
support
action
on
releases
and
planning
at
the
group
level,
so
across
multiple
projects
and
for
the
users.
A
A
It's
not
a
new
topic
just
to
give
you
a
little
bit
of
background
around
two
years
ago,
our
research
team
conducted
user
interviews
on
the
dashboard
workflows
with
it
lab
one
of
the
insight
was
around
a
director
level
management
dashboard
that
would
allow
customers
to
see
how
well
their
teams
are
performing
the
releases
and
they
could
provide
them
a
top
level
overview
of
all
project
statuses.
So
the
users
who
requested
this
feature
works
typically
team
leads
and
their
manager
had
roles
at
the
director
level
as
forward
to
February
this
year.
A
We
interview
a
total
of
nine
users
across
four
personas,
those
who
are
release
managers,
software,
developer
team
lead
and
one
security
personam.
During
the
interviews,
we
learned
that
the
role
most
likely
to
feel
the
pain
of
working
across
dependent
projects
is
Sasha
the
software
developer
and
that
the
software
engineers
would
be
very
interested
in
a
snapshot
view
across
all
the
projects
and
meeples.
The
other
persona
that
is
most
likely
to
get
fired
for
mishaps,
related
to
error
sourced
in
the
other
project
is
Rachel.
A
The
release
manager,
the
heart
of
our
personas
problem,
is
that
Sasha
enriched
you'll
want
to
collaborate,
move
fast
and
execute
the
work
with
as
little
interruption
as
possible
without
a
context
across
ripples.
That
rate
your
needs,
for
example,
there
could
be
a
premature
releases
errors
in
the
repo
dead
surface,
another
and
untimely
appointments
to
production,
so
the
pain.
This
is
for
organisations
that
have
hundreds
of
projects
and
thousands
of
deployments.
A
Today,
each
release
item
works
in
isolation,
release,
managers
and
directors
software
engineers
they
have
to
go
to
each
project
to
keep
track
of
the
releases,
the
environments,
deployments,
pipelines,
etc.
We
spoke
to
customers
and
heard
that
they
are
more
likely
to
want
to
combine
repos
for
highly
dependent
code
and
if
they
could
easily
see
that
changes
from
movie
people
did
not
impact
the
product
in
a
different
but
connect
the
ripples
within
a
group.
They
would
want
to
be
able
to
support
the
work
flows
better
wicket
left
today.
A
If
you
use
manual
tests
in
isolation
or
tools
like
ZB
labs,
deploy,
review
apps
can
help
review
changes,
but
only
after
the
changes
spread
across
most
o
rifles.
Our
immersion
to
the
same
environment
and
customers
would
often
migrate
to
mono
repo
to
avoid
spending
time
validating
their
releases
across
projects
so
having
the
ability
not
only
orchestrate
but
to
coordinate
depending
labels
will
make
our
users
lives
easier.
A
We're
going
to
be
able
to
with
CB
Labs
releases
elegance
of
crossing
views,
administration
and
deployments,
as
well
as
actionable
metrics
for
how
things
are
performing
our
solution
to
that
overwhelming
problem
is
providing
visibility
to
the
users
on
releases
at
the
group
level
and
then
linking
them
to
the
page
of
each
project
release.
We
believe
that
this
will
mitigate
our
users
risk
manually,
checking
each
project
release
our
team
consider
technicalities
of
releases
at
a
group
level,
for
example.
A
Instead
of
bringing
a
concept
of
tags
to
a
group
which
would
introduce
a
check
point
in
your
source
code
history
and
creates
a
problem,
cysts
groups
don't
really
have
a
code
base.
We
want
to
explore
group
releases
as
some
sort
of
supportive
version,
our
first
job
to
be
done.
It's
allowing
users
to
create
a
new
group
release
from
an
existing
release.
Projects.
Users
would
then
be
able
to
access
some
sort
of
at
a
glance
view
of
all
projects
that
were
associated
to
this
new
release
or
version
item.
A
This
is
important
because
all
products
that
are
being
released
or
announced
to
the
market
at
the
same
time
are
now
in
a
single
bucket.
If
you
also
have
milestones
associated
to
it,
once
we
introduce
the
concept
of
group
milestones,
you
can
see
the
plan
versus
deliver
stats
across
all
the
projects.
The
next
management
feature
that
will
help
widen
the
webbing
in
wine
experience
for
all
worlds
in
geek
lab.
Is
this
the
ICD
group
dashboard?
A
This
s1
will
give
people
the
power
to
look
into
their
teams
across
all
projects
and
see
the
keys
asymmetric,
like
the
percentage
of
projects
with
releases
in
the
group.
Last
five
lines
in
the
group,
the
ratio
of
the
last
35
clients
in
the
group
and
so
on.
The
initial
prototyping
raised
a
lot
of
questions
around
dashboards,
Woodgate
lab.
A
We
know
that
today,
group
level
metrics
are
displayed
in
different
ways,
so
you
can
see
here
that
the
analytics
insights
have
a
different
user
interface
from
Vella
stream
analytics
and
also
the
security
dashboard,
and
also
the
environment
and
operation.
Dashboard
part
of
our
analysis
was
to
identify
the
goals
of
each
dashboard
and
compare
a
little
bit
how
these
goals
match
the
CICE
dashboards
goals.
They
start
to
become
a
very
complex
word
and
we
love
boring
solutions.
We
have
decided
that
our
low-hanging
fruit
was
to
identify
which
we
climb.
A
Ui
components,
are
production
ready
and
can
be
used
to
create
the
MVC
for
the
vegetable
with
listed,
which
components
can
currently
be
reused
and
which
ones
need
some
work
in
the
pyjamas
project.
Our
next
design
step
is
validating
in
mocks
with
users.
Engineer
is
research
and
how
it
can
aggregate
projects
at
the
group
level,
because
one
of
our
goals
is
to
not
really
create
any
additional
UI
components
and
UI
changes.
We
will
try
to
reuse
as
much
component
as
possible
and
it's
actually
why
improvements
on
the
fly.
A
The
next
steps
of
what
we
want
to
do
is
to
validate
these
prototypes
with
customers.
We
have
some
interview
schedules,
understandably,
why
we
propose
enable
large
organizations
to
manage
plan
and
execute
releases
across
vehicles
easily
after
the
solution
validation,
we
will
review
the
design
and
technical
specs
and
rip
the
issues
down
for
planing
schedule.
Of
course
we
will
be
conversations
along
dashboard
inside
city,
so
that
will
make
sure
that
the
user
experience
at
CrossFit
lab
it's
aligned.