SKILupDay

CD roots exist in Agile Principle i found two principle close to it. i will say its one particular engineering practice

Not really, I think it has evolved more than any other practise under the DevOps movement. It has brought in the most technological aspects of DevOps practices.

CD is the 1st of the 12 agile values - in this respect it's about process. In my mind, the world of DevOps has commandeered it in the context of the CD pipeline or DevOps toolchain

CD is miss-understood. I see "CD" meaning is ambiguous. Continuous Delivery, Continuous Deployment and Continuous Delivery Pipelines often are referred to as "CD" even though they are related bu different.

Or maybe CD is not an extension from Agile? Maybe a reaction as well same with what we heard from DOES20.

DevOps is not a market, but a tool-centric philosophy that supports a Continuous Delivery value chain.

@davefarley77 once said to me it shouldn't be called DevOps, it should be called CD and I'm inclined to agree, but I think it's too late; it's already too tightly associated with automation

totally

Not aligning to organizational vision

Just faster version of everything :-) Too many tools

Not thinking about culture! You won't achieve anything if people don't understand why you want to give your customers more and better value and that the behaviours and ways of working need to evolve accordingly; high trust, experimentation, failure and learning

Lack of Vision, Attitude, Passion, Training, Visualization of benefits

automating bad practices , process

Not having a clear wok flow of the value stream

Some key pitfalls I see ALL the time with organizations working towards continuous delivery is too much focus on tools and not enough on leadership, culture and processes. Also testing is too often under-invested in transformation bugdets.

lack of business IT alignment and difference in stakeholders interest

@BealHelen nailed it!

@bajpaigarima1 you align to my thoughts .

Without empathy, psychological safety and adaptability top-down the organization and support for learning and unlearning, it can be tough.

@mhexcalibur does leadership & culture goes hand in hand ? #devops

@TinyCyber at what stage do you think organizational vision marriage with #CD. Isn't it at the #IT level that they plan for automation as business generally does not demands it. #devops

(edited)

I think it is throughout. #IT needs to demonstrate increased value so that business does demand it. Vision should be basic, shared goals also helps improve satisfaction rates

Good Attitude, Patience, Passion and Ability to create Pipelines

It needs to be broken down into process, functional, technical and soft skills.

Skills most relevant for Continuous Delivery include a solid understanding of DevOps foundations, and continuous delivery architectures such as the courses offered by the DevOps Institute www.devopsinstitute.com

Then under each segment, there are different set of skillset required !!

ITSM,Agile (SCRUM + KANBAN) must, DevOps must, CI, Security and Cloud service knowledge

Experimentation , creating data stories for decision making & DevOps practices with ideation

Flexibility, Cloud platform and cloud environment skills, infrastructure maintenance, analytical skills, tools and its integration, DevOps pipeline operation, test automation skills, environment orchestration, release management skills, API

@bajpaigarima1 Totally experimentation mindset - practicing hypothesis driven design and development

Agree @humanofdevops, and I certainly would like focus on security and monitoring as well!

A culture of countinuos learning

Find your own solutions, create your own transformation based on your own Business goals aligned with any or multiple such solutions !!

We use Agile practices + Design thinking + DevOps practices in most of cases , no one thing can do it alone

I'm a big fan of the Professional Scrum and Kanban certification (I have it!) - these frameworks enable teams to manage the flow of work in order to achieve a state of continuous delivery of value to their customers (number 1 of the 12 agile principles)

No one-size-fits-all approach. Depends on the size and complexity of the project. Scrum and kanban are both in umbrella of agile and they can complement each other depending on how you want to take advantage of it. ;)

@BealHelen complete agree I am also another big fan of PSK :)

The important part of this question is that CD is added to every practice. We need CD in any framework to be successful.

@Jameswasson1 CD makes scrum more alive :)

@HumanOfDevOps Couldn't agree more!

CD is my Vanilla and Methodologies are toppings

Does some of you use design thinking techniques ?

Yes. Need to be open between philosophy and tools.

@Jameswasson1 Cool stuff! I am in

vendors :P

Its everyone success in organization so everyone in org. is responsible. A valuable business requirement helps to create valuable software. And when software gets right feedback at right time, its going to generate value for organization.

Treat Cd pipeline as product and Cd product owner is responsible for incremental features- align it with business goals

COE should own it for Continuous Improvement of the Pipeline as per my view!

Is there a Continuous delivery main stakeholder?

@mjenkins70718 interesting, can you elaborate

@bajpaigarima1 Second that! Please elaborate @mjenkins70718

(edited)

@bajpaigarima1 @alalit Usually Improvement stops when Pipeline is stable. Everyone is Happy with the current state where even quality teams are fine with Pipelines as it exists. If COE team is involved then they look for current trends and improvement based on technology and tool

there are new roles emerging like the Continuous Delivery engineer / manager which may own. however I think the #productowner are also coming up for product driven organization. Last but not the least, segregate ownership for each pipeline. Can be many but avoid #devops

we define north star for cd pipeline product , create leader action plan for the product, define taxonomy of the product & create a charter to set accountability

(edited)

Shared ownership, everyone must be responsible for contributing, through feedback, from dev to prod, developing team owns their code, their development. Ops owns shared environments, stable delivery

@mjenkins70718 If improvement stops, you are done. Doesn't have to be big improvements, small steps forward