DevOps and the North Pole

T’was a month before Christmas on the pipeline, not a heart was beating not even mine.

For the product owner there is work to be “DONE”, so into the “Sprint Log” the work has begun! 

On Dasher! On Prancer (Development Deer) - QA and Security, they are all here.

Red hats worn by all and only one “White”; The teams almost ready, so don’t you fright.

When what to my wondering eyes should appear, a massive build from the Ops Engineer!

This today, that tomorrow, “Fail Fast” and learn there is no sorrow!

Ho Ho Ho! A jolly Scrum Master appears; impediments removed we all give a cheer!

Ops leads the way with their nose shining bright; we are agile and fast and we’re out of site!

Off with a flash, then “deer-to-deer” review”; here comes the surprise, it's coming to YOU.

We stand all amazed and straight is our gaze.

The Christmas tree stands all tall and bright; its branches are massive and covered with lights!

On top is a star that streams long bright bars, spreading LOVE, PEACE, and JOY both near and afar!

We are proud and celebrate this De Liv ere eee! We got it all done with “velocity”.

Down in the meadow, we see a small boy. It’s Tiny Tim with a new “user story”.

The tree is amazing, but children are coming; they need some presents, so we’re off and running.

No time to linger there is much to do; we’re agile and fast, and on to Sprint two!

Red hats are flying and only one "White" we know we must hurry to make this all right.

Now the children are happy, and they’ve come from miles; presents abound bringing their happy smiles.

In retrospect when all’s said and done; working the DevOps Pipeline is very much FUN!

Merry Christmas to all and Happy Holidays, too. We will continue to “collaborate” with YOU!

Ho Ho Ho!

Have the happiest of holidays!

Comments

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

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

Search