Skip to main content

Recommended Reading (Part 2)

Last week, we discussed the value of having well-rounded knowledge of ITIL, ITSM, Organizational Change and Business Management in preparation for and after the Managing Across the Lifecycle (MALC) course and certification.
Here is the continuation of my recommended books.  As a lifelong learner, I am always looking for new works.   Please feel free to make additional suggestions via comments to this blog.
 

Part 2: Recommended Reading

  • Who Moved my Cheese? by Spencer Johnson
  • The E Myth Revisited by Michael Gerber
  • In Search of Excellence by Tom Peters
  • The Balanced Scorecard: Transforming Strategy in Action by Robert Kaplan and David Norton
  • Good to Great by Jim Collins
  • Competitive Advantage by Michael Porter
  • Competitive Strategy by Michael Porter
  • Reengineering the Corporation by Michael Hammer and James Champy
  • Reengineering Management by Michael Hammer and James Champy
  • Principles of Scientific Management by Frederick Winslow Taylor
  • First, Break All the Rules by Marcus Buckingham
  • Now, Discover Your Strengths by Marcus Buckingham
  • Go, Put Your Strengths to Work by Marcus Buckingham
  • The Fifth Discipline by Peter Senge
  • Organizational Learning: a Theory of Action Perspective by Chris Argyris and DA Schoen
  • Blink by Malcolm Gladwell
  • Tipping Point by Malcolm Gladwell
  • Outliers by Malcolm Gladwell
  • Turn the Ship Around by L. David Marquet 
  • It’s Your Ship by Michael Abrashoff

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…