►
Description
CI/CD as a Product - Garima Bajpai, Capital Carbon Consulting
During this talk, I will reflect on my thoughts on decoding the importance of next-generation CI/CD pipeline. Without dwelling too much on the basics, the key priority for them will influence the next-generation value ecosystem for CICD features. Some of the key factors would be: CxOs are suggesting to consider business need to be producing features which are more than just a faster, more efficient version of everything, making sure next-generation data capabilities are part of the ecosystem and bridging the multi-cloud and on-premise cloud stack takes priority to integrate edge, cloud and compute capabilities.
These factors will craft the next-generation features for the CICD pipeline. In order to align the features with the value ecosystem, here are some suggestions:
Treat CICD as a product group
The product group must have incremental features aligned with the key CxO priorities
Embed unified value tracking into the CICD pipeline to steer the right investments
Invest in traceability, audit and vulnerability management
When you start treating CICD as a product group, it is essential to define the “north star” for the product group, create a leader’s action plan, map the people of the product group and eventually accelerate the new charter.”
A
A
My
topic
of
today
would
be
ci
cd
as
a
product
and
before
going
into
more
detail
about
the
topic,
I
would
like
to
start
my
talk
with
a
mandatory
slide,
who
I
am
I'm
guri
mabajwai
based
out
of
order,
canada,
industry,
speaker
for
digital
train,
ai
ops
and
devops
women
in
communication
mentor
for
wctfcd
chapter
in
canada,
co-founder
of
devops
community
of
practice,
co-organizer
for
devops
summit,
canada,
which
happens
november
and
2nd
and
3rd.
I
would
like
to
invite
you
all
to
join
us
ambassador
with
devops
institute
and
ambassador
with
continuous
delivery
foundation.
A
A
It's
an
experience
based
movement
and
the
the
movement
is
so
powerful,
just
because
it's
based
on
experimentation
and
focus
on
flow
and
feedback.
So
having
had
a
look
at
what
devops
means
in
the
context
of
my
talk,
I
would
like
to
reflect.
Ci
cd
and
somehow
devops
and
ci
cd
have
been
interchangeably
used
in
various
contexts,
so
it's
extremely
important
to
establish
a
common
vocabulary
for
ci
cd
and
from
my
perspective
I
would
like
to
s.
Without
going
into
more
technical
details
around
ci
cd.
A
I
would
like
to
s
take
a
bird's
eye
view
on
ci
cd
as
subset
of
software
practices,
which
help
improve
flow
feedback
and
experimentation,
and
there
are
various
practices
through
which
ci
cd
enables
us
to
do
that.
Continuous
integration,
continuous
employment
context,
delivery
and
practice
and
techniques
like
automation,
play
a
vital,
important
role
when
it
comes
to
ai
and
why
ai
is
important
in
this
context,
I'll
explain
to
you,
ai,
to
my
understanding,
enhances
predictive
and
adaptive
decision
making.
A
I
can
clearly
see
that
we
are
ready
to
welcome
the
ai
to
the
devops
family,
so,
together
these
three
things
would
redefine
the
future
of
cicd,
as
well
as,
to
a
certain
extent
how
we
will
work
together
with
you
know,
devops
as
a
progressive
movement.
Ci
cd
has
a
pro
a
potential
capability
and
ai
to
enhance
the
capabilities
which
we
will
have
to
develop
and
evolve
software
and
digital
solutions.
So,
let's
quickly
plunge
into
the
very
first
thing
before
even
starting
to
talk
about
a
future
of
ci
cd
pipeline.
A
We
also
have
to
understand
that
we
are
into
an
era
where
we
are
building
a
social
ecosystem
of
a
skill
set.
We
are
actually
establishing
a
network
of
practitioners
for
evolving
these
digital
solutions.
Right
and
skill
building
is
a
collective
journey
around.
You
know
how
infrastructure,
how
application
and
how
data
would
be
treated.
A
Address
this
need
which
is
coming
to
us.
We
need
to
basically
think
different
ways.
Different
mechanisms
to
deal
with
it
decentralization,
open
governance,
socially
protective
policies
and
creating
like
virtual
labs,
would
be
some
of
these
key
considerations
which
we
will
see,
and
through
these
enablers,
we
will
be
able
to
establish
new
incremental
features
for
our
ci
cd
practices,
and
I
will
actually
move
ahead
in
this
journey.
A
To
give
you
a
view
of
how
I
see
you
know,
cicd
will
evolve
incrementally,
and
you
know
what
I
see
from
where
I
am
today,
and
I
built
this
dialogue
with
various
communities,
open
communities
and
I
believe
that
ex
experimenting
with
new
features
in
the
safe
zone
will
become
a
norm.
So
these
the
product,
companies,
the
digital
product
companies,
will
build
new
features
through
an
ecosystem
of
stakeholders,
and
these
new
experiments
will
take
place
in
joint
setting
where
we
we
are
involving
stakeholders,
different
stakeholders.
A
We
will
use
new
data
sources
and
new
technological
advancements
to
build
our
products.
We
will
also
enhance
our
understanding
about
the
existing
regulations
and
how
we
design
new
future
oriented
security
and
privacy
frameworks,
and
this
will
impact
how
we
build
our
incremental
features
in
our
ci
cd
pipeline
and,
lastly,
implementation
and
expansion
of
e-privacy
framework
data-driven
policies.
A
All
these
things
will
also
influence.
You
know
crafting
the
future
of
ci
cd.
Now
with
such
a
complex
mesh
of
driving
factors.
How
do
we
believe
that
we
can
take
the
next
steps?
You
know,
how
do
we
envision
our
next
generation
cncd
pipeline?
So
it's
a
difficult
question
so
before
actually
we
discussed
about,
you
know
why
we
need
next
generation
cncd
practices.
What
are
the
key
drivers,
but
now
we
are
into
a
discussion
where
you
know
we
need
to
understand
how
we
start
up
this
complex
journey.
A
So
there
are
various
ways
we
can
do
it,
but
what
I
am
getting
here
for
is
what,
if
the
clcd
pipeline
was
a
product,
so
when
you
start
deleting
your
ci
cd
pipeline
as
a
product,
basically
a
group
of
products,
so
you
need
to
have
some
incremental
features.
You
need
to
treat
that
ci
cd
pipeline
as
a
portfolio
right.
So
and
you
have
to
do
all
the
due
diligence
to
put
up
incremental
features
to
invent
value
tracking
and
also
outline
your
investment
strategy.
A
A
They
started
their
agile
journey
and
they
said
business
adopted
agile.
What
half
of
the
projects
are
still
failing?
What
they
need
actually
is
not
more
more
than
just
a
faster
version
of
everything.
So
how
do
you
actually
introduce
value
towards
the
business
stakeholders
is
the
key
you?
How
do
you
actually
use
your
next
generation
data
capabilities
to
enhance
customer
experience,
how
to
bring
return
of
investment
for
each
and
every
mvp
faster?
A
Also,
there
is
a
lot
of
challenge
around.
You
know
how,
from
a
technology
perspective,
the
landscape
is
changing,
so
we
need
to
ensure
that
we
have
a
capability
which
is
not
micro
focused,
but
you
know
have
a
longer
term
strategy
in
terms
of
building
a
bridging
multi-cloud
gap.
You,
you
should
have
a
infrastructure
which
is
capable
for
balancing
your
cloud
compute
as
well
as
edge
components
of
your
delivery
right.
A
These
kind
of
you
know
concerns
and
gaps
which,
from
an
executive
point
of
view,
are
still
existing,
and
if
you
have
this
this
vision,
you
can
actually
move
forward
from
from
where
you
are
today
in
the
ci
cd
context
and
treat
ci
cd
as
a
portfolio,
a
product
group,
and
when
you
start
looking
at
a
product
group
you
what
you
need
to
define
is
you
need
to
define
your
north
star?
You
need
to
define
a
wanted
position
which
has
business
outcomes
associated
with
it.
A
You
also
have
to
consider
the
people
of
the
product
so
how
your
product
would
be
taken
up
from
a
people's
perspective
or
what
kind
of
considerations
you
would
have
in
that
dimension.
And,
lastly,
how
would
you
accelerate
the
new
charter
for
your
ci
cd
pipeline
as
a
portfolio?
What
are
the
key
factors?
What
are
the
drivers?
You
will
consider
and
it's
it's
a
difficult
question
to
answer.
A
So
what
we
had
done
is
that
we
interacted
with
a
lot
of
entrepreneurs
and
startup
owners,
and
you
know,
to
a
certain
extent,
product
owners
in
large
enterprises
and
we
kind
of
try
to
connect
the
dots
with
the
the
transition,
the
change
which
is
happening
as
we
speak.
You
know
the
evolving
software
practices,
which
you
know
devops
is
one
of
the
vehicles
to
towards
it,
and
cicd,
as
I
mentioned,
becomes
a
change
agent
in
that
context.
A
But
you
know
what
we
have
seen
is
that,
although
we
were
able
to
close
the
gap
between
development
and
operations
through
the
dialogue
around
devops-
and
you
know,
how
would
we
cut
down
or
bridge
the
gap
between
these
two
functional
cycles,
which
were
created
from
operations
and
development
perspective?
We
still
lack,
you
know
a
perspective
around.
How
do
we
engage
with
business
owners?
How
do
we
engage
with
stakeholders?
A
We
found
out
that
there
were
difficulties,
you
know,
steering
it
from
a
design
inception
perspective
and
they
had
like
gaps
to
identify
their
product
values.
We
also
saw
that
in
the
development
and
deployment
phases,
although
they
had
you
know
robust
infrastructure
and
robust
capability
around
you
know
devops.
A
Basically,
they
had
a
advanced
pipeline
ci
cd
pipeline
to
ensure
integrity
in
the
system.
Even
though
that
was
there,
the
consistency
in
the
product
values
was
difficult
to
achieve
because
of
different
views,
and
it
was
difficult
to
build
consensus
around
consistent
product
values
when
it
comes
to
operations,
even
if
they
were
releasing
mvps.
A
There
was
a
challenge
to
tune
the
product
values
because
there
was
either
not
enough
data
or
there
was
data,
but
there
was
no
capacity
or
capability
to
assess
to
make
data
stories
which
can
help
them
in
decision
making.
So
these
are
like
some
of
the
strategic
gaps
when
you
see
from
an
end
to
end
perspective
and
what
why
I'm
actually
bringing
this
view
is
because
we
need
to
kind
of
ensure
that
when
we
have
the
next
generation
incremental
features
for
ci
cd,
we
ensure
that
we
fill
these
strategy
gaps.
A
We
do
not
only
consider
the
second
question
in
this
picture,
which
is
how
fast
can
we
deliver?
We
also
have
to
consider
the
first
question.
Is
it
a
good
idea,
so
we
should
have
some
capabilities
from
a
ci
cd
perspective.
Who
can
help
us
with
this
question
and
also
the
third
question,
which
becomes
extremely
important.
A
Was
it
a
really
good
idea
right
in
the
beginning,
because
if
you
don't
have
a
value
feedback
loop,
which
can
actually
enable
your
decision
making
and
steer
the
business
owners
to
collaborate
with
development
and
operations
teams,
then
the
whole
process
itself
has
not.
You
know
got
to
a
point
where
you
see
the
end
picture
the
bigger
picture,
so
this
I
I
believe,
would
create
more
opportunities
to
think
through
and
build
incremental
features.
The
future
of
ci
cd
lies
somewhere
in
this
picture
itself.
A
So,
making
this
discussion
more
tangible,
I'll
I'll
discuss
about
what
kind
of
incremental
features
I
see
when
I
consider
ci
cd
pipeline
as
a
product
portfolio,
so
there
are
four
things
which
I
want
to
outline
today.
The
first
aspect
which
I
would
like
to
outline
is
triggering
the
pipeline
for
ml
projects
for
sure
from
today
to
from
two
to
five
years
down
the
line,
a
lot
of
products,
maybe
eighty
percent
of
the
products
would
ensure
they
have
ai
native
features
into
their
product
portfolio.
They
have
some
kind
of
integration
into.
A
You
know
how
they
enable
ai
capabilities
into
the
features
and
products
they
are
developing.
So
it's
extremely
important
that
the
ci
cd
pipeline
supports
those
kind
of
features
and
triggering
the
pipeline
for
ml
projects
is
extremely
important.
The
second
part
of
the
building
of
an
incremental
feature
is
data
versioning.
So
when
you
think
about
a
lot
of
ai
native
aspects
will
come
into
products.
That
means
you
will
have
a
lot
of
data
into
the
system.
You
need
to
cleanse
that
data.
You
need
to
have
a
data
versioning
system.
A
A
The
third
aspect
of
these
incremental
features
would
be
traceability,
auditable
policy
as
code
and
think
about,
like
from
an
ai
perspective,
how
you
would
have
security
inbuilt
in
these
air
products,
so
that
will
another
be
another
area
where
you
know
you
will
see
a
lot
of
incremental
features
if
for
ci,
cd
and
last
but
not
least,
embed
value
stream,
mapping
and
I'll
elaborate.
This
with
some
examples
in
the
upcoming
slides
so
taking
that
discussion
further.
The
first
part
which
I
actually
talked
about
was
incremental
features
to
support
ai.
A
You
know
there
will
be
specific
details
which
will
be
required,
specific
features
which
will
be
have
to
be
integrated,
and
one
of
those
would
be
how
to
enable
ai
security
for
ai
based
products
or
aid
products.
The
third
aspect
is
data
engineering
practices
to
prepare
the
data
and,
lastly,
how
to
develop,
train
test,
deploy,
manage
and
track
machine
learning
models.
So
how
do
we?
How
can
we
help
in
that
process
and
how
your
ci
cd
pipeline
can
be
one
of
the
enablers?
A
A
more
value
driven
product
pricing
and
how?
How
do
we
maximize
return
of
investment
for
every
mvp,
which
we
are
developing
right?
How
we
actually
deliver
just
sufficient
amount
of
value?
You
know,
because
too
much
value
is
not
good
news.
It
gets
too
complicated
just
too
soon,
so
you
need
to
have
the
right
investments
in
the
right
direction.
All
this,
like
you
know
they
enable
us
to
get
introduced
to
the
business
stakeholders
to
bridge
the
gap
between
the
strategy
organization.
A
Lastly,
developing
a
continuous
product
canvas,
basically
with
a
set
of
features
which
you
have
the
choice
of
you
know
set
of
features
you
can
actually
develop.
You
can
deploy,
you
can
release,
which
are
the
most
valuable,
most
essential
features.
How
do
you
quantify
a
value?
Driven
approach
towards
your
release?
A
I
would
also
like
to
highlight
that
we
are
looking
are
heading
towards
integrated
ecosystem,
which
can
which
should
support
new
ways
to
secure
our
digital
products,
and
we
need
to
build
trust
to
go
digitally
we'll
have
to
enable
reliable
global
flows
of
information
data
application
technology
and
also
how
we
trust
fully
govern
our
machine
human
integration
models.
So
there
is
a
lot
of
a
lot
of
potential
to
build
up
new
features
around
security
in
your
ci
cd
pipeline.
You
know
improving
your
hybrid
cloud.
Security
posture
can
be.
A
I
also
kind
of
want
to
address
this
challenge
from
a
more
tangible
product
feature
perspectives.
The
product
features
getting
protected
by
the
use
of
security
functionality,
so
basically
ensuring
traceability,
audit,
vulnerability,
management
for
open
source
components,
product
feedback
loops
should
be
constantly
reducing
liability.
A
So
you
need
to
ensure
that
whatever
feedback
loops,
you
are
creating.
How
do
you
integrate
this
with?
You
know
a
view
on
how
they
reduce
liability
enabling
personalized
security
and
privacy
based
you
know,
features
based
on
your
e-privacy
framework
and
leveraging
security
practices
to
get
useful
data.
That
brings
us
closer
to
the
demand
of
the
customer
right.
So
all
these
are
like
tangible
things
which
we
can
do
it
in
in
the
security
area
and
there's
a
lot
of
potential
in
that
dimension.
A
Lastly,
I
would
like
to
consider
value
streaming
and
improving.
The
purposefulness
of
deployment
of
features
is
the
extremely
important
aspect
of
everything
what
we
do
through
ci
cd.
So
if
we
actually
are
able
to
close
the
gap
between
what
value
are,
we
are
delivering
and
not
only
reflecting
that
how
much
faster
we
are,
we
would
have
a
better
possibility
of
engaging
our
investors
and
engaging
our
leadership
teams
onto
a
product
portfolio
discussion
around
ci
cd.
A
We
also
need
to
ensure
that
we
set
the
right
strategy
for
customer
reliability,
engineering,
which
means
how
to
build
enough
safety
margin
just
enough
safety
margin
so
that
we
have
room,
for
you
know,
experimentation
innovation,
you
know,
building
new
features,
also
collection
of
data
and
its
governance.
And,
lastly,
how
do
we
collaborate
with
virtual
labs?
A
How
do
we
integrate
into
a
larger
ecosystem,
because
a
lot
of
these
features
which
we
are
building
for
our
digital
products
will
be,
will
be
developed
and
delivered
through,
like
virtual
collaboration
with
stakeholders,
and
can
be
what
your
labs
can
be?
One
of
one
of
the
ecosystem
building.
You
know
concepts.
A
A
A
The
second
aspect
would
be
you
know:
how
do
we
ensure
that
we
eliminate
future
toil?
How
do
we
ingest
the
right
set
of
data?
How
do
you
use
the
right
models?
How
do
you
support
decision
making?
So
these
things
actually
is
second
aspect
which
we
will
be
seeing
more
and
more
incremental
features
around,
and
your
ci
cd
pipeline
might
be
integrated
with
some
of
these
features.
A
So
this
perspective,
basically,
we
had
gained
through
working
through
a
set
of
entrepreneurs,
and
a
lot
of
you
know
product
owners
through
you
know
our
discussions
around
various
industry
segments.
What
we
have
done
so
far
is
that
we
we
have
delivered
a
lot
of
workshop
with
these
entrepreneurs,
helping
them
with
their
product
ideas,
and
that
is
where
our
understanding
around
ci
cicd
pipeline
and
the
future
incremental
features
which
will
be
required
for
this
pipeline
has
got
matured.
A
So
that
is
all
what
I
had
for
today's
talk,
and
I
would
like
to
thank
you
for
giving
me
an
opportunity
here
to
discuss
my
perspective
and
I
would
like
you
would
invite
you
to
the
devops
summit,
canada
november.
Second
and
third,
if
you
want
to
contact
our
team,
our
contact
details
are
at
the
bottom.