Skip to main content

Dimensions for Transformation Leadership

If you are involved in helping your organization to incorporate Agile, DevOps or any type of Digital Transformation it will become very clear that “Leadership” will have a powerful impact on the success of your effort.

Transformational Leadership is a model in which leaders inspire and motivate followers to achieve greater performance by appealing to their values and sense of purpose.  This helps to facilitate wide scale organizational change.  That type of wide scale change is required.

Required Dimensions for every Transformational Leader that will promote positive results include:

Vision – Leaders must understand the organizational and team direction and shape them accordingly. People will follow an individual who inspires them, a person with vision and passion can achieve great things.  Leaders need to inspire followers to motivate the results they wish to see.
Personal Recognition – Includes but is not exclusive to recognizing and commending the team for better than average work.  Personally, complimenting individuals for outstanding work can go a long way to inspire a sense of pride and positive attitude.  Attitude is everything.
Supportive Leadership – Overall supportive leadership infers that leaders consistently consider others personal feelings before acting.  A real sense of caring about individuals and their interest will be recognized.   The opposite will also be recognized if it does not exist.  Caring must be evident.
Intellectual Stimulation -  Transformations by their very nature should challenge the teams status quo.  Leaders will need to ask new questions and challenge teams on basic assumptions about the work being performed.
Inspirational Communication –Inspiration and passion demonstrated via leadership will propagate to the team.  Inspiration motivates.   This form of communication inspires pride and shows that leaders need to say positive things about the team.  Inspiration encourages and allows followers to see that change brings about opportunities.  Motivation results in action.

Leadership is not just for the executives in the corner office.  One of the most powerful things we can do in this lifetime is to grow our personal leadership skills.  As John Maxwell says, leadership is influence. Influence is the power to change, or the power to affect someone or something.
A DevOps Leader is a tactical or strategic individual who helps design, influence, implement or motivate the cultural transformation proven to be a critical success factor in DevOps adoption. This individual understands the human dynamics of cultural change and is equipped with practices, methods and tools to engage people across the DevOps spectrum.  

Transformational Leadership is essential for establishing and supporting generative and high trust cultural norms.  Great leaders develop through a never-ending process of self-assessment, self-study, education, training and experience.





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…