Skip to main content

ITIL 4 – Create, Deliver and Support (CDS)

Create, Deliver and Support (CDS) is one of many content areas of focus within the ITIL 4 guidance. It is included in the ITIL 4 schema for ITIL Specialist certification and is one of the many modules contained in the Managing Professional Transition class


Create, Deliver, and Support (Training and Certification) is an advanced course that requires the ITIL 4 Foundation knowledge and certification. It takes a deeper dive into core areas of holistic thinking and application by understanding clearly; the Service Value System, Service Value Chain and the Anatomy of a Value Stream.

To create, deliver and support services, specialists need a broad set of competencies to meet the dynamic need and demand for digital services.


Proficiencies gained will help professionals optimize end to end value and must expand beyond tech to include such things as: 
  • Radical soft skills that take communication, leadership, and innovation to the next level
  • Ability to provide opportunities for continued professional development
  • Ability to develop recruiting and onboarding skills for cross-functional teams
  • Building job descriptions that include both technical and non-technical skills
  • Enable and encourage staff to investigate new ideas, ways of thinking and new ways of working
  • Recognize non-IT experience (e.g., team management, procurement) and provide efficient workforce planning
Practitioners must know how to ensure the integration of activities for business value streams and practices that support consumer needs for services. To do so, the service management professional must be proficient in their approach. More importantly, they must understand how to think holistically, work incrementally and to deliver value FAST!

To learn more, or to register for the Create Deliver and Support certification course, please visit https://www.itsmacademy.com/CDS

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…