Skip to main content

Changing Culture to Become Agile Based

 Success in modern technical endeavors absolutely requires multiple perspectives and expertise to collaborate. (1)  When I ask managers attending my classes if their organizations practice ‘agile’ they hesitate and say something like we kind of do but not in all areas of the organization. Further questioning usually uncovers that most of this agility starts and ends with the software development teams. When asked if these practices have been introduced to the business units there is a long uncomfortable pause, and then I hear 'we don’t usually talk to those groups'.

Over the last couple of decades, a new set of major management philosophies have been developed and are now being adopted to ITSM. These new ways of thinking enabled manufacturing, software development and others to analytically realize both disciplined execution and continuous innovation, something that was thought to be mutually exclusive and impossible to accomplish with traditional management methods. Over the last decade these new practices, such as Agile, Scrum, Lean, Kanban and DevSecOps, have been proven to improve performance in thousands of organizations around the world.

As organizations begin to shift towards continuous integration, delivery and deployment through the adoption of the DevOps principles, Flow, Feedback, Experimentation and Learning, we can also create a new type of conversation with the business – a continuous one. We now have the resources and capabilities to deploy products in hours, not months. To support this rapid level of change the business units that define and fund the creation of these services must also display that same level of agility. ‘The way we’ve always done things’ with little to no communication creates constraints on the development and support teams ability to quickly respond to the rapidly changing competitive landscape.

Every business decision creates an IT opportunity.  Agility in the entire organization requires decision-making to be done as close to the customer feedback as possible (The Three Ways). The teams working on the products need to be able to quickly decide what to work on next based on continuous feedback from the end-user/customer.  Through experimentation and learning making mistakes is not a failure, it is the elimination of an unusable alternative.   These opportunities should be quickly analyzed and any new information incorporated into the next set of sprints (The Three Ways).

Some organizations like Apple, Google and Zara do things differently. These firms constitute what has been called the Creative Economy. They have shifted the goal of the entire organization from maximizing shareholder value to delighting the customer. These are organizations in which all the management layers adopt the philosophy of ‘customer-value first.’ They are Agile-friendly environments. In such firms management practices at the team level, like Agile, become self-evident. Making money becomes the result, not the goal of the organization. Paradoxically, as the examples of Apple and Google show, this approach can be hugely profitable. (2)

Making the transition to Agile includes five major shifts:
  • Instead of a goal of making money for the organization, the goal of the organization is to delight the customer.
  • Instead of those doing the work reporting as individuals to bosses, the work is done in self-organizing team: the role of management is not to check whether those doing the work have done what they were meant to do, but rather to enable those doing the work to contribute all that they can and remove any impediment that might be getting in the way.
  • Instead of work being coordinated by a bureaucracy with rules, plans and reports, work is coordinated by Agile methods with iterative work cycles and direct feedback from customers or their proxy.
  • Instead of a preoccupation with efficiency and predictability, the predominant values are transparency and continuous improvement.
  • Instead of one-way top-down commands, communications tend to be in horizontal conversations.

The principles are not a random collection of improvements. Together they form a mutually reinforcing sequence. (3)


(1) John Allspaw - The DevOps Handbook by Gene Kim 

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 th

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

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi