Monthly Archives: August 2011

ITIL Finland

ITIL® Finland

The applications of ITIL® have become an integral part of the IT industry. ITIL® Finland has transformed the technical industry into to a complete service provider and well-managed industry.

Employees of the companies in Finland were not really equipped in preventing or handling of problems and mismanagement. This led to loss and inefficiency. ITIL® Finland has provided great security and comfort in this regard. Qualified professionals manage the functions, recruit staffs and trainees and make future policies for the organization.

Some of the major areas of work are configuration management, service, problem, process management, service desk and service support. The Art of Services offers services in Finland where people can access ITIL® Finland courses and learn about ITIL® applications at both the primary and professional level.

What is the BIG new thing in ITIL Version 3?

One of the gaps that evolved was that the focus on service management became very operationally-based. The big add-on change that is being introduced is to take a broader viewpoint of what service management encompasses.

This includes strategic considerations, the design implications, and the cultural and organisational change implications.

So the major add-on shift is to introduce service management from a life-cycle perspective, from strategy to production, as opposed to just a process-based view.

Why Project Scope Management is Necessary

Project Scope Management is a required component of any Project Management effort, because without it the project would proceed everywhere and nowhere fast until resources run out. Precisely because Project Decision Makers need to manage project resources well, Project Scope Management should be undertaken as well.

In Project Scope Management, steps are undertaken to assure that only necessary work will be completed in the duration of the project, with unnecessary work totally excluded. This helps clarify the scope or coverage of the work for all concerned parties.

The processes or steps that Project Scope Management entails are: Scope Planning, Scope Definition, Components Division, Scope Verification, and Scope Control.

Under Scope Planning, a plan will be created wherein the scope will be thoroughly defined, undergo verification, and be controlled. This is also where the work will be broken down into sub-processes.

Scope Definition requires creating a well-defined scope statement so that project decisions later on can be based on this statement.

Components Division means that the work which was earlier broken down into sub-processes will be further subdivided into more manageable steps or portions.

In Scope Verification, the project deliverables will be completed and delivered, with formal acceptance assured.

Scope Control is the final step and means that any changes to the project scope will be managed here.

Each of these steps may require input from just one person, or from the entire team, where necessary. It may be observed in practice that the steps do not occur in the order they appear here, but may overlap or be interchanged as the Project Decision Makers see fit.

The Three Functional Types of Business Process Management Software

There are a lot of Business Process Management (BPM) software packages around – most of which present almost identical features but at the same time, a touch of uniqueness in them as certain functions integrated with some set them apart from the rest. This is the reason why it is a bit challenging to categorize BPM software, but nonetheless, here are the three software types with functions that are innate in almost all BPM packages.

(a) Workflow-based applications This software type suggests how processes can be efficiently delegated to automated systems and team members. To get this done, a workflow software requires a detailed map of existing business processes and these are then carefully evaluated to take on the task of automating certain steps to deliver optimum results and performance, hence increasing customer satisfaction. However, since a workflow software is applied to a fix process, making certain adjustments or improvements on it may not be permitted.

(b) Efficiency monitoring software Determining the weak link that makes the process chain ineffective or unsuccessful is the main goal of this type of BPM software. This is accomplished by carefully monitoring the process from start to finish, possessing built-in application programming interfaces (APIs) to connect with any enterprise system during the course of a business process. Identifying such constraints will make it easier for the management to find methods of overcoming them through a series of careful strategic planning.

(c) Enterprise Application Integration (EAI) tools This is a combination of both workflow-based and efficiency monitoring software applications. This tool use APIs to extract information from various systems that will result to an increase in the level of efficiency of business processes.

Complexity Addressed: The Zachman TOGAF Explained

Working with TOGAF and the Zachman Framework has always been said to be comparable to the Periodic Table. This is because like the atoms that can be found in a periodic table, the same atoms are also the building blocks of the cells which can be found in the Zachman Framework – only this time, the building blocks are used in supporting enterprises. In the framework, one will find many columns that really do have no logical order of importance.

Instead, they serve as somewhat unique abstractions of the actual enterprise itself. This is done in order to reduce what complexity there may be in the different models that are built around it. The cell models, or the primitive models, are present such that there can only be one variable. John Zachman says that these primitive models are highly important in order for the reusability of the enterprise itself. Also, the commonalities which can be found in the enterprise are such that the primitive models can also be considered as one of the elements of architecture.

The astounding detail that is involved in the Zachman Framework is very impressive. Not a single cell becomes the sole property of one detail or one row, as all work to make things highly functional. The great thing about this is that it gets to ensure the alignment of the different intentions of all owners of the enterprise, which can then be best represented by the second row of such a framework and everything that was implemented as a requirement to building the enterprise itself.