Showing posts with label changing IT culture. Show all posts
Showing posts with label changing IT culture. Show all posts

Thursday, October 14, 2010

ITSM Weekly the Podcast (Week29) - Guest Speaker:Matt Blair & Taj Peeran

For the next gen of IT professionals the business landscape is a theory not a law.  With so much dynamics in the underlying operations of marketing, sales, manufacturing, IT is going to be challenged to bring a new game to the table.  Students need to be Business Students with Technology skills.  Product development and innovation is going to be a the mainstay of the engineering folks.   The role of the IT professional will be to manage the "pure sciences" capability, including intellectual property into a monetized outcome of technology (applied science).  Creating and protecting value models based on business benefits driven by technology will be no easy task.  The CIO of the future will have to have deep and diverse skills, if role exists at all.

Listen in to this weeks podcast as we talk to Matt Blair & Taj Peeran 2 students working to get their Masters in Information Services (MSIS).
Show notes here: http://www.servicesphere.com/blog/2010/8/22/itsm-weekly-the-podcast-episode-29.html

ITSM Weekly The Podcast (Episode 29) from ServiceSphere on Vimeo.



Dancing as Fast as We Can, Utility, Warranty and the “I” in team. 
What happens when a CIO, a Service Desk Manager and an Industry Junkie Chat Weekly?!
REAL LIFE STUDENTS OF ITSM!
Special Guest:  Matthew Blair - Matt Blair is the President of the MSIS Association - a networking, personal development and community service organization that runs a parallel with the Masters in Information Systems (MSIS) program in the Kelley School of Business at Indiana University.  He writes about current IT issues in his blog,MattMinute, and also has intern experience in audit, project management and process refinement.  He holds a Bachelors in Finance and Accounting and will be graduating with a Masters in Information Systems in May 2011.  He can be reached via LinkedIn or e-mail at mablair@indiana.edu.
Special Guest:  Taj Peeran is currently pursuing a Masters Degree in Information Systems at Kelley School of Business, and at the moment interning at Mead Johnson, Evansville for the Global PMO Group. With an undergraduate degree in Computer Science, and a keen interest in technology and software development, he worked for Wipro Technologies for 4 years, where he focused on developing and architecting solutions on the J2ee platform. On the MSIS program he says - 'The program has an excellent blend of technology and business subjects. The focus of the program is to empower its students to understand the different aspects of managing and governing IT'. He can be reached via LinkedIn or email: apeeran@indiana.edu
Series:  ITSM and Higher Education
Submit Questions:  Anonymously or Email or Call In: (765) 236-6383 or Twitter Questions/Comments #ITSMWP
Episode 29 Topics:

Tuesday, August 24, 2010

ITSM Weekly the Podcast (Week26) Special Guest: Riitta Raesmaa


One of the areas that plagues CIO's and subsequently IT organizations is the area of contract management.  Even the CIO who is a savvy negotiator will readily admit, once the deal is inked managing the life-cycle of the contract becomes an exercise in file keeping, not vendor management.  This weeks guest on the podcast is Riitta Raesmaa, VP of Marketing and Communications for Sopima.  Like all of our guests she is skilled in ITSM and a major contributor to information sharing, whether through ITSMF or twitter.  She doesn't talk about contracts management on the podcast, but looking at her companies website Sopima got me thinking, this is definitely a topic CIO's could learn a lot more about.
Our last in the series of Women in IT Riitta is great fun, has a huge following on twitter and brings some great insight to the nation of Findland.

Show notes and Links here:  http://www.servicesphere.com/blog/2010/8/1/itsm-weekly-the-podcast-week-26.html  Thanks again to Hornbill for sponsoring this series.


R


ITSM Weekly The Podcast (Week 26) from ServiceSphere on Vimeo.

how Hosts:
Christopher Dancy
Matt Beran
Matthew Hooper 
 


Sponsor:  Hornbill Software 
Sponsor Special:  You Choose!! 
Week 26 Topics:

Thursday, July 29, 2010

ITSM Weekly the Podcast (Week24) -Women in Tech Series Guest: Sophie Klossner

Continuing our series of Women in Tech, we are excited to have Sophie Klossner on our show this week.  An active and leading member of HDI since 1992.  Sophie has seen the IT profession develop from multiple angles, and gives us a great perspective on it's current state.
It seems to me that the world is getting more competitive.  Because of this I think we are seeing a more drastic reaction to events.  In other words, when things are good, they are great, however, when things are not good, they are horrible.  The reality of it all is things are rarely "Great" and rarely "Horrible" and we tend to get caught up in cycles.   This weeks' podcast touches on a real situation where Cloud Computing takes an impact.  We all know it happens, and that it will happen.  Yet we also know the the market cannot sustain a reputation hit this early in it's development.  Enjoy the discussion that ensues when Beran send "The Tweet".

I'd like to thank our sponsor Hornbill again for hosting this series.
Show notes are here:
http://www.servicesphere.com/blog/2010/7/18/itsm-weekly-the-podcast-week-24.html


ITSM Weekly The Podcast (Week 24) from ServiceSphere on Vimeo.

Show Hosts:
Christopher Dancy
Matt Beran
Matthew Hooper



Submit Questions:  Anonymously or Email or Call In: (765) 236-6383
Sponsor:  Hornbill Software
Sponsor Special:  You Choose!!
NOTE:  There were audio issues with some of this recording.  We apologize in advance!
Week 24 Topics:  

Friday, June 11, 2010

How to Maximize Outsourcers - Part 2 of 3 - Choosing the Outsourcer












This is the 2nd part of a 3-part article on how to get the most out of your outsourcing relationships.  
Part 2 - The Outsourcer.  Friend, Foe or Value Provider

Part 2 - Them

When making the decision to outsource, you are saying to yourself  "I want to achieve greater value for this particular service by leveraging the core disciplines of others".  What you then need to ask yourself is “what are those value drivers?”.  
There are basically 4 aspects of value you can expect to achieve from an outsourcer.
1) Quality - Since the service you are outsourcing should be core to the provider, you should be expecting an elevated level of quality.
2) Price - The outsourcer is leveraging a shared infrastructure across its customer base,  so you should expect affordability at a unit cost level.
3) Time - Focused operation should have allowed the outsourcer to become mature in their processes and architecture, enabling them to  facilitate new programs with greater efficiency.
4) Risk Mitigation – Lastly, you should expect that the resources required to plan, manage, control, and counteract risks are stronger in the outsourcer, since business tolerance for failure is far less for an outside party than for internal groups. (for the most part)
No doubt there are many other reasons to choose an outsourcing relationship, but these are the major contributors to deriving value from the relationship.  
Before you embark on the transition of the service, you must determine  whether this outsourcer has the "right stuff" to service ME.

Did you know that Outsourcing Fails?  Of course you do; a lot of outsourcing initiatives fail.  Usually this is because of Part 1 of this article "You".  (well, not you personally) 
 However, it also has to do with how the outsourcer was evaluated.
When it comes to evaluating an outsourcer it is important to recognize a few myths:
Myth 1) The outsourcer is in business for me.
Myth 2) Bigger is Better.
Myth 3) SLA's and Contracts protect me

Let's take a look at these myths to determine if our outsourcer is a "friend", "foe" or "Value Provider".

Myth 1) The Outsourcer is in business for me.
OK fine, the outsourcer has chosen to offer a capability you are looking for.   That doesn't mean that they are in business for you.  
That doesn’t mean that they are making decisions to provide capabilities for where your business is going.
In other words, you may mistakenly make the assumption that your anticipated needs are clearly understood by the outsourcer and that their investment strategy is targeted towards your business consumption.
This is a myth that many outsourcers will be glad to let you believe.  
The frank fact is that outsourcers are in business for themselves.  They want to deliver the service that you buy at a given time and maintain that service without change for as long as possible.  Thus, as a buyer, you are not going to get the value unless you clearly articulate your expectations up front and your outsourcer can clearly articulate the service portfolio of current and future offerings.
A 2004 survey from OutsourcingBestPractices.com  stated that 23% of the outsourcing failures were because of "The buyer's unclear expectations up front as to its objectives".
Friend: "We have provided this service for lots of clients, we know what you need."
Foe: "Changes to services only introduce risks, we will accommodate enhanced services after we have stabilized you as a client."
Value Provider: "Here is our Service Catalog of current services.  We are predicting these areas of market demand and have these service in the pipeline to delivered by these dates"
Bottom line:  
If the services aren't in their plans, they won't be in your hands.

Myth 2) Bigger is better
There will be no argument here that for pure play utility services, selecting  a larger company will give you great value.  What I want to focus some light on here is the sometimes mistaken assumption that all services added to a larger firm’s portfolio will be as good and as valuable to us as the core services for which they are known and trusted. 
Another key factor to keep in mind is the life-cycle of an outsourced arrangement.
According to "IT Outsourcing Part 1: Contracting the Partner" there are 5 phases.
Phase 1: Decision Making - Should the organization outsource (see Part 1 of this article)
Phase 2: Supplier selection - what this article is helping cover.
Phase 3: Transition - Transfer services to provider, transformation of retained service ownership
Phase 4: Service Delivery - Maintaining performance and governance over provider.
Phase 5: Contract Completion - Handling renewals, changes or withdrawal.
When thinking about these phases, you need to ask yourself if the size of the outsourcer accommodates your goals.  Remember that outsourcers love to bring clients in and hate to see them go.   So while bigger shops can more readily support the first 3 phases of the life-cycle, what’s their reputation for supporting Phase 4  and 5?  How hard will it be to end the contract with a larger firm?
Larger firms have more resources, yes, in their legal teams.  
This brings us to our next myth.

Myth 3) SLA's and Contracts protect me
This has been, in my experience, one of the greatest mistakes made by either side of the outsourcing arrangement, trusting that an  SLA will provide you service.
The brutal truth is that the SLA is a contract that is in place to fall back on when either party so significantly fails that you have to litigate.  You can reinterpret the claimed breach to a court that will really have no clue what you both are talking about.
You need to think of your SLA like your life insurance policy; you want to have it, but never want to use it.  Understand the risks and conducts that could go against the contract, but otherwise do the right thing.
SLA's are important, don't get me wrong.  However, their greatest usable value is in determining the guidelines by which performance and capacity will be managed.  Outsourcers like any other company provide value for money.  Their value model will be based on the requirements and commitments that you as a client make with them.  The SLA documents these important requirements and commitments, so that resource planning, controls, and execution decisions can be made at multiple levels of the organization.

So if you really want to get the most out of your outsourcing contract, you have to create a Service Network Relationship.  In my next and final part of this article I will share with you the 4 different aspects of Service Perspective.  I promise this won't be your Mama's ITIL Pie and Service Cream.





Monday, April 26, 2010

ITSM Weekly the Podcast (Week12)

This week we had a recap of the Know10 event Service-Now's vendor show, usage of social media solutions and technology for improved ITSM communication and a breakdown of mobile technology.  Definitely more technical than our typical shows, but a real perspective of the tools that we are all trying to leverage.

More great show notes from Chris Dancy here:
http://www.servicesphere.com/blog/2010/4/24/itsm-weekly-the-podcast-week-12.html
Thanks as always to our producer at large out Matt Beran

Listen Now:


ITSM Weekly The Podcast (Week 12) from ServiceSphere on Vimeo.

Tuesday, September 1, 2009

Is now the time for a Service Management Initiative?

Yes, I'm still alive.

Very sorry I have not posted in a long time.(or as we say here in Boston " a wicked long time")
As many of you may have heard Vigilant was acquired by Inforonics in Littleton, MA. It's been a lot of work to get the acquisition accomplished, but we are excited about the new opportunities.
You can read more about that here: Inforonics Acquires Vigilant

Though I've delayed in posting for this particular topic, it may be a good thing.
I'll have to admit, that earlier in the year I may have written this quite a bit differently than I do today. It's been a wild ride here in the US with our economy, and the signs are still blinking as to our recovery. (imho). So my "If I were CIO" strategy is a bit different than in the past.

So what about the IT Service Management strategy that was so vigorously trumpeted in 2008?
From what I have seen there are 2 clear areas that every company needs to focus on, and they need to do it now.
Configuration and Problem Management.
(yes - I know, I didn't say Change, I'm shocked as well, but like I said this article has 9 months of my experiences behind it, so as opposed to the speculation I would have written about in January, I'm writing based on what I have seen.)

Why Configuration and Problem?
First off - the real issue is Problem Management. Companies are really bad at it! Thus when you are working on a problem, and making no progress, this means the business is suffering. Companies can not afford downtime and slowdowns from technology issues, ever - especially in this economy. They need to have systems up and running fast.

So what's the problem with their problem management?
Asset mapping and documentation. I've worked on several major performance and availability problems for clients this year. Serious revenue impacting issues! In each and every example the operational deficiency, and thus the reason to bring our team in, was a gap in understanding of how the technology really supported the business operation.

That is why if companies are going to invest anything in their Service Management initiatives this year, I truly believe it has to be in Configuration Management. Config Management is not just about the assets. It's about the business service, and how the asset's support them. If we (IT - the custodians of operational business technology assets) are going to add value to the business, we need to ensure that we have a handle on what the state of our operations truly is. We need to not only identify the asset relationship, we need to ensure that we can determine its health and its ability to perform on-going.

Yes, of course Change Management comes into play here. However, Change Management alone is not getting the job done. In each of the organizations I referred to above there was a CAB, RFC's, all that jazz. However, there was no record of truth or current health state of CI's. Changes were being made against assumed configurations, without any understanding of their current state of health. (in other words, no integration into event management) So changes were being made and requested against incorrect information and unstable CI's. Hence the problem kept getting worse, not better. (My analogy to the clients as "Stacking Cue Balls" each change caused another break - just like each ball stacked causes the lower ones to topple)

With a well thought out CMS strategy, including health monitoring and CI capacity analysis tools, Problem Management becomes a lot easier for organizations. A clear picture of the assets in relationship to each other helps the process of elimination, it provides a direct plan of attack to isolate root cause, and it also provides helpful information in getting the right people involved.

This is why companies struggle with Problem Management. They expect the PM process to give them root-cause. This will never happen if the proper data is not collected and managed in a meaningful way.

For my next posting I'm going to breakdown the Problem Management process we've used to isolate faults quickly. -I promise it won't take me 9 months to write it. :)