Skip to main content

Posts

Showing posts with the label Organization Change

DevOps Leader

"Culture eats strategy for breakfast." Peter Drucker “Every company wants to behave like a software company.” Sanjay Mirchandani As the business environment continues to evolve and change, an adoption of a digital-first mindset is taking place in boardrooms across the globe. Today’s organizations face a never-ending torrent of change from the dynamics of global economics and competition, to the ever more rapid advancements in technology. These can be perceived as both an opportunity and a threat. The ability to adapt and innovate rapidly in this environment has become a core organizational competency. A leader is needed to bring about this change. Adoption of DevOps can bring about those needed changes that allow an organization to remain competitive in today’s market space. A successful DevOps transformation begins with a value stream map which can allow us to see a time diagnostic of our delivery lifecycle. This flow-based representation gives us an end to end

Organizational Change Management

Change is not something that you do to people, change is something that you do with people. What thoughts occur when you or your staff are notified of a significant change to a process or service?  Is it one of dread, fear or perhaps frustration?  Managing organizational change should be a required element in any or all process and service changes where significant impact for users and staff are expected.   Service providers must ensure readiness for the change and ensure that a cultural shift does indeed take place.  Organizations change for a variety of reasons that could include the need to “get better” or perhaps to “be the best”.  Sometimes organizational change management is triggered by the need to deal with a changing economy or revenue loss.  At the outset, management must be honest with workers and still able to convince them that the best way to deal with current reality is via change.  Each individual’s ability to understand and to accept change will vary.  Change is i

Reference Models

In 1999 the US Federal Government took a step toward improving the quality, performance, delivery and support of IT-based services. This step was the creation of the Federal Enterprise Architecture Framework (FEAF).  This framework consists of five reference models. A reference model is an abstract or logical framework or structure that describes the interconnections between ideas, concepts, elements or components that make up a whole system. We can look to the FEAF reference models as a guide for how we might approach an ITSM implementation regardless of industry or organizational structure. Performance Reference Model : Used to measure the performance of major IT investments  This equates to a CSI or Metrics Program  Business Reference Model : Process-driven structure that describe business operations regardless of the organization that performs them This equates to a Service Portfolio framework Services Reference Model : Classification of service components an