Skip to main content

ITSM and the Consummate Gardener

The Consummate Gardener

 
There are times in IT Service Management that seem to be like dry cold spells.  Times when the funding is dry, the resources are lean and to all but the consummate gardener might appear to be nonproductive in the way of moving forward.  The consummate gardener will find something to put on the schedule in the bitter cold of January, something like garden planning, tool maintenance, or alphabetizing the seed packets. Perhaps browsing seed catalogs and more to ensure they are prepared for the next season. Why?  They have a vision!  The crop, the wonderful fruit of their labor realized.
 
Back to the Basics
Like the gardener there are areas of ITSM Best Practice that a service provider can continually be preparing for and improving.  When times are lean and dry as well as when they are not.  With all the terms, the technology, the latest and greatest buzz lets pause and step back; back to the basics.  For the gardener that is the seed, the soil and the tools that will be needed to ensure their vision.
People:  (Seed)
Consistent thought effort and preparation for how to invoke the culture required for strategic initiatives has to begin with a focus on people.  Who? What? Where? How? When will you need executive management involved in the near future for aspires that are on the horizon?  The consummate gardener in ITSM will be reading up on relationship management, stakeholder communication, and perhaps investigating to find out what communication plans and awareness campaigns are working in other areas that they can leverage from.  They will be engaged in and encouraging change champions that will create fertile ground for the upcoming seed that will soon be planted.  
Process:  (Soil)
The crop will not bring in itself.  Like the gardener the service provider will need to think of who, what where when how the ground is to be fertilized, tilled, planted and sowed to ensure a fruitful crop.  For ITSM it might be things like what governance boards will be required?  Not only what policy will be needed to govern ITSM processes but what activities and procedures will I need?  The gardener here will be preparing for documentation, knowledge management and perhaps begin with what templates might help.   The consummate gardener has a listening ear for conversations that make evident where existing process and activities are broken.  Listening, reading gathering and preparing while constantly keeping the vision of the full crop in mind while fertilizing the soil.  When the time is right the consummate gardener will be prepared to instigate the projects required with appropriate buy in and support and watch their vision play out.
Technology (Tools)
Success for many gardeners comes from having the best tools available.  The consummate gardener is aware that determining the crop, getting prime seed, building relationships and getting the best suppliers for just the right seed will trump the tools and automation that they might be fortunate enough to have.  Bad seed when planted in unprepared soil will not result in the best crop regardless of what tools or automation the gardener uses.
The consummate gardeners in ITSM will take advantage of every season prioritizing their thoughts and efforts with a clear vision of the crop.  They understand that the seed and the soil are utmost to their success and will prioritize to ensure that the tools they use are in support of those.  Let’s get back to the basics: The seed, the soil and the tools.  The planting does not begin in spring and the crop will not bring in itself.  We need a consummate gardener who understands that the heart the vision and the effort in the bitter cold of January will bring forth the ultimate fruitful crops all in their season.

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…