Skip to main content

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 retrospective 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

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…