Skip to main content

Are You Ready for Some Football?

It’s that time of year where the kids are heading back to school, the seasons are about to change and YESSS it’s time for the NFL to begin its new season!   The other night I was watching the HBO series NFL Hard Knocks about the Cincinnati Bengals training camp and it dawned on me how much a football organization is similar to an ITSM organization and how they incorporate ITIL best practices in their methodology.  I know you are saying, what the?????? But hear me out and let me show you a few comparisons.

Strategic Plan:  Win the Super Bowl and become the world champions.  Well defined, well communicated.  Everyone in the organization understands what the fans (customers) want. Strategy defines the perspective, position, plans and patterns that the organization will need to execute to meet its business objectives.  This began at the end of the previous season (CSI) as the coaching staff reviewed statistics (CSF & KPI) to identify improvement opportunities for the next season (Problem management) how well they did on investment in personnel (ROI) and how good they performed against the rest of the league (Benchmarking).
Tactical Plan:  Ensure that the offense, defense and special teams can work together to carry out the game plan (predefined model for that particular opponent) each week.  In other words are all the processes aligned and have they been given the appropriate knowledge and capabilities to ensure that the intended outcomes can be achieved.
Operational Plan:  Monitor, measure, maintain and knowledge transfer. Watching film on the upcoming opponents and outlining those areas of weakness that can be exploited by creating offensive and defensive packages (models) that can be implemented against their upcoming rival.   Defining roles and responsibilities and reviewing personnel statistics (CSF, KPI, metrics) to look for strengths and weaknesses of each team member. "Practice what is right so you can’t get it wrong” (Vince Lombardi) by engaging in repeatable, proven training methodologies.
So if your favorite team seems to be struggling this year, you may want to drop the coach an ITIL Foundation pocket guide. Enjoy the season and let's play some football.

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…