Skip to main content

Lifelong Learning - Recommended Reading (Part 1)

As a follow up to my recent discussion on the differences between being a ‘student’ and being a ‘learner’, I thought it would be useful to provide a somewhat comprehensive list of readings and source material to help those who are heading into and/or beyond the pinnacle of their ITIL learning journey—Managing Across the Lifecycle (MALC).  Preparing for MALC requires a deep level of commitment, beginning with a sound understanding of the five ITIL core books.    To truly be an ITIL/ITSM Expert, you should develop some complementary skills in Organizational Change Management, Business/IT Management and other ITSM frameworks and standards?
 
While it is unreasonable to expect a learner to complete all of these readings as part of their MALC preparation, the spirit here is to recommend a versatile business view that will serve you before, during and after you become an ITIL Expert.    The road doesn't end at MALC - lifelong learning habits will keep your knowledge and perspective fresh and well-rounded.

Even if you cannot read the entire original books, try to find a summary or an overview or even just look up information on the authors.   If you have additional recommendations, please share via comments.

Recommended Reading Part 1

  • The Phoenix Project by Gene Kim
  • Out of the Crisis by W. Edwards Deming
  • The New Economics by W. Edwards Deming
  • Quality Control Handbook by Joseph Juran
  • Quality is Free by Philip Crosby
  • The Six Sigma Way by Peter Pande, et al.
  • The Essential Drucker by Peter Drucker
  • Freakonomics by Steven Levitt
  • The World is Flat by Thomas Friedman
  • Rework by Jason Fried and David Hansson
  • The Goal by Eliyahu Goldratt
  • All Hat No Cattle by Chris Turner
  • The 7 Habits of Highly Effective People by Steven Covey
  • The Five Dysfunctions of a Team by Patrick Lencioni
  • Leading Change by John Kotter
  • The Heart of Change by John Kotter
To be continued next week.....

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…