itSMF publish their list of ITIL Version 3 processes

it's more than nice-to-know

From what I hear about V3 it seems to build on the "process approach" of V2. Wouldn't it be nice then that we at least had a common understanding on what that was, before running off to V3?
I suggest to use a very simple solution to determine the correct answer to the question (and it has far-stretching consequences, I can promise you that).

My suggestion would be to apply the definitions of ITIL when you read ITIL.
Sounds simple he?

So let's have a look at some of the things ITIL says about a process:
- A process is a set of coordinated activities combining and implementing resources and capabilities in order to produce an outcome which, directly or indirectly, creates value for an external customer or stakeholder
- Process definitions describe actions, dependencies, and sequence.
- Processes have the following characteristics: Measurable, Specific results, Customers, Responds to a specific event.
- Processes are examples of closed-loop systems because they provide change and transformation towards a goal, and utilize feedback for self-reinforcing and self-corrective action. It is important to consider the entire process or how one process fits into another.

Are you still with me?

Then I'll go on with some more interesting quotes directly from "the source":
- Functions are often mistaken for processes. For example, there are misconceptions about Capacity Management being a service management process. First, capacity management is an organizational capability with specialized processes and work methods. Whether or not it is a function or a process depends entirely on organization design. It is a mistake to assume the capacity management can only be a process. It is possible to measure and control capacity and to determine whether it is adequate for a given purpose. Assuming that is always a process with discrete countable outcomes can be an error.
- Definition of a process: A structured set of activities designed to accomplish a specific objective. A process takes one or more inputs and turns them into defined outputs. A process includes all of the roles, responsibilities, tools and management controls required to reliably deliver the outputs. A process may also define or revise policies, standards, guidelines, activities, processes, procedures, and work instructions if they are needed.
- Process control can be defined as: The activity of planning and regulating a process, with the objective of performing a process in an effective, efficient and consistent manner.
- Processes, once defined, should be documented and controlled; once under control, they can be repeated and become manageable.
- Process results must be individually identifiable and countable. While we can count Changes, it is impossible to count how many Service Desks were completed. So change is a process and Service Desk is not: it is a function.

So let me ask you (with these ITIL definitions in your mind): how many capacities have you done today? And how many availabilities? And how many continuities? Securities? What about the number of finances? Or Configurations? Demands? Suppliers?

And let's finally have a look at that one great graphic on how a process is structured and managed (it was in V2 and again all over V3 and was already used all over the world before it was copied into ITIL); it says that we have an input, a series of logically grouped actions, an output, and a control mechanism that includes a feed-back loop. (I'd prefer to also manage the *outcome*, but that may be a too much to ask). Now take that graphic and read the Availability Management documentation (in whatever version), or the Capacity Management chapters. Or Knowledge Management. What about Access Management. Or Service Measurement? Or Return on Investment? Can you see how they fit into that graphic?

Now (with the ITIL definitions still in your mind) start counting the processes: 1, 2, 3, 4, 5, 6.... maybe it's my lack of imagination - or I should drink more wine to double my vision - but that's about as far as I get.
Jeroen Bronkhorst very recently told me that he was near the end of the job of delivering the ITIL process model, and I believe that he's done his very best at this. I guess TSO will publish it without a (public) review, like the additional ITIL stuff in TSO's introduction book was published without a review. Until that time it will be one of the best kept secrets in the industry, as it always was for V2.

I'm opening the register for opinions on this process count at ITSM Portal now. Maybe the Skeptic can do a similar one in this blog. Shall we make a bet on the outcome?