Skip to main content

Documented Policy

Governance: Ensures that policies and strategy are actually implemented and insures that the required processes and procedures are followed.  This includes the defining of roles and responsibilities, measuring and reporting and taking any actions to resolve any issues identified.

Policy: Formally documented management expectations and intentions.  Policies are used to direct decisions and ensure consistent and appropriate development and implementation of processes, standards, roles, activities, IT infrastructures and anything that will give guidance on the management of your organization.  The objective of policies and procedures is to document an organization’s policy for operation and the procedures necessary to fulfill that policy. 
Policies and procedures answer the “what” and “how” questions for individuals within an organization.  Written documentation will allow for consistent treatment across the organization.  Policies and Procedures also help to create an internal control framework.  It is this internal control framework that management will rely upon and that will ensure the organization’s objectives are being met.

Policies and procedures are the strategic link between the organization’s vision and its day-to-day operations. Well written policies and procedures allow employees to understand their roles and responsibilities within predefined limits. Policies and procedures allow management to guide operations without constant management intervention. Policies identify the key activities and provide a general strategy to decision-makers on how to handle issues as they arise. This is accomplished by providing the reader with limits and a choice of alternatives that can be used to "guide" their decision making process as they attempt to overcome problems.

The ultimate goal of every procedure is to provide the reader with a clear and easily understood plan of action required to carry out or implement a policy. A well written procedure will also help eliminate common misunderstandings by identifying job responsibilities and establishing boundaries for the job holders.  Good procedures actually allow managers to control events in advance and prevent the organization (and employees) from making costly mistakes.
Without well documented and communicated policies, misunderstanding, confusion, missed opportunities, aggravation and chaos will ensue.

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…