Entries in the category "Practices"

DevOps: Why The 15 Essential Practices Are Key To Your Organization’s Survival

The survival of many organizations depends on how quickly their IT department can help them adapt to a continual and rapidly-changing environment and deliver business value better, faster and cheaper.

The DevOps movement is designed to remove the blockages that hinder IT from delivering the value that the business requires, at the speed the business desires. Accordingly, organizations are heeding the call and IT is feeling the pressure to quickly adopt and successfully implement DevOps, but many are experiencing challenges in effectively applying the concept.

In response to this, Pink Elephant has developed a unique methodology consisting of 15 essential practices that allows organizations to implement DevOps through the ‘Full Stack’ of culture, practices and automation. This approach defines and provides guidance to help change the relationship between Application Development and Systems Operations, break down the “Wall of Confusion” and ensure effective collaboration.

It’s All About Integrated Service Management

The scope of IT Service Management (ITSM) – as we’ve known it for almost 30 years – has been increasing recently.

Not only do we still have the core processes for ITSM, but we also have some related practices and guidance to help us address ITSM in the context of the fast changing business demands we’re all experiencing today. We’re talking Lean & Agile here.

Each of these provides additional approaches and value to help ensure that IT objectives and results are what the business really needs.

But it’s not all about documented practices. 

The Evolution of Process Governance

(From Process Owner –> Service Management Office -> To SIAM)

Every Community Needs Good Governance Otherwise We Get Lord of The Flies & Piggy Dies
Ref: Lord of the Flies is a 1954 novel by Nobel Prize–winning British author William Golding

As organizations look for ways to accelerate value delivery and improve collaboration, people and teams have traditionally turned to published IT frameworks and models for ideas and answers. Many of these models make the point that defining and documenting your processes is simply not enough. For any organizational process, product or capability to be sustained and improved over the long term, it is critical to establish and gain acceptance of ownership and personal accountability. Effective ownership means that those who accept this responsibility have each of the following characteristics; interest,  time, skills, knowledge, passion and authority. (All of these elements are critical and need to be present for this concept to work!)