For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone
Note: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Posted: Tue Feb 23, 2010 3:00 am Post subject: ITSM - Need Guidance
Hi All,
I am trying to draft down a career path for a fresher to join in ITSM and then move up the ladder.
Now if we see a support group - they will have aq clear cut career path to climb up the ladder...
like a L1, L2, L3 support
Then a technical Lead
Then a technical Manager
Then an Architect
etc
How does it work for ITSM - I am in need to draft a career path for a person in ITSM..but in general as ITSM and not a specific division as IT Service Operation or IT Change Management Or IT Demand Management
Say a fresher to be considered as
ITSM coordinator
Then moving up the ladder can be designated - ITSM Analyst
I get stuck from here: Logically it should flow to ITSM Manager
Then ITSM Process Owner
but what next - Straight to Service Delivery Manager?
I feel there is should be something in here or there should be something running parellel to ITSM Process Owner... say a role of ITSM Architect (who can be responsible for defining policy, or who could be considered an SME for ITSM implementation for all projects and be consulted or relied upon to seek best practically implementable solution)
May I request some help here in defining roles within ITSM (in generic manner) which will lead as a career path and some guidance on differentiating their responsibilities and key skills required for job.
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Tue Feb 23, 2010 9:51 pm Post subject:
Whilst some combinations are likely to be more frequently followed than others, I doubt very much that it makes sense to sketch out a career path in these terms.
Certainly I have seen very diverse career moves within IT and the development/recognition of aptitudes combined with the opportunities that pop up at the right time have a lot to do\ with what happens.
Stepping back a bit, I'm not sure that there is much sense in trying for such a detailed mapping into the future because the future seems to change quite radically before you get there.
It might be more fruitful to just keep track of what sort of things you feel good at and interested in and take opportunities that arise in which you can exploit this. Some people believe they will always be technical while others believe they will certainly move to management roles and both cases a proportion of these are borne out in time. But I thought I would always be technical when I started and that just shows what I knew!
Even if you insist on establishing these detailed progressions, you really need to expand them somewhat. For example what about capacity and performance technical roles?
Finally, There is no need to perceive of a career in ITSM as being a sequence of management roles from start to finish. The move from a "technical stream" into a "management" role can occur at any level and can be hybrid through several levels. It is certainly hard to perform such roles without at least some technical background. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum