Skip to main content

Ebony and Ivory - Agile and ITIL

Today technology has been integrated into almost every aspect of business and continues to grow in importance with every new innovation. It is impacting organizational structures, business processes, how and what products and services we offer to our customers.  This tidal wave of change is increasing in complexity and velocity.  These dynamics are shaping the strategies we must employ to manage our IT environments.

Given the changes that are happening in the digital world today, support organizations have had to look at how to enhance and speed up the traditional waterfall approach to management of our IT infrastructures.  ITIL and Agile are not contradictory of each other. Agile development provides opportunities to assess the direction of a project throughout its development lifecycle.  It is a methodology on how to deliver projects, that is iterative, adaptive and an incremental approach to project management which can be used for almost any type of project.

ITIL is about best practice in IT Service Management. It’s a holistic collection of processes and functions on how to define, design, transition, run and continuously improve services and the processes that support their delivery.  ITIL’s perspective is from the operational point of view, recognizing that value to the customer is delivered during service operation and therefore operational requirements must be engaged as early as Service Strategy. ITIL is neutral about what types of tools or management methodologies are used, which means that ITIL and Agile are complementary and not competitive.

From a design perspective, both usually have a starting point of an approved business case and gather business requirements.  One in the form of a Service Level Requirements document, the other in user stories.  Both then prioritize these requirements or improvement opportunities ensuring they align to customer needs and the overall business strategy.

During the transition phase time boxed sprints are employed.  Normally the sprint will start with a sprint planning meeting and daily standup meetings, which help to track progress and to eliminate impediments. The sprint ends with the sprint review meeting, where the new or changed service is formally accepted. There can also be a Sprint Retrospect Meeting, which results in lessons learned for the next sprint.

In ITIL the change transition planning and support process gets employed to oversee coordination and prioritization of resources.  Moving into change, SACM and release and deployment controls are utilized to insure that intended outcomes are being realized and risk assessment are being properly review, along with accurate recording of data, information and knowledge. This will normally finish with a post implementation review where the change is accepted into operations and lessons learned can be recorded for future changes.  In speaking with a number of my students, it’s in the actual deployment and the operational phases where they are still working on the integration of methodologies. They incorporate Agile in the Strategy, Design and large parts of the Transitions stage, but in the Operation stage, the rigor of the ITIL concepts is still a requirement when integrating older applications and systems with new that are still prevalent in real world situations (off the island).  This helps to safeguard service availability, security and continuity while Agile ensures the quickened pace to deliver new capabilities to the business. This ties in with creating a culture of ITIL’s continuous improvement, while looking to move forward with greater speed, without compromising quality.

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…